Iteration #7 Status Report

Overall Project Performance

• From Iterations #1 - #7:
  • Total Project Story Points: 964
  • Story Points Completed: 375
  • Story Points Remaining to Completion: 589
  • Team Velocity: 54 Per Iteration
  • Iterations Remaining to Completion: 11
  • Forecasted Date to Completion: November 19, 2013
  • Total Stories Closed: 103
  • Percentage of Work Completed: 41%

• Current Backlog Status:
  • Story Backlog: 33 feature stories ready for development in upcoming iterations.
  • Defect & Change Backlog: 35 defect and change stories ready for development in upcoming iterations.
  • Planning Backlog: 7 stories for the Product Manager to review and edit for inclusion in the Story Backlog.
  • Triage Backlog: 3 stories for Team to review, relate work items to and assign point values.

Iteration #7 Performance

• Highlights
  • Team completed 68 story points across 23 features which resulted in an increased average velocity rate of 54 story points per iteration.
  • Team increased its average velocity rate performance by 5% from the previous iteration.
  • The gain in average team velocity was not sufficient enough to impact our production release forecasts and therefore no dates have changed:
    • Pessimistic Release Scenario - The average velocity figure of the worst 3 iterations is 32. If the team drops to this velocity figure, then development would be completed no earlier than 18 iterations on March 20, 2014.
    • Optimistic Release Scenario - The average velocity figure of the best 3 iterations is 72. If this velocity figure can be achieved and maintained, then development would be completed no later than 8 iterations on October 02, 2013.
    • Expected Release Scenario - The average velocity figure from all the previous iterations is 54. If this velocity figure can be maintained, then development would be completed in 11 iterations on November 19, 2013.
  • Project's quality performance and defect levels across all iterations:
    • 87% average pass rate.
    • 13% average fail rate.
    • 73% test coverage.
  • The development team is now assisting QA with testing on the project review day to help increase our test coverage.
  • Other strategies such as setting up automated testing and test days are being organized with QA to also help increase our test coverage.
  • At the conclusion of Iteration #8 we will be releasing figures on the project's feature completeness levels.

23 Total; 0 Open (0%); 2 Resolved (8.7%); 21 Verified (91.3%);

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

Upcoming Iteration

• Firefox Metro Iteration #8
  • Duration: May 28, 2013 - June 10, 2013
  • Points: 123
  • Stories: 21

21 Total; 0 Open (0%); 10 Resolved (47.62%); 11 Verified (52.38%);