Program Management/Firefox/2012-Q2-Goals

From MozillaWiki
Jump to navigation Jump to search

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
  • Track early stage tasks and coordination in wiki and bugzilla.
  • Hire full time PM to oversee initiative.

Games

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

  • Provide rotating PM point for ongoing projects.
  • PM assignee for Search Hijacking project.
  • [DROPPED] PM assignee for Blackhole project.

Mobile

  • Ship Fennec Native project by end of Q1
    • Assemble and maintain a release checklist to track cross-functional activities throughout release (Sync, l10n, legal, privacy/security, amo)
    • Weekly status summaries
    • Organize and run the weekly mobile showcase.
  • Plan for MWC
    • 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

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
  • 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
    • Explosive crashes
    • Plugin crashes
  • Clear list of quality criteria for stability program management and tracking

Telemetry

  • [CARRY OVER] 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

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

Other

  • Hire 2 more program/project managers
  • [DONE] Drive mediawiki-bugzilla through to deployment