Firefox/Metro/Iteration9StatusReport: Difference between revisions

Firefox/Metro/Iteration9StatusReport (view source)

Revision as of 23:47, 26 June 2013

362 bytes removed , 26 June 2013

→‎Iteration #8 Performance

Mmucci

Confirmed users

4,174

edits

@@ Line 19: / Line 19: @@
 ** [https://bugzilla.mozilla.org/show_bug.cgi?id=841214 Triage Backlog:]  '''7''' stories for Team to review and assign to the Story Backlog or Defect/Change Backlog.
-==Iteration #8 Performance==
+==Iteration #9 Performance==
 <p> </p>
 * '''Performance Highlights'''
-** Team completed 46 story points across 21 features which resulted in a decreased average team velocity rate of 53 story points per iteration.
+** Team completed 51 story points across 19 features which resulted in a decreased average team velocity rate of 51 story points per iteration.
-** Average team velocity rate dropped 2% from the previous iteration.
+** Average team velocity rate dropped 4% from the previous iteration.
-** Despite this decline, the overall average team velocity has increased 11% from Iteration #1 - Iteration #8.
+** Despite the decline in average team velocity, point closure increased 10% from the previous iteration.
 * '''Release Highlights'''
-** The decrease in average team velocity was not sufficient enough to impact our production release forecasts and therefore no dates have changed:
+** Production release forecasts have been modified:
-*** Pessimistic Release Scenario - The average team 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.
+*** Pessimistic Release Scenario - With a velocity performance of 32 development would be completed no earlier than 17 iterations on March 06, 2014.
-*** Optimistic Release Scenario - The average team 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.
+*** Optimistic Release Scenario - With a velocity performance of 74 development would be completed no later than 8 iterations on October 22, 2013.
-*** Expected Release Scenario - The average team velocity figure from all the previous iterations is 53.  If this velocity figure can be maintained, then development would be completed in 11 iterations on November 19, 2013.
+*** Expected Release Scenario - With a velocity performance of 51 development would be completed in 11 iterations on December 05, 2013.
 * '''Quality Highlights'''
 ** At the conclusion of Iteration #8, the project's quality performance and defect levels across all iterations was: