Difference between revisions of "ANLY482 AY2017-18T2 Group14 Interim"
Mq.wang.2014 (talk | contribs) |
Mq.wang.2014 (talk | contribs) |
||
| Line 61: | Line 61: | ||
<br> | <br> | ||
<font face ="Open Sans" size=4> | <font face ="Open Sans" size=4> | ||
| − | 1. Unfamiliarity of MSSQL and Power BI | + | 1. Unfamiliarity of MSSQL and Power BI: |
Prior to this project, we don’t have any prior experience on these tools, Thus, at the beginning of the project, we invested plenty of time in learning and familaring these tools. | Prior to this project, we don’t have any prior experience on these tools, Thus, at the beginning of the project, we invested plenty of time in learning and familaring these tools. | ||
| − | 2. Lack of domain knowledge | + | <br> |
| + | 2. Lack of domain knowledge: | ||
Domain knowledge is essential in understanding the dataset given, due to the incomplete data definition, we spent a lot of time figuring out the meaning of data, consolidating and documenting the data dictionary. | Domain knowledge is essential in understanding the dataset given, due to the incomplete data definition, we spent a lot of time figuring out the meaning of data, consolidating and documenting the data dictionary. | ||
| − | 3. Communicate with users have non-IT background | + | <br> |
| + | 3. Communicate with users have non-IT background: | ||
We found it is challenging to communicate with users that have limited IT background. Our project sponsor is from operation management. Thus, when we explain some technical complexity to project sponsor, we need to put it into simple and plain words. | We found it is challenging to communicate with users that have limited IT background. Our project sponsor is from operation management. Thus, when we explain some technical complexity to project sponsor, we need to put it into simple and plain words. | ||
| − | 4. Data inconsistency (inconsistent data type, data columns, data values) | + | <br> |
| + | 4. Data inconsistency (inconsistent data type, data columns, data values): | ||
Data collected from the project sponsor is stored in different places with different formats. Besides, the variable type and variable values are highly inconsistent. | Data collected from the project sponsor is stored in different places with different formats. Besides, the variable type and variable values are highly inconsistent. | ||
</font> | </font> | ||
Revision as of 19:27, 25 February 2018
1. Unfamiliarity of MSSQL and Power BI:
Prior to this project, we don’t have any prior experience on these tools, Thus, at the beginning of the project, we invested plenty of time in learning and familaring these tools.
2. Lack of domain knowledge:
Domain knowledge is essential in understanding the dataset given, due to the incomplete data definition, we spent a lot of time figuring out the meaning of data, consolidating and documenting the data dictionary.
3. Communicate with users have non-IT background:
We found it is challenging to communicate with users that have limited IT background. Our project sponsor is from operation management. Thus, when we explain some technical complexity to project sponsor, we need to put it into simple and plain words.
4. Data inconsistency (inconsistent data type, data columns, data values):
Data collected from the project sponsor is stored in different places with different formats. Besides, the variable type and variable values are highly inconsistent.
In the next sprint, we will be continuously working on the excel report output0 to output3. As requested by project sponsor, we will keep the origin format for the management team and at the same time, polish origin report to make it more interactive. We aim to finish this by 15 Mar 2018.
Also, we will start working on insight discovery. TBC
