HeaderSIS.jpg

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

From IS480
Jump to navigation Jump to search
Line 66: Line 66:
  
 
[[Image: Schedule_Index_Epsilon.png|500px]]
 
[[Image: Schedule_Index_Epsilon.png|500px]]
 +
 +
== '''Effort Metrics''' ==
 +
 +
[[Image: Effort_Metric_Guide_Epsilon.png|800px]]
  
 
== '''Bug Metrics''' ==
 
== '''Bug Metrics''' ==

Revision as of 10:24, 6 October 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

Schedule Metrics

Absolute Days Delayed

Absolute Days Delayed Epsilon.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.


Schedule Index Guide

Schedule Index Guide Epsilon.png

Schedule Index

Schedule Index Epsilon.png

Effort Metrics

800px

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)