Program Management/Firefox/2012-Q1-Goals

Projects & Programs

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

Desktop

Silent Update

• Mostly done. Follow through on all pieces of silent update and add-on compatibility changes through release cycle.
  • Continuation of weekly check-ins as necessary.

Web Apps Integration

• Organize regular meeting and cross-team check-in.
• Keep wiki pages/lists updated with status.
• Track engineering pieces for integration.

Windows Metro

• Organize initial kickoff meeting.
• Track early stage tasks and coordination in wiki and bugzilla.
• Hire full time PM to oversee initiative.

Games

• Plan and organize Games Summit in Toronto.
• Oversee Project X port.
• Maintain and track list of platform changes that are discovered as a result of industry input and those needed to support the port.
• Gather a list of external industry contacts and contributors to help advise development.

Rapid Response Projects

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

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
  • https://wiki.mozilla.org/CrashKill/Plan/Priorities#Q1.2F2012
• Dashboard for managing crash landscape - incoming crash rate, fixes crash rate, per component breakdown and release to release comparison
• Triage and triaging crash sub lists
  • Explosive crashes
  • Plugin crashes
• Clear list of quality criteria for stability program management and tracking

Telemetry

• (TBD)

Responsiveness

• Organize and run regular Snappy meetings.
• Track responsiveness initiatives targeted for Q1 through completion.

Mobile

• Ship Fennec Native project by end of Q1
  • Assemble and maintain a release checklist to track cross-functional activities
  • Sync, l10n, legal, privacy/security, amo
• 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

Process

• Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews
  • Complete interviews and reports
  • Presentation of results to broader audience
  • Clear set of first recommendations to implement for better bug management
  • Select program to piloting recommendations
  • Dashboard for measuring progress