Program Management/Firefox/2013-Q1-Goals

Firefox Desktop

• Ship FHR in Fx20 GA.
• Define and execute performance projects for start-up and shutdown (Snappy)
• Define and drive implementation of performance metrics
• Support elaboration of platform technical roadmap

Firefox Android

Features, Releases, and Roadmap

• Reinstate Fx Android Program Status to convey recent accomplishments, progress of features compared to roadmap POR, and risk profile around market share initiatives
• Reinstate live walk-throughs to showcase features in progress
• Collaborate with Product to refine cadence of Product Planning weekly
• Firefox Android Work Week
• Fx19, Fx21

MWC 2013

• Orchestrate delivery of all cross-functional and core-engineering technical requirements to ensure a successful Fx Android Presence at MWC 2013
• Converge Readability 2.0: Finalize UX, Engineering, and QA POR and resulting schedule

Firefox Metro

Q1-2013

Requirements Management

• Deliver full Metro Software Requirements Specification outling Minimum Viable Product (MVP) features.
• Reorganize all 'legacy' (pre Iteration #1) bugs and use cases to conform to the new production framework.
  • [DONE] Achieved During Iteration #2
• Resolve the status of all 'legacy' (pre Iteration #1) bugs and use cases to 'Fixed/Verified' status (QA test conducted and any defects resolved).
• Develop and execute test cases for all 'legacy' (pre Iteration #1) bugs and use cases and create new Defect Stories.

Scheduling

• Develop forecast schedule model for the following:
  • Total value of project story points to complete the project.
  • Total number of iterations to complete the project.
  • Aurora Build Release date.
  • Beta Build Release date.
  • Public Launch Release date.

Product Development

• Migrate Metro prototype to MC-Nightly.
  • [DONE] Achieved During Iteration #2
• Conclude four development Iterations and deliver MVP vertical-slice Iteration builds to Product Manager and QA Department.
  • [DONE] Iteration #1 Completed
  • [DONE] Iteration #2 Completed

Team Performance

• Scale team Iteration performance as follows (based on a forecast of 100 story points per Iteration):
  • Iteration #1
    • Team completes 20 points of of their committed Feature Stories.
      • [DONE] At the conclusion of Iteration #1 the team has surpassed the goal and completed 30 story points.
  • Iteration #2
    • Team completes 25 points of of their committed Feature Stories.
      • [DONE] At the conclusion of Iteration #2 the team has surpassed the goal and completed 32 story points.
  • Iteration #3
    • Team completes 30 points of of their committed Feature Stories.
  • Iteration #4
    • Team completes 35 points of of their committed Feature Stories.

Firefox OS

Q1-2013

• Deliver to FFOS Roadmap
  • FFOS v1 Code Freeze early January
  • FFOS Shira Code Freeze February
  • FFOS Leo Code Freeze
• Partner Communication Plan
  • RACI or Actor profiles identifying R&R for Mozilla plus Partners
  • Cross-organizational alignment on communication plan

Q2-2013

• Deliver to FFOS Roadmap
  • FFOS v1.0 Launch with TEF & ZTE Q2
  • FFOS v1.x (Shira) Launch with DT & TCL Q2
  • FFOS v1.x (Leo) Launch with TEF & LG Q3

Mobile Web Compatibility

• Define measurable compatibility projects for 2013
• Hire 2-3 technical/evangelism resources
• Drive Webkit aliasing research

Program/Project Management

• Expand team by 3 people