Difference between revisions of "IS480 Team wiki: 2016T2 ProgneSIS MidTermWiki"
Jump to navigation
Jump to search
Line 179: | Line 179: | ||
[[IS480 Team wiki: IS480 Team wiki: 2016T2_ProgneSIS_ProjectManagement|View our Schedule Metrics Here!]]<br> | [[IS480 Team wiki: IS480 Team wiki: 2016T2_ProgneSIS_ProjectManagement|View our Schedule Metrics Here!]]<br> | ||
− | [[Image:Team_ProgneSIS_Schedule_Metrics_Score_Graph.png| | + | [[Image:Team_ProgneSIS_Schedule_Metrics_Score_Graph.png|600px|center|link=]] |
<h5>Schedule Metrics Highlights</h5> | <h5>Schedule Metrics Highlights</h5> | ||
+ | |||
+ | {| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;" | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Iteration | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Planned Duration (Days) | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Actual Duration (Days) | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Schedule Metric Score | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:250px" | Action | ||
+ | ! style="background: #7f7f7f; color: white; font-weight: bold; width:50px" | Status | ||
+ | |- | ||
+ | |1 | ||
+ | |21 | ||
+ | |22 | ||
+ | |95.2381% | ||
+ | |Estimates are generally accurate and on track. Proceed as per normal. | ||
+ | Slight delay due to the need to integrate with 3rd party accounting software, Xero. Team had to spend more time than planned in integration and understanding what revenue and costs comprise. | ||
+ | |||
+ | Follow up action: Iteration 2 was delayed by a day. However, the subsequent iterations are shortened with modules broken down into more manageable parts. No buffer day is used. | ||
+ | |Completed | ||
+ | |- | ||
+ | |||
+ | |} | ||
+ | |||
<br> | <br> | ||
Line 192: | Line 214: | ||
<h5>Bug Distribution based on Severity</h5> | <h5>Bug Distribution based on Severity</h5> | ||
[[Image: Team_ProgneSIS_Bugs_by_Category_Graph.png|600px|center|link=]] | [[Image: Team_ProgneSIS_Bugs_by_Category_Graph.png|600px|center|link=]] | ||
+ | |||
+ | <h5>Bug Metrics Highlights</h5> | ||
{| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;" | {| class="wikitable" style="margin: auto;width:90%; text-align:center; background: white;" |
Revision as of 15:14, 21 February 2016
Main Wiki | Mid Term Wiki | Final Wiki |
|
Task/Function/Features | Status | Confident Level (0-1) | Comment |
---|---|---|---|
Login/Logout/Registration | Fully deployed and tested 100% | 1 | Minh & Yi Xuan |
Accounts Settings (User Module) | Fully deployed and tested 100% | 1 | Claudia, Minh & Yi Xuan |
Customer Settings (User Module) | Fully deployed and tested 100% | 1 | Claudia, Minh & Yi Xuan |
Integrate with VersaFleet | Fully deployed and tested 100% | 1 | Minh, Yi Xuan & Jason |
Overall Deliver Fulfilment Rate(DFR) | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
DFR by drivers | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
DFR for customers | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
DFR by pickup region | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
DFR by delivery region | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
DFR by volume | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
DFR by drivers | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
Customer view DFR | Fully deployed and tested 100% | 1 | Minh, Yi Xuan & Jason |
Trips by each driver | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
Trips for each customer | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
Trips for each pickup region | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
Trips by each delivery region | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
Trips by each volume (range) | Fully deployed and tested 100% | 1 | Claudia, Minh, Yi Xuan & Jason |
Feedback and enquiry | In Progress | 1 | Yi Xuan |
Help Page | In Progress | 1 | Claudia |
Daily Report | In Progress | 1 | Claudia, Minh, Yi Xuan & Jason |
Project Schedule (Planned vs Actual)
Project Metrics
Schedule Metrics
View our Schedule Metrics Here!
Schedule Metrics Highlights
Iteration | Planned Duration (Days) | Actual Duration (Days) | Schedule Metric Score | Action | Status |
---|---|---|---|---|---|
1 | 21 | 22 | 95.2381% | Estimates are generally accurate and on track. Proceed as per normal.
Slight delay due to the need to integrate with 3rd party accounting software, Xero. Team had to spend more time than planned in integration and understanding what revenue and costs comprise. Follow up action: Iteration 2 was delayed by a day. However, the subsequent iterations are shortened with modules broken down into more manageable parts. No buffer day is used. |
Completed |
Bug Metrics
Bug Score
Bug Distribution based on Severity
Bug Metrics Highlights
Iteration | Bug Score | Summary of bugs | Action Taken |
---|---|---|---|
1 | 26 1 Critical 3 High 1 Low |
Most of the bugs in this iteration were due to incorrect logic to get accurate figures. | The team has to stop all current development and resolve the bug immediately. Project Manager reschedules project. |
8 | 10 2 High |
All of the bugs in this iteration are backend related and are only detected when the developers test and check the algorithms. | The team has to stop all current development and resolve the bug immediately. No rescheduling needed as debugging was relatively straightforward. |
Project Risks
Risk | Probability | Impact | Mitigation |
---|---|---|---|
Uneven distribution of workload | High (It is now low) | High | Members clock in more hours to make up for workload during iterations with heavier commitments. |
Difficulty in getting VersaFleet users | High | High (It is now low) | Team to liaise with client's development manager to schedule for user testing OR team to get logistics users that are similar to VersaFleet users |
Difficulty in getting API from client | High | High (It is now low) | Team to liaise directly with backend developers to acquire necessary APIs |
Technical Complexity
Quality of Product
Intermediate Deliverables
Stage | Specification | Modules |
Project Management | Minutes | Sponsor weeks -19, -14, -13, -10, -5, -4, 1 Supervisor weeks -11, -9, 4, 5, 7 |
Metrics | Schedule metrics, Task metrics & Bug metrics | |
Requirements | Storyboards and User Study | [1], [2] |
Analysis | Use case | [3] |
Sequence Diagram | [4] | |
Business Process Diagram | [5], [6] | |
Screen Shots | CRUD Customer, Trend Analysis | |
Design | Frontend Component Design | [7] |
Backend API Design | [8] | |
Testing | User testing design | [9] |
Deployment
Testing
Reflection
Team Reflection
Individual Reflection