Program Management/Firefox/2013-Q1-Goals

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

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
  • [DONE] Reinstate Fx Android Program Status to convey recent accomplishments, progress of features compared to roadmap POR, and risk profile around market share initiatives
  • [DONE] Reinstate live walk-throughs to showcase features in progress
  • [DONE] Collaborate with Product to refine cadence of Product Planning weekly
  • [DONE] Fx19, Fx20
  • [MISSED] Firefox Android Work Week <== this happened without me but my real work begins, now!
MWC 2013
  • [DONE] Orchestrate delivery of all cross-functional and core-engineering technical requirements to ensure a successful Fx Android Presence at MWC 2013
  • [DONE] Converge Readability 2.0: Finalize UX, Engineering, and QA POR and resulting schedule

[DONE] Firefox Metro

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


Project Management

  • Deliver full Metro Software Requirements Specification outlining Minimum Viable Product (MVP) features.
    • [DONE] Confirmed by Product Manager During Iteration #3
  • Integrate QA within development process to test and verify stories as they are completed within an iteration.
    • [DONE] QA has been testing stories upon completion since Iteration #2.
  • Integrate QA within development process to test and verify entire release build at the end of each iteration.
    • [DONE] QA has been testing iteration release builds since Iteration #1.
  • Resolve all 'to be planned' stories so they are ready for development in upcoming iterations.
    • [MISSED] Was previously completed but a new story requiring planning was added on March 27, 2013. Will be carried over to Q2.
  • Reorganize all 'legacy' (pre Iteration #1) stories to conform to the new production framework.
    • [DONE] Confirmed by Product Manager During Iteration #2
  • Develop Expected Scenario Production Forecast.
    • [DONE] Confirmed by Project Manager During Iteration #3
  • Resolve the status of all 'legacy' (pre Iteration #1) stories to 'Fixed/Verified' status (QA test conducted and any defects resolved).
    • [DONE] Confirmed by Project Manager During Iteration #4
  • Modify all 'on hold' stories so they are ready for development in upcoming iterations.
    • [MISSED] Not completed during Q1 - 15 items remain to be resolved. Will be carried over to Q2.


Product Development

  • Migrate Metro prototype to MC-Nightly.
    • [DONE] Achieved During Iteration #2
  • Conclude Development Iteration #1 and Deliver Release Build to Product Manager and QA Department.
    • [DONE] Iteration #1 Completed
  • Conclude Development Iteration #2 and Deliver Release Build to Product Manager and QA Department.
    • [DONE] Iteration #2 Completed
  • Conclude Development Iteration #3 and Deliver Release Build to Product Manager and QA Department.
    • [DONE] Iteration #3 Completed
  • Conclude Development Iteration #4 and Deliver Release Build to Product Manager and QA Department.
    • [DONE] Iteration #4 Completed


Team Performance

  • 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.
    • [DONE] At the conclusion of Iteration #3 the team has surpassed the goal and completed 33 story points.
  • Iteration #4 - Team completes 35 points of of their committed Feature Stories.
    • [DONE] At the conclusion of Iteration #4 the team has surpassed the goal and completed 63 story points.

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