SLIDE 1
Supervisor Meeting 7
Edmund Jane Kai Cong Shena Yan Jun
Supervisor Meeting 7 Project Progress Project Status - - PowerPoint PPT Presentation
Supervisor Meeting 7 Project Progress Project Status - - PowerPoint PPT Presentation
Edmund Jane Kai Cong Shena Yan Jun Supervisor Meeting 7 Project Progress Project Status =
SLIDE 2
SLIDE 3
Project Status
100.00% 85.00% 100.00% 100.00% 100.00% 0.00% 20.00% 40.00% 60.00% 80.00% 100.00% 120.00% 140.00% Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5
Schedule Metrics
SAFE ZONE ππβπππ£ππ π½ππππ¦ = πΉπ‘π’ππππ’ππ πΈππ§π‘ π΅ππ’π£ππ πΈππ§π‘
SLIDE 4
Score(%) Status Actions to be taken SM < 80 Severely Behind Time 1. Emergency Team Meeting 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 <= 110 On Time If score is not 100%, adjust duration for individual tasks of next iteration to ensure end date for planned iteration will remain the same. 110 < SM <= 120 Ahead of Schedule 1. Re-estimate the tasks for the future iterations. 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 Schedule 1. Immediately, inform supervisor about the slip within 24 hours. 2. Use the same mitigation strategy as the category 110 < SM < 120
Schedule Metrics
SLIDE 5
Schedule Metrics
Score(%) Status Actions to be taken SM < 80 Severely Behind Time 1. Emergency Team Meeting 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 <= 110 On Time If score is not 100%, adjust duration for individual tasks of next iteration to ensure end date for planned iteration will remain the same. 110 < SM <= 120 Ahead of Schedule 1. Re-estimate the tasks for the future iterations. 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 Schedule 1. Immediately, inform supervisor about the slip within 24 hours. 2. Use the same mitigation strategy as the category 110 < SM < 120
SLIDE 6
Actions taken
No actions required.
SLIDE 7
Project Status
6 13 17 17 2 4 6 8 10 12 14 16 18 2 3 4 5 Bug Point Iteration
Bug Metric Graph
SLIDE 8
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. 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. 40 < Points
SLIDE 9
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. 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. 40 < Points
SLIDE 10
Actions taken
Used the planned debugging time in the iteration
SLIDE 11
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
Iteration 6
Review Documentations Forget password Manage Skills Allocation task to venues (Manage workflow) View tasks schedule View notifications Manage tasks Tidy up web codes and improve on code segregation Inte grati
- n
De bu ggi ng Test ing Deployment
SLIDE 12
SLIDE 13
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.
SLIDE 14
Thank You.
Questions & Answers