HeaderSIS.jpg

IS480 Team wiki: 2015T6 6nificance Metrics

From IS480
Jump to navigation Jump to search

6nificance Logo.png

6nificance-home.png
HOME

6nificance-about-us.png
ABOUT US

6nificance-proj-overview.png
PROJECT OVERVIEW

6nificance-proj-mgmt.png
PROJECT MANAGEMENT

6nificance-docs.png
DOCUMENTATION

Project Schedule Metrics Risks Change Management


SCHEDULE METRICS TASK METRICS BUG METRICS


What: Schedule metrics are used to measure the progress of project.
When: It is measured at the end of each iteration.
How: Planned number of days/Actual number of days

Score Action
SM <= 0.9 Team is behind the schedule. Effort required to complete is under-estimated.
  1. Inform Supervisor
  2. Re-estimate tasks for future iterations
  3. Deduct the number of days behind schedule from buffer days
  4. If there is no more buffer day, decide the functionalities to drop
0.9 < SM <= 1.1 Estimates are fairly accurate and team is on schedule.
SM > 1.1 Team is ahead of schedule. Effort required to complete is over-estimated.
  1. Inform Supervisor
  2. Re-estimate tasks for future iterations
  3. Add the number of days gained to buffer days


Schedule Metrics Results


6nificanceScheduleMetric.PNG


Summary of Schedule Metrics

Iteration Planned Duration (Days) Actual Duration (Days) Schedule Metric Score Action Taken Status
1 14 23 0.61 More time needed to apply new concepts of android development, Google Cloud Services and Facebook login.
More time also needed to debug identified bugs of high impact during testing.

Follow up action: Informed supervisor about delay. Re-scheduled the dates and tasks of iterations 2, 3 and 4. More coders have also been temporarily deployed and a temporary job roles swap has been made until Acceptance Presentation.

Completed
2 12 14 0.86 More time needed to complete the detect photo color function of Design Module as well as optimizing UI development for Design Module to include RGB sliders.

Follow up action: Informed supervisor about delay. Re-scheduled the dates and tasks of iterations 3 and 4. Reduced duration of iteration 3 and 4 from 10 days to 9 days.

Completed
3 9 9 1.00 Estimates are generally accurate and on track. Proceed as per normal. Completed
4 9 9 1.00 Estimates are generally accurate and on track. Proceed as per normal. Completed
5 14 16 0.88 More time needed to complete Update Profile function due to difficulties with uploading images to cloud database.

Follow up action: Informed supervisor about delay. Re-scheduled the dates and tasks of iteration 6. Reduced duration of iteration 6 from 14 days to 12 days. More coding hours per day were allocated in iteration 6.

Completed
6 12 14 0.86 More time needed to research and complete Social Module due to complexity with creating a new social media platform from scratch.

Follow up action: Informed supervisor about delay. Re-scheduled the dates and tasks of iteration 7. Removed 2 buffer days in iteration 8.

Completed
7 14 16 0.88 More time needed to debug bugs found in newsfeed and view color hashtag of social module

Follow up action: Informed supervisor about delay. Reduced duration of iteration 8 from 9 days to 7 days.

Completed
8 7 7 1.00 Estimates are generally accurate and on track. Proceed as per normal. Completed
9 17 19 0.89 More time needed to optimize loading speed of images and sorting color algorithm

Follow up action: Informed supervisor about delay. Reduced duration of iteration 10 from 14 days to 12 days.

Completed
10 12 13 0.92 Estimates are generally accurate and on track. Proceed as per normal.
Completed
11 14 14 1.00 Estimates are generally accurate and on track. Proceed as per normal.
Completed