Program Management/Firefox/2013-Q2-Goals

From MozillaWiki
Jump to: navigation, search

Firefox Desktop

Firefox Android

  • Hopefully hit 5 star reviews by the end of the quarter (we're close!!)
  • Effectively manage risk around features in development and going to market during Q2 (Fx21-Fx26):https://wiki.mozilla.org/Mobile/Roadmap#Features
  • Continue sending weekly status for the current channels of development
  • Spearhead use of estimations and rolling them up into gantt charts to depict timelines
  • Start PMing Shumway project
  • Officially close-out Readability 2.0
  • Ensure productization of Apps for Android and schedule/POR for Apps for Android program

Firefox Metro

  • Total Goals: 19
  • Completed Goals: 17
  • Missed Goals: 2

Project Management

  • [DONE] Develop a revised Metro Software Requirements Specification outlining a new version of the Minimum Viable Product (MVP) feature set.
    • Completed at the end of Iteration #5 on April 16. Product Manager review of V1 Release List resulted in the removal of 9 Feature Stories to V2.
  • [DONE] Conduct a review of the Story Backlog and revise the priority levels of feature stories.
    • At the conclusion of Iteration #6, the Product Manager revised the priority levels of the feature stories in the Story Backlog. The revision resulted in:
      • 30 feature stories shifted to a P1 priority level.
      • 1 feature story shifted to a P2 priority level.
      • 10 feature stories shifted to a P3 priority level.
      • 12 feature stories shifted to a P4 priority level.
  • [DONE] Develop a Pessimistic, Optimistic and Expected Release Scenario. The initial figures will be presented following the conclusion of Iteration #6 and will be updated at the conclusion of each upcoming iteration.
    • At the end of Iteration #6, the three release scenarios were as follows:
      • 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 19 iterations on March 20, 2014.
      • Optimistic Release Scenario - The average velocity figure of the best 3 iterations is 71. If this velocity figure can be achieved and maintained, then development would be completed no later than 9 iterations on October 02, 2013.
      • Expected Release Scenario - The average velocity figure from all the previous iterations is 51. If this velocity figure can be maintained, then development would be completed in 12 iterations on November 19, 2013.
    • At the end of Iteration #7, the three release scenarios were as follows:
      • 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.
    • At the end of Iteration #8, the three release scenarios were as follows:
      • 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 53. If this velocity figure can be maintained, then development would be completed in 11 iterations on November 19, 2013.
    • At the end of Iteration #9, the three release scenarios were as follows:
      • 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 - With a velocity performance of 74 development would be completed no later than 8 iterations on October 22, 2013.
      • Expected Release Scenario - With a velocity performance of 51 development would be completed in 11 iterations on December 05, 2013.
  • [DONE] Maintain 'triage' backlog at no more than 10 items at the conclusion of Q2.
    • Completed at the end of Q2 with 7 items in the backlog.
  • [DONE] Maintain 'planning' backlog at no more than 10 items at the conclusion of Q2.
    • Completed at the end of Q2 with 8 items in the backlog.
  • [DONE] Calculate a 90% confidence interval around the median velocity using a Binomial distribution. The initial figure representing the velocity range will be presented following the conclusion of Iteration #5 and will be updated at the conclusion of each upcoming iteration.
    • At the conclusion of Iteration #5, for velocity values of 30,32,33,63,75, the Metro Team has a median velocity of 33 and there is a 90% likelihood that the actual velocity will fall between 30 and 75.
    • At the conclusion of Iteration #6, for velocity values of 30,32,33,63,75,74, the Metro Team has a median velocity of 48 and there is a 90% likelihood that the actual velocity will fall between 30 and 75.
    • At the conclusion of Iteration #7, for velocity values of 30,32,33,63,75,74,68, the Metro Team has a median velocity of 63 and there is a 90% likelihood that the actual velocity will fall between 30 and 75.
    • At the conclusion of Iteration #8, for velocity values of 30,32,33,46,63,68,74,75, the Metro Team has a median velocity of 54 and there is a 90% likelihood that the actual velocity will fall between 32 and 74.
    • At the conclusion of Iteration #9, for velocity values of 30,32,33,46,51,63,68,74,75, the Metro Team has a median velocity of 51 and there is a 90% likelihood that the actual velocity will fall between 32 and 74.

Quality Management

  • [DONE] Establish QA performance metrics concerning test coverage and defects discovered.
    • The quality performance from the regression testing across Iterations #1 - #6 is as follows:
      • 87% average pass rate.
      • 13% average fail rate.
      • 73% test coverage.
    • The quality performance from the regression testing across Iterations #1 - #7 is as follows:
      • 89% average pass rate.
      • 11% average fail rate.
      • 95% test coverage.
    • The quality performance from the regression testing across Iterations #1 - #8 is as follows:
      • 90% pass rate.
      • 10% fail rate.
      • 88% test coverage.
  • [DONE] Review and revise priority level ranking definitions and their relationship to QA testing.
  • [DONE] Establish feature completeness metric concerning the number of feature stories that are 'incomplete' as outlined in the DOD.
    • At the conclusion of Iteration #8, 34% of Feature Stories are Incomplete - development finished in a previous iteration but contain blocking defects and/or change requests.
    • At the conclusion of Iteration #9, 44% of Feature Stories are Incomplete - development finished in a previous iteration but contain blocking defects and/or change requests.

Product Development

  • [DONE] Conclude Development Iteration #5 and Deliver Release Build to Product Manager and QA Department.
    • Completed at the end of Iteration #5 on April 12.
  • [DONE] Conclude Development Iteration #6 and Deliver Release Build to Product Manager and QA Department.
    • Completed at the end of Iteration #6 on April 30.
  • [DONE] Conclude Development Iteration #7 and Deliver Release Build to Product Manager and QA Department.
    • Completed at the end of Iteration #7 on May 23.
  • [DONE] Conclude Development Iteration #8 and Deliver Release Build to Product Manager and QA Department.
    • Completed at the end of Iteration #8 on June 10.
  • [DONE] Conclude Development Iteration #9 and Deliver Release Build to Product Manager and QA Department.
    • Completed at the end of Iteration #9 on June 25.

Team Performance

  • [DONE] Iteration #5 - Team completes 40 points.
    • At the conclusion of Iteration #5 the team has surpassed the goal and completed 75 story points.
  • [DONE] Iteration #6 - Team completes 45 points.
    • At the conclusion of Iteration #6 the team has surpassed the goal and completed 74 story points.
  • [DONE] Iteration #7 - Team completes 50 points.
    • At the conclusion of Iteration #7 the team has surpassed the goal and completed 68 story points.
  • [MISSED] Iteration #8 - Team completes 55 points.
    • At the conclusion of Iteration #8 the team missed the goal and completed only 46 story points.
  • [MISSED] Iteration #9 - Team completes 55 points.
    • At the conclusion of Iteration #9 the team missed the goal and completed only 51 story points.

Firefox OS

Ideas:

  • Partner goals
    • Certification pass
    • IOT pass
    • LG workflow settled
  • Schedule goals
    • 1.1 schedule completed
    • 1.2/1.3 feature roadmap published
  • Communication
    • Something about improved status reporting

Platform

Games Team

  • Manage WebAudio Rollout to be prefered on by default in Firefox 25
  • Emscripten + Ams.js games working on FirefoxOS
  • Release Epic Demo to the public
  • [DONE] Complete Mutliplayer BananaBread

Mobile Web Compatibility

  • Determine some measurement of compatibility for Firefox for Android and Firefox OS
  • Define concrete goals for the program
  • Staff MoCo team via hiring and contractors
  • Engage community on testing and outreach efforts

Quality/Performance

  • Define performance projects in terms of goals and timelines
  • Establish performance program with executive buy-in

Engineering Tools

Git Migration

  • Determine if Hg to Git migration is feasible and desirable for engineering
  • If outcome above is yes, define project plan for migrating to Git

Program/Project Management

  • Expand the team by 2 people.
Retrieved from "https://wiki.mozilla.org/index.php?title=Program_Management/Firefox/2013-Q2-Goals&oldid=672115"