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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 13: Line 13:
===Windows Metro===
===Windows Metro===
* ?? not sure if there are goals here - lower priority
* ?? not sure if there are goals here - lower priority
* Track early stage tasks and coordination in wiki and bugzilla.
* Hire full time PM to oversee initiative.


===Games===
===Games===


 
===Telemetry===
===Responsiveness===
* {{done|Organize and run regular Snappy meetings.}}
* {{done|Track responsiveness initiatives targeted for Q1 through completion.}}
** Asa has a list of 3 projects
** Taras has another list of 4-5 projects


===Rapid Response Projects===
===Rapid Response Projects===
* Provide rotating PM point for ongoing projects.
* Drive the team to a proposed design for Search Hijacking project.
* PM assignee for Search Hijacking project.
* {{drop|PM assignee for Blackhole project.}}


==Mobile==
==Mobile==
* Ship Fennec Native project by end of Q1
* Ship Fennec Native 1.0
** Assemble and maintain a release checklist to track cross-functional activities throughout release (Sync, l10n, legal, privacy/security, amo)
** Track burn down to release
** Weekly status summaries
** Weekly status summaries
** Organize and run the weekly mobile showcase.
** Organize and run the weekly mobile showcase.
* Plan for MWC
** Final release signoff
** Capture MWC demo plan, schedule and HW requirements.
* Document clear Beta and Release shipping criteria for Native Fennec 1.0.
* Initial plan for Native Fennec 12, 13 and 14


==Cross Product==
==Cross Product==
===Crashkill===
===Crashkill===
* Track Socorro Q1 goals - features/bugs we would like to see implemented in Q1 to support the mandate of crashkill and needs in engineering
* Track Socorro Q2 goals  
** https://wiki.mozilla.org/CrashKill/Plan/Priorities#Q1.2F2012
* Dashboard for managing crash landscape - showing incoming crash rate, fixes crash rate, per component breakdown, top crashes, reproducible crashes and release to release comparisons
* 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
* Triage and cleanup of crash sub lists
** Explosive crashes
** Plugin crashes
* Clear list of quality criteria for stability program management and tracking
===Telemetry===
* {{prev|Improve adoption rate from current 2% on release and nightly.}}
* {{done|Enable Telemetry on mobile native UI}}
* {{defer|Improve Telemetry adoption on mobile}}
* {{done|Improve consumability of Telemetry front-end (dashboard)}}
** Dashboard released publicly with improved short URL. Further work required in Q2.


=Process=
=Process=
* Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews
* Design of dashboards for tracking quality metrics
** Complete interviews and reports - all data published on the wiki.
* Presentation of bugzilla anthropology results
** Presentation summarizing the results
** Clear set of first recommendations to implement for better bug management
** Identify 2 programs/projects to pilot recommendations


=Other=
=Other=
* Hire 2 more program/project managers
* Hire 1-2 more program/project managers
* {{done|Drive mediawiki-bugzilla through to deployment}}

Revision as of 04:02, 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

Windows Metro

  • ?? not sure if there are goals here - lower priority

Games

Telemetry

Rapid Response Projects

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

Mobile

  • Ship Fennec Native 1.0
    • Track burn down to release
    • Weekly status summaries
    • Organize and run the weekly mobile showcase.
    • Final release signoff

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