Difference between revisions of "IS480 Team wiki: 2014T1 Team Epsilon Metrics Management"
(23 intermediate revisions by the same user not shown) | |||
Line 40: | Line 40: | ||
<!-- Start Content --> | <!-- Start Content --> | ||
+ | |||
+ | == '''Story Burn Up Chart''' == | ||
+ | |||
+ | [[Image: Story_Burn_Up_Chart_Epsilon.png|800px]] | ||
+ | |||
+ | This burn up chart tracks how much work has been completed and the total amount of work done by the team. | ||
+ | |||
+ | For story points breakdown per iteration, please check out our [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2014T1_Team_Epsilon_Project_Schedule User Stories, Critical Path and Acceptance Criteria] section after the project timeline. | ||
+ | |||
+ | For more information, please check out our [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2014T1_Team_Epsilon_Project_Management Methodology] section. | ||
== '''Schedule Metrics''' == | == '''Schedule Metrics''' == | ||
+ | |||
+ | <b> Absolute Days Delayed </b> | ||
+ | |||
+ | [[Image: Absolute_Days_Delayed_Epsilon_Final.png|500px]] | ||
+ | |||
+ | |||
+ | If stories cannot be completed on time, they will either be: | ||
+ | *scheduled to be done in the next iteration (timebox) OR | ||
+ | *be developed by extending the current iteration | ||
+ | |||
+ | The decision will be based on the progress of the story as well as if there are any milestones that need to be met. | ||
+ | |||
+ | [[image:Epsilon_Final_Absolute_Days_Delayed.png|800px]] | ||
+ | |||
+ | |||
+ | |||
+ | -------- | ||
+ | |||
+ | |||
+ | <b> Schedule Index </b> | ||
+ | |||
+ | [[Image: Schedule_Index_Epsilon.png|500px]] | ||
+ | |||
+ | <b> Schedule Index Guide </b> | ||
+ | |||
+ | [[Image: Schedule_Index_Guide_Epsilon.png|800px]] | ||
+ | |||
+ | <b> Schedule Index Chart </b> | ||
+ | |||
+ | [[Image: Schedule_Index_Chart_Epsilon_Final.png|800px]] | ||
+ | |||
+ | == '''Effort Metrics''' == | ||
+ | |||
+ | [[Image: Epsilon_Effort_Metric_Final.png|800px]] | ||
== '''Bug Metrics''' == | == '''Bug Metrics''' == | ||
Line 67: | Line 111: | ||
<nowiki>*</nowiki> Bug Points = (# Low Impact Bugs) + 5(# High Impact Bugs) + 10(# Critical Impact Bugs) | <nowiki>*</nowiki> Bug Points = (# Low Impact Bugs) + 5(# High Impact Bugs) + 10(# Critical Impact Bugs) | ||
− | |||
− | == ''' | + | [[image:Epsilon_Final_Bug_Metric.png|800px]] |
− | + | ||
− | + | == '''Change Log''' == | |
− | + | ||
− | + | Check out our latest [[Media: Epsilon_Final_Change_Log.pdf | Change Log]] here. | |
− | + | ||
− | + | [[image:Epsilon_Midterm_Change_Metric.png|800px]] | |
− | + | ||
− | + | == '''Product Backlog''' == | |
− | | | + | |
− | + | Check out our latest [[Media: Epsilon_Final_Product_Backlog.pdf | Product Backlog]] here. | |
− | |||
− |
Latest revision as of 03:48, 21 November 2014
Home | Project Overview | Project Management | Documentation | Team |
Methodology | Project Schedule | Metrics Management | Risk Management |
Contents
Story Burn Up Chart
This burn up chart tracks how much work has been completed and the total amount of work done by the team.
For story points breakdown per iteration, please check out our User Stories, Critical Path and Acceptance Criteria section after the project timeline.
For more information, please check out our Methodology section.
Schedule Metrics
Absolute Days Delayed
If stories cannot be completed on time, they will either be:
- scheduled to be done in the next iteration (timebox) OR
- be developed by extending the current iteration
The decision will be based on the progress of the story as well as if there are any milestones that need to be met.
Schedule Index
Schedule Index Guide
Schedule Index Chart
Effort Metrics
Bug Metrics
Severity | Description |
---|---|
Low Impact (1 point) |
Unimportant. Typo error or small user interface alignment issues. |
High Impact (5 points) |
The system runs. However, some non-critical functionalities are not working. |
Critical Impact (10 points) |
The system is down or is un-usable after a short period of time. We have to fix the bugs to continue. |
Bug Points* | Action |
---|---|
< 10 | Use the planned debugging time in the iteration. |
>= 10 | Stop current development and resolve the bugs immediately. Project Manager reschedules the project. |
* Bug Points = (# Low Impact Bugs) + 5(# High Impact Bugs) + 10(# Critical Impact Bugs)
Change Log
Check out our latest Change Log here.
Product Backlog
Check out our latest Product Backlog here.