Firefox/Metro/Iteration10StatusReport

Iteration #10 Status Report

Overall Project Performance

• From Iterations #1 - #10:
  • Total Project Story Points: 1,003
  • Story Points Completed: 547
  • Story Points Remaining to Completion: 456
  • Team Velocity: 57 Per Iteration
  • Iterations Remaining to Completion: 9
  • Forecasted Date to Completion of Development: November 25, 2013
  • Total Stories Closed: 169
  • Percentage of Work Completed: 55%

• Current Backlog Status:
  • Story Backlog: 31 feature stories ready for development in upcoming iterations.
  • Defect & Change Backlog: 56 defect and change stories ready for development in upcoming iterations.
  • Planning Backlog: 9 stories for the Product Manager to review and edit for inclusion in the Story Backlog.

Iteration #10 Performance

• Performance Highlights
  • Team completed 75 story points across 30 features which resulted in an increased average team velocity of 57 story points per iteration.
  • Average team velocity rate increased 11% from the previous iteration.
  • Increase in average team velocity caused the Forecasted Date to Completion of Development to contract by 1 iteration to November 25.
  • Point closure increased 47% from the previous iteration.

• Release Highlights
  • At the conclusion of Iteration #10, given the historical velocity performance values of 30,32,33,46,51,63,68,74,75,75, the Metro Team has a median velocity of 57 and there is a 90% likelihood that the actual velocity will fall between 32 and 75.
    • Pessimistic Release Scenario - With a velocity performance of 32 development would be completed no earlier than 15 iterations on February 26, 2014.
    • Expected Release Scenario - With a velocity performance of 57 development would be completed in 9 iterations on November 25, 2013.
    • Optimistic Release Scenario - With a velocity performance of 75 development would be completed no later than 7 iterations on October 28, 2013.

• Quality Highlights
  • The quality performance from the regression testing across Iterations #1 - #9 is as follows:
    • 88% pass rate.
    • 12% fail rate.
    • 100% test coverage.

• Feature Completeness Highlights
  • At the conclusion of Iteration #10, 44% of Feature Stories are Incomplete - development finished in a previous iteration but contain blocking defects and/or change requests.
  • 14% of the current Defect & Change Backlog has yet to be related to a completed Feature Story.

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 406 [1] => Not Acceptable ) ) 1

Iteration Performance History

Iteration #1: View Backlog

• Story Points Completed = 30
• Stories Completed = 5
• Team Velocity: 30 Per Iteration

Iteration #2: View Backlog

• Story Points Completed = 32
• Stories Completed = 6
• Team Velocity: 32 Per Iteration

Iteration #3: View Backlog

• Story Points Completed = 33
• Stories Completed = 10
• Team Velocity: 32 Per Iteration

Iteration #4: View Backlog

• Story Points Completed = 63
• Stories Completed = 14
• Team Velocity: 40 Per Iteration

Iteration #5: View Backlog

• Story Points Completed = 75
• Stories Completed = 25
• Team Velocity: 47 Per Iteration

Iteration #6: View Backlog

• Points Completed: 74
• Stories Completed: 20
• Team Velocity: 51 Per Iteration

Iteration #7: View Backlog

• Points Completed: 68
• Stories Completed: 23
• Team Velocity: 54 Per Iteration

Iteration #8: View Backlog

• Points Completed: 46
• Stories Completed: 21
• Team Velocity: 53 Per Iteration

Iteration #9: View Backlog

• Points Completed: 51
• Stories Completed: 15
• Team Velocity: 51 Per Iteration

Iteration #10: View Backlog

• Points Completed: 75
• Stories Completed: 30
• Team Velocity: 57 Per Iteration

Upcoming Iteration

• Iteration #11: July 15, 2013 - July 26, 2013
• View Sprint Backlog