HeaderSIS.jpg

IS480 Team wiki: 2015T1 4Sight Schedule Metrics

From IS480
Jump to navigation Jump to search
4Sight team logo.png
4Sight Home.png HOME   4Sight Team.png ABOUT US   4Sight Project overview.png PROJECT OVERVIEW   4Sight Project management.png PROJECT MANAGEMENT   4Sight Documentation.png DOCUMENTATION  
Project Schedule Software Development Methodologies Schedule Metrics Task Metrics Bug Metrics Risk Management Change Management


Schedule Metric

4Sight ScheduleMetric.png


Schedule Metric Score & Description

4Sight FinalScheduleMetricScore.JPG
Sprint Estimated no. of days Actual no. of days Metric Score Description
0 12 12 1.00 Project schedule is on track. No action required.
1 12 12 1.00 Project schedule is on track. No action required.
2 12 12 1.00 Project schedule is on track. No action required.
3 12 12 1.00 Project schedule is on track. No action required.
4 12 12 1.00 Project schedule is on track. No action required.
5 12 13 0.92 Slight delay in project schedule.
Team consumed a buffer day to complete all tasks scheduled for this sprint.
The delay occurred when our team was deploying our web application to heroku.
6 12 12 1.00 Project schedule is on track. No action required.
7 12 14 0.86 Slight delay in project schedule.
Team consumed additional two buffer days to complete most of the tasks scheduled for this sprint.
The delay was caused by the tasks in the notification module. Many of the SMS service providers do not provide two way SMS for local numbers. Even if they do, the trail account given to us does not provides two way SMS service. As a result, we were unable to test for the swapping of appointments via SMS. In addition, our progress was to some extent, dependent on the vendors as well since we have to liaise with them on the API and trail accounts in order to build the application and set up the necessary configuration.
Overdue tasks are scheduled for sprint 8 as our team has enough capacity.
8 12 13 0.82 Slight delay in project schedule.
Team consumed a buffer day due to some technical difficulties faced in getting the web socket implementation up on heroku.
9 12 12 1.00 Project schedule is on track. No action required.
10 12 12 1.00 Project schedule is on track. No action required.
11 12 14 0.86 Slight delay in project schedule.
Team consumed two buffer days to complete most of the tasks scheduled for this sprint.
The delay was due to the poor estimation of the hours required in completing the scheduled tasks as the team had underestimated the complexity of the customization of settings feature as part of the admin module. A lot of time was spent on refactoring codes in the admin module and modularizing it to make it more dynamic and flexible.
12 12 14 0.86 Slight delay in project schedule.
Team consumed two buffer days to complete tasks scheduled for this sprint.
Some of the customization of setting feature tasks were carried forward to this sprint, causing a delay in the tasks that were originally scheduled for this sprint.