Program Management/Firefox/2012-Q2-Goals: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 25: Line 25:
** Weekly status: risk evaluation and mitigation
** Weekly status: risk evaluation and mitigation
** Final release plan  
** Final release plan  
Roadmap Planning Support
Road Map Planning Support
** Themes
** Themes
** Scope
** Timeline
===B2G & Gaia===
* Converge M2.5
* Schedule for M3
* Feature Tracking and Status
* Engage with TF counterparts
* Gaia v1.0
** Scope
** Scope
** Schedule
** Schedule
** Weekly UX Review


==Cross Product==
==Cross Product==

Revision as of 04:26, 29 March 2012

Projects & Programs

  • PM Goals and projects should directly support highest engineering and product priorities.

Desktop

Minimal Impact Update

  • Oversee all pieces of Silent Update through release
    • Windows security (UAC) landed in FF12, background updates will either land in 1Q or in the first week of 2Q

Killimanjaro

  • Dashboard for tracking burn down
  • Draft project charter

Games

Telemetry

Rapid Response Projects

  • Drive the team to a proposed design for Search Hijacking project.

Mobile

Firefox for Android

  • Ship Fennec Native 1.0
    • Track burn down to release
    • Weekly status: risk evaluation and mitigation
    • Final release plan
  • Road Map Planning Support
    • Themes
    • Scope
    • Timeline

B2G & Gaia

  • Converge M2.5
  • Schedule for M3
  • Feature Tracking and Status
  • Engage with TF counterparts
  • Gaia v1.0
    • Scope
    • Schedule
    • Weekly UX Review

Cross Product

Crashkill

  • Track Socorro Q2 goals
  • Dashboard for managing crash landscape - showing incoming crash rate, fixes crash rate, per component breakdown, top crashes, reproducible crashes and release to release comparisons
  • Triage and cleanup of crash sub lists

Process

  • Design of dashboards for tracking quality metrics
  • Presentation of bugzilla anthropology results

Other

  • Hire 1-2 more program/project managers