Program Management/Firefox/2013-Q3-Goals

Firefox Desktop

Updates

• Research issues that cause Firefox instances to stay on older versions

Firefox Android

• 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

Firefox Metro

• Total Goals: 13
• Completed Goals: 8
• Missed Goals: 0

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 Feature Stories and Defect/Change Stories have been moved to V2.
  • All new Feature Stories and Defect/Change Stories will now be triaged for inclusion as part of the Metro Preview as well as priority ranking.
• 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%
• [DONE] Conduct a second Metro Test Day by the conclusion of Q3.
  • Completed on Friday August 30 by Samvadena and Anthony from the QA Department.

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.
• [DONE] Conclude Development Iteration #12 and Deliver Release Build to Product Manager and QA Department.
  • Completed at the end of Iteration #12 on August 12.
• [DONE] Conclude Development Iteration #13 and Deliver Release Build to Product Manager and QA Department.
  • Completed at the end of Iteration #13 on August 26.
• 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.
• [DONE] Identify the 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.
  • Completed during Iteration #12 - View Metro Preview Release Backlog
• [DONE] Develop the initial development complete forecasts (expected, pessimistic and optimistic) for the Firefox Metro Preview Release.
  • Completed at the end of Iteration #12. The Metro Preview Release is scheduled for Firefox 26 - See Full Schedule

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.

Firefox OS

• TBD.

Platform

Performance

• Improve visibility into engineering performance work via reporting and change in communication tactics
• Iterate on existing project definitions and define new projects as required

Engineering Effectiveness

• Continue to iterate on engineering meeting to provide more value for engineers
• Drive creation of initial Git read-only mirror of Mozilla Central hosted and supported by Mozilla

JS

• Engage with JS team and determine how and where to support the team
• Facilitate the landing of Generational GC

Geolocation

• Review geolocation project and provide initial project definition and structure

Stability

• Move bulk of daily watching of crash stats (back) to QA
• Organize Stability Work Week
• Figure out B2G stability process (partner requirements, web tools, daily analysis, ...)

Mobile Web Compatibility

• Reinvigorate Web compatibility effort via MoCo funded staffing and community participation
• Establish compatibility measure/benchmark in order to measure progress and target effort
• Make significant headway in removing Firefox OS UA overrides
• Engage with other companies that are also investing in mobile Web compatibility

Program/Project Management

• Onboard cpeterson to team
• Create a team project backlog (active projects and unstaffed)