Program Management/Firefox/2013-Q2-Goals

Firefox Android

• TBD

Firefox Metro

• Total Goals: 16
• Completed Goals: 5
• Missed Goals: 0

Project Management

• Develop a revised Metro Software Requirements Specification outlining a new version of the Minimum Viable Product (MVP) feature set.
  • [DONE] 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.
• Conduct a review of the Story Backlog and revise the priority levels of feature stories.
• Develop Best Case and Worst Case Production Forecast Release Dates following the conclusion of Iteration #6.
• Maintain 'triage' backlog at no more than 10 items at the conclusion of Q2.
• Maintain 'planning' backlog at no more than 10 items at the conclusion of Q2.
• Establish a cap on the number of defect and change story points allocated to each iteration following the revision of the Minimum Viable Product (MVP) feature set to ensure the project does not deplete the contingency fund before development is complete.
  • [DONE] Completed at the end of Iteration #5 on April 16. Current Defect Contingency point value = 140 which results in a maximum of 9 defect story points per iteration. This figure will be adjusted at the end of each upcoming iteration to reflect the current state of the production release forecast.
• 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 will be updated at the conclusion of each upcoming iteration.
  • [DONE] 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.

Quality Management

• Establish QA performance metrics concerning test coverage and defects discovered.

Product Development

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

Team Performance

• Iteration #5 - Team completes 40 points of of their committed Feature Stories.
  • [DONE] At the conclusion of Iteration #5 the team has surpassed the goal and completed 75 story points.
• Iteration #6 - Team completes 45 points of of their committed Feature Stories.
• Iteration #7 - Team completes 50 points of of their committed Feature Stories.
• Iteration #8 - Team completes 55 points of of their committed Feature Stories.
• Establish a whole team and resource specific velocity ceiling if three iteration goals are missed in a row.

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
• 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.