HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2016T1 IPMAN Metrics"

From IS480
Jump to navigation Jump to search
Line 64: Line 64:
 
Sprint velocity is a measurement of the amount of work Team IPMAN has completed during each sprint and it a key metric. Velocity is calculated at the end of each sprint by summing the total points of completed user stories. Only stories that are completed at the end of the iteration are counted. Sprint Velocity shows the rate of progress of Team IPMAN.
 
Sprint velocity is a measurement of the amount of work Team IPMAN has completed during each sprint and it a key metric. Velocity is calculated at the end of each sprint by summing the total points of completed user stories. Only stories that are completed at the end of the iteration are counted. Sprint Velocity shows the rate of progress of Team IPMAN.
 
</div>
 
</div>
[[Image:IPMAN SprintVelocity.png|center|1000px]]
+
[[Image:Wiki_SprintVelocity.png|center|1000px]]
 
<br>
 
<br>
  

Revision as of 23:09, 7 September 2016

Team IPMAN Logo 1600x800.png


Team IPMAN Icon Home.png   HOME

 

Team IPMAN Icon AboutUs.png   ABOUT US

 

Team IPMAN Icon ProjectOverview.png   PROJECT OVERVIEW

 

Team IPMAN Icon ProjectManagement.png   PROJECT MANAGEMENT

 

Team IPMAN Icon ProjectDocumentation.png   DOCUMENTATION

 


IPMAN Metrics Title.png


Sprint Velocity

Sprint velocity is a measurement of the amount of work Team IPMAN has completed during each sprint and it a key metric. Velocity is calculated at the end of each sprint by summing the total points of completed user stories. Only stories that are completed at the end of the iteration are counted. Sprint Velocity shows the rate of progress of Team IPMAN.

Wiki SprintVelocity.png


Scrum Burndown Chart

The Scrum Burndown Chart is a visual measurement tool to display the amount of work completed each day against the ideal projected rate of completion for the current sprint. The purpose of this chart is to enable Team IPMAN to deliver the product within the desired schedule.

IPMAN BurndownChart Sprint7.png


Sprint 3
Sprint 4
Sprint 5
Sprint 6

Bug Metrics


IPMAN BugMetric Chart.png


Impact Score

Severity Description
Low Impact (Score: 1) Inconsequential. Simple typo error or minor user interface misalignment.
High Impact (Score: 5) Non-critical functionalities are not working, but still system runs.
Critical Impact (Score: 10) The system or core functionality is down.


Mitigation Plan

Total Score = # Bugs (Low) x 1 + # Bugs (High) x 5 + # Bugs (Critical) x 10

Bug Score Action
Score <= 10 Fix during buffer time.
10 < Score <= 20 Fix during planned debugging time in current iteration.
Score > 20 Halt current development and fix the bug(s) immediately. Reschedules if necessary.


Silhouettes wiki background IPMAN.png