HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2014T1 Team Epsilon Metrics Management"

From IS480
Jump to navigation Jump to search
 
(11 intermediate revisions by the same user not shown)
Line 44: Line 44:
  
 
[[Image: Story_Burn_Up_Chart_Epsilon.png|800px]]
 
[[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''' ==
Line 49: Line 55:
 
<b> Absolute Days Delayed </b>
 
<b> Absolute Days Delayed </b>
  
[[Image: Absolute_Days_Delayed_Epsilon.png|500px]]
+
[[Image: Absolute_Days_Delayed_Epsilon_Final.png|500px]]
  
  
Line 58: Line 64:
 
The decision will be based on the progress of the story as well as if there are any milestones that need to be met.
 
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>
 
<b> Schedule Index Guide </b>
Line 63: Line 79:
 
[[Image: Schedule_Index_Guide_Epsilon.png|800px]]
 
[[Image: Schedule_Index_Guide_Epsilon.png|800px]]
  
<b> Schedule Index </b>
+
<b> Schedule Index Chart </b>
  
[[Image: Schedule_Index_Epsilon.png|500px]]
+
[[Image: Schedule_Index_Chart_Epsilon_Final.png|800px]]
  
 
== '''Effort Metrics''' ==
 
== '''Effort Metrics''' ==
  
[[Image: Epsilon Effort Metric Latest.jpg|800px]]
+
[[Image: Epsilon_Effort_Metric_Final.png|800px]]
  
 
== '''Bug Metrics''' ==
 
== '''Bug Metrics''' ==
Line 95: 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)
  
== '''Risk Metrics''' ==
+
 
 +
[[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

Team Epsilon Logo.png.png

Home   Project Overview   Project Management   Documentation   Team

Methodology   Project Schedule   Metrics Management   Risk Management


Story Burn Up Chart

Story Burn Up Chart Epsilon.png

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

Absolute Days Delayed Epsilon Final.png


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.

Epsilon Final Absolute Days Delayed.png




Schedule Index

Schedule Index Epsilon.png

Schedule Index Guide

Schedule Index Guide Epsilon.png

Schedule Index Chart

Schedule Index Chart Epsilon Final.png

Effort Metrics

Epsilon Effort Metric Final.png

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)


Epsilon Final Bug Metric.png

Change Log

Check out our latest Change Log here.

Epsilon Midterm Change Metric.png

Product Backlog

Check out our latest Product Backlog here.