Program Management/Firefox/2013-Q3-Goals

Firefox Desktop

Product Announcements test and subsequent hand-off to Winston's team (hopefully)
Privacy and Security reviews for
Project Plan for Shumway
Manage risk for all features shipping in Fx23, Fx24
Mobile Work Week
Help manage WebRTC automation plan of attack
Check out Webmaker.org and see where I can get involved, even if is just to help test

Project Management

[DONE] Conduct a review of the Story Backlog and revise the priority levels of feature stories by the conclusion of Q3.
- Completed at the end of Iteration #11 on July 26.
- All P3 Feature Stories and Defect/Change Stories are no longer considered a blocking bug and not mandatory for a V1 release.
- All P3 Defect/Change Stories have been moved to V2.
Maintain 'planning' backlog at no more than 10 items at the conclusion of Q3.

Quality Management

Maintain quality performance indicators (across Iterations #10 - #14) at the following levels by the conclusion of Q3:
- Minimum Average Pass Rate - 89%
- Maximum Average Fail Rate - 11%
- Minimum Average Coverage Rate - 85%
Maintain the number of Defect and Change Stories yet to be related to a completed Feature Story at no more than 10% of the current Defect & Change Backlog at the conclusion of Q3.
Conduct a second Metro Test Day by the conclusion of Q3.

Product Development

[DONE] Conclude Development Iteration #10 and Deliver Release Build to Product Manager and QA Department.
- Completed at the end of Iteration #10 on July 12.
[DONE] Conclude Development Iteration #11 and Deliver Release Build to Product Manager and QA Department.
- Completed at the end of Iteration #11 on July 26.
Conclude Development Iteration #12 and Deliver Release Build to Product Manager and QA Department.
Conclude Development Iteration #13 and Deliver Release Build to Product Manager and QA Department.
Conclude Development Iteration #14 and Deliver Release Build to Product Manager and QA Department.
Conclude Development Iteration #15 and Deliver Release Build to Product Manager and QA Department.
Identify and schedule the P1 feature stories, defects and changes required for a Firefox Metro Preview Release consisting of start (top sites, bookmarks, and history), basic navigation, tabbed browsing, smooth panning, scrolling and zooming.

Team Performance

Establish a minimum median velocity of 50 (Expected Date of Completion) and an actual velocity range that falls between 46 (Pessimistic Date of Completion) and 63 (Optimistic Date of Completion) by the conclusion of Iteration #15.