Supervisor Meeting 7 Project Progress Project Status - PowerPoint PPT Presentation

Edmund Jane Kai Cong Shena Yan Jun Supervisor Meeting 7

Project Progress

Project Status 𝑇𝑑ℎ𝑓𝑒𝑣𝑚𝑓 𝐽𝑜𝑒𝑓𝑦 = 𝐹𝑡𝑢𝑗𝑛𝑏𝑢𝑓𝑒 𝐸𝑏𝑧𝑡 𝐵𝑑𝑢𝑣𝑏𝑚 𝐸𝑏𝑧𝑡 Schedule Metrics 140.00% 120.00% SAFE ZONE 100.00% 80.00% 60.00% 100.00% 100.00% 100.00% 100.00% 85.00% 40.00% 20.00% 0.00% Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5

Schedule Metrics Score(%) Status Actions to be taken SM < 80 Severely 1. Emergency Team Meeting Behind Time 2. Inform supervisor and sponsor about the slip within 24 hours 3. Consider dropping tasks 4. Use the same mitigation strategy as the category as 80 < SM < 90 80 < SM <= 90 Behind Time 1. PM to find out the cause of delay from developers 2. Re-estimate the tasks for future iterations 3. Allocate more time for similar functionalities 4. Increase programming sessions for next iteration If end date of estimated next iteration is pushed back, • Deduct the number of days behind schedule from buffer days. • If there is no more buffer day, decide the functionalities to drop. 90 < SM <= On Time If score is not 100%, adjust duration for individual tasks of next iteration to 110 ensure end date for planned iteration will remain the same. 110 < SM <= Ahead of 1. Re-estimate the tasks for the future iterations. 120 Schedule 2. PM to find out from developers the cause of early delivery 3. Add the number of days gained to buffer days. 120 < SM Far Ahead of 1. Immediately, inform supervisor about the slip within 24 hours. Schedule 2. Use the same mitigation strategy as the category 110 < SM < 120

Schedule Metrics Score(%) Status Actions to be taken SM < 80 Severely 1. Emergency Team Meeting Behind Time 2. Inform supervisor and sponsor about the slip within 24 hours 3. Consider dropping tasks 4. Use the same mitigation strategy as the category as 80 < SM < 90 80 < SM <= 90 Behind Time 1. PM to find out the cause of delay from developers 2. Re-estimate the tasks for future iterations 3. Allocate more time for similar functionalities 4. Increase programming sessions for next iteration If end date of estimated next iteration is pushed back, • Deduct the number of days behind schedule from buffer days. • If there is no more buffer day, decide the functionalities to drop. 90 < SM <= On Time If score is not 100%, adjust duration for individual tasks of next iteration to 110 ensure end date for planned iteration will remain the same. 110 < SM <= Ahead of 1. Re-estimate the tasks for the future iterations. 120 Schedule 2. PM to find out from developers the cause of early delivery 3. Add the number of days gained to buffer days. 120 < SM Far Ahead of 1. Immediately, inform supervisor about the slip within 24 hours. Schedule 2. Use the same mitigation strategy as the category 110 < SM < 120

Actions taken No actions required.

Project Status Bug Metric Graph 18 17 17 16 14 13 12 Bug Point 10 8 6 6 4 2 0 2 3 4 5 Iteration

Bug Metrics Points in Iteration Actions to be taken Points < 20 Use the planned debugging time in the iteration. 20 < Points < 30 Stop testing and resolve the bug immediately. 30 < Points < 40 Project Manager to schedule for additional debugging time for the iteration and re-estimate tasks for next iteration. 40 < Points All coders to help in debugging the project. Project Manager to schedule for additional debugging time for the iteration and re-estimate tasks for next iteration.

Bug Metrics Points in Iteration Actions to be taken Points < 20 Use the planned debugging time in the iteration. 20 < Points < 30 Stop testing and resolve the bug immediately. 30 < Points < 40 Project Manager to schedule for additional debugging time for the iteration and re-estimate tasks for next iteration. 40 < Points All coders to help in debugging the project. Project Manager to schedule for additional debugging time for the iteration and re-estimate tasks for next iteration.

Actions taken Used the planned debugging time in the iteration

Iteration 6 Manage Skills Manage Tidy up web codes and tasks improve on code segregation Allocation task to venues (Manage View notifications workflow) De Inte bu Test Deployment grati ggi ing Forget password View tasks schedule on ng 21/8 22/8 23/8 24/8 25/8 26/8 27/8 28/8 29/8 30/8 31/8 1/9 2/9 3/9 4/9 Review Documentations

Test Plan  05/09/2013 - Thursday  3 – 4 Participants  Heuristic Evaluation: UI aspect  UT: Participant and Observer  Same day for heuristic and UT  Should we provide the navigation steps for testing? Because heuristic is to test the usability.

Thank You. Questions & Answers