Difference between revisions of "ANLY482 AY1516 G1 Team Skulptors - Project Management"
| Line 37: | Line 37: | ||
<br/> | <br/> | ||
<b>Phase 1: Week 1-2</b><br/> | <b>Phase 1: Week 1-2</b><br/> | ||
| − | + | Phase 1 involved heavily on requirement gathering for the purpose on ensuring that the proposal submission was detailed and relevant to the need for data analyzation. This phase also included the time where the team test and experience using the various analytical tools available. This is to ensure that the team correctly identifies the most suitable analytical tool, given the constraints and circumstances of the project. In total, the team spend the first 2 weeks of the semester preparing and evaluating the above details.<br/> | |
<br/> | <br/> | ||
<b>Phase 2: Week 3-8 </b><br/> | <b>Phase 2: Week 3-8 </b><br/> | ||
| − | Upon approval of | + | Upon approval of the team’s proposal, the team moved on to engage in phase 2, which involves the building of the project’s foundation. In the first few weeks of this phase, most of the time were spend on understanding the data better as the team wished to avoid a situation where they have to constantly check back with the clients to ask for clarification. In order to better understand the work process in the warehouse, the team was also fortunate enough to be granted a day visit to the client’s warehouse in the western part of Singapore. <br/> |
| − | + | Through the exclusive visit to the warehouse, the team had the opportunity to observe and experience first-hand, the problems that were faced within the warehouse. <br/> | |
| − | In Week 4, | + | In Week 4, the team also started developing mockups to allow the clients to have a rough impression of the dashboard’s design and features that the team would be developing for them. The prototypes were then subsequently edited and revised according to the feedback obtained from the clients. These mockups were done on Tableau to quickly give clients a look and feel to our envisioned product. <br/> |
| − | + | From Week 5 onwards, the team shifted to more hands on tasks such as the learning and developing of the prototype using D3.js and its libraries. Throughout this time period, the team also did several revisions on the prototype. These revisions were based on feedback from both the clients and Prof. Kam. Most of these advice involved data visualization good practices since none of the team members had experience in visual analytics. The team also turned to an online book – D3.js Tips and Tricks for data visualization advice, as recommended by Prof Kam.<br/> | |
| − | From Week 5 onwards, | + | This was also the phase where both the dashboard’s inbound and outbound design and layout changed greatly. This change was mainly to incorporate interactivity within the dashboard. The last week of the phase was spent on developing the mid-term report and consolidating the work progress among the team. <br/> |
| − | |||
| − | The last week of | ||
<br/> | <br/> | ||
<b>Phase 3: Week 9-15 (Current Phase)</b><br/> | <b>Phase 3: Week 9-15 (Current Phase)</b><br/> | ||
| − | + | Throughout Week 9 – Week 12, the project focused mainly on warehouse utilization as the clients hope to have a visual display of how much and which part of their warehouse are stocked/filled. This means that through the use of the team’s dashboard, the client should be able to identify where they should locate their fast moving goods, and where to store them in the future. On top of this function, the team also further improvised on the inbound and outbound charts, to create an interactive tree map as suggested by Prof Kam. Control charts were also coded to dynamically display on clicking of the tree map, to show the control chart of the SKUs/Product. In addition, the team also worked on the development of the value added feature – File Upload, as mentioned in the earlier part of the report.<br/> | |
| − | + | The last few weeks of this phase revolved mainly on the integration, debugging and testing of the dashboard. Meetings were scheduled mostly during the study week to conduct the finishing touches for the dashboard. Testing on the other hand, was conducted first by the team, and subsequently by the clients themselves, to sieve out potential problems. This time was also spent on the remaining final deliverables such as final report writing, making of presentation slides and wiki updates. | |
| − | On top of this function, | + | <br/> |
| − | |||
| − | The | ||
<br/> | <br/> | ||
<!--Content End--> | <!--Content End--> | ||
Latest revision as of 15:20, 17 April 2016
 HOME
|
 ABOUT US
|
 PROJECT OVERVIEW
|
 DATA ANALYSIS new!
|
 PROJECT MANAGEMENT
|
 DOCUMENTATION
|
| Project Schedulenew! | Work Plan new! | Change Management new! | Risk Management | Team Reflectionnew! |
Phase 1: Week 1-2
Phase 1 involved heavily on requirement gathering for the purpose on ensuring that the proposal submission was detailed and relevant to the need for data analyzation. This phase also included the time where the team test and experience using the various analytical tools available. This is to ensure that the team correctly identifies the most suitable analytical tool, given the constraints and circumstances of the project. In total, the team spend the first 2 weeks of the semester preparing and evaluating the above details.
Phase 2: Week 3-8
Upon approval of the team’s proposal, the team moved on to engage in phase 2, which involves the building of the project’s foundation. In the first few weeks of this phase, most of the time were spend on understanding the data better as the team wished to avoid a situation where they have to constantly check back with the clients to ask for clarification. In order to better understand the work process in the warehouse, the team was also fortunate enough to be granted a day visit to the client’s warehouse in the western part of Singapore.
Through the exclusive visit to the warehouse, the team had the opportunity to observe and experience first-hand, the problems that were faced within the warehouse.
In Week 4, the team also started developing mockups to allow the clients to have a rough impression of the dashboard’s design and features that the team would be developing for them. The prototypes were then subsequently edited and revised according to the feedback obtained from the clients. These mockups were done on Tableau to quickly give clients a look and feel to our envisioned product.
From Week 5 onwards, the team shifted to more hands on tasks such as the learning and developing of the prototype using D3.js and its libraries. Throughout this time period, the team also did several revisions on the prototype. These revisions were based on feedback from both the clients and Prof. Kam. Most of these advice involved data visualization good practices since none of the team members had experience in visual analytics. The team also turned to an online book – D3.js Tips and Tricks for data visualization advice, as recommended by Prof Kam.
This was also the phase where both the dashboard’s inbound and outbound design and layout changed greatly. This change was mainly to incorporate interactivity within the dashboard. The last week of the phase was spent on developing the mid-term report and consolidating the work progress among the team.
Phase 3: Week 9-15 (Current Phase)
Throughout Week 9 – Week 12, the project focused mainly on warehouse utilization as the clients hope to have a visual display of how much and which part of their warehouse are stocked/filled. This means that through the use of the team’s dashboard, the client should be able to identify where they should locate their fast moving goods, and where to store them in the future. On top of this function, the team also further improvised on the inbound and outbound charts, to create an interactive tree map as suggested by Prof Kam. Control charts were also coded to dynamically display on clicking of the tree map, to show the control chart of the SKUs/Product. In addition, the team also worked on the development of the value added feature – File Upload, as mentioned in the earlier part of the report.
The last few weeks of this phase revolved mainly on the integration, debugging and testing of the dashboard. Meetings were scheduled mostly during the study week to conduct the finishing touches for the dashboard. Testing on the other hand, was conducted first by the team, and subsequently by the clients themselves, to sieve out potential problems. This time was also spent on the remaining final deliverables such as final report writing, making of presentation slides and wiki updates.
