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

From MozillaWiki
Jump to navigation Jump to search
(Created page with "=Projects & Programs= ==Desktop== * Support team in highest priority initiatives for Q1 ===Silent Update=== * Manage effort running weekly meetings * Engage with Engagement, Pr...")
 
 
(48 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=Projects & Programs=
=Projects & Programs=
* PM Goals and projects should directly support highest engineering and product priorities.


==Desktop==
==Desktop==
* Support team in highest priority initiatives for Q1


===Silent Update===
===Minimal Impact Update===
* Manage effort running weekly meetings
* {{defer|Oversee all pieces of Silent Update through release}}
* Engage with Engagement, Product Management, releng, Security, and QA and keep them involved in the project
** Windows security (UAC) landed in FF12, background updates will either land in 1Q or in the first week of 2Q
* Kill major update pain points in Q1
* {{done|Oversee Add-On compatibility through release}}
** Follow through all pieces of silent update and add-on compatibility changes through release.


===Web Apps Integration===
===Web Apps Integration===
* Attend regular coordination meetings
* {{drop|Organize regular meeting and cross-team check-in.}}
* Keep wiki pages/lists updated with status
* {{done|Keep wiki pages/lists updated with status.}}
* {{done|Track engineering pieces for integration.}}


==Windows Metro===
===Windows Metro===
* Manage early stage project kickoff tasks and coordination
* {{defer|Organize initial kickoff meeting}}.
* Hire full time PM to oversee initiative
* {{defer|Track early stage tasks and coordination in wiki and bugzilla}}.
* {{defer|Hire full time PM to oversee initiative}}.
 
===Games===
* {{done|Plan and organize Games Summit in Toronto}}.
* {{done|Oversee Project X}}.
* {{done|Maintain and track list of platform changes that are discovered as a result of industry input and those needed to support Project X}}.
* {{done|Gather a list of external industry contacts and contributors to help advise development}}.
 
===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===
* {{done|Provide rotating PM point for ongoing projects}}.
* {{done|PM assignee for Search Hijacking project}}.
** Actual project got pushed out.
* {{drop|PM assignee for Blackhole project.}}
 
==Mobile==
* {{risk|Ship Fennec Native project by end of Q1}}
** {{done|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.
* {{done|Plan for MWC}}
** Capture MWC demo plan, schedule and HW requirements.
* {{done|Document clear Beta and Release shipping criteria for Native Fennec 1.0.}}
* {{defer|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
* {{done|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
** 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
* {{defer|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 clean up of crash sub list and ongoing triage
* {{done|Triage and cleanup of crash sub lists}}
** Explosive crash list
** Reproducible crashes
** Plugin crash list
** Plugin crashes
* Clear list of quality criteria for stability program management and tracking
* {{done|Clear list of quality criteria for stability program management and tracking}}


===Telemetry===
===Telemetry===
* (TBD)
* {{defer|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.


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


===Games===
=Other=
* Plan and organize Games Summit
* {{defer|Hire 2 more program/project managers}}
* {{done|Drive mediawiki-bugzilla through to deployment}}


==Mobile==
=Stuff not included=
===Performance===
* List of projects that have requested PM help but are not on the list or staffed...
 
** Browser ID
=Process=
** Taking a picture feature
* Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews
** Sync (help with integration/tracking in general)
** Complete interviews and reports
** Memshrink
** Presentation of results
** New UI
** Clear set of recommendations to implement for moving forward
** Start piloting recommendations
** Dashboard for measuring progress
=General Program Management=
* {{miss|Develop initial template/tool for managing programs consistently}}
* {{done|Elaborate program management related material (wiki) and continue to educate engineering teams about pm}}

Latest revision as of 07:39, 18 March 2013

Projects & Programs

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

Desktop

Minimal Impact Update

  • [DEFER] 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
  • [DONE] Oversee Add-On compatibility through release

Web Apps Integration

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

Windows Metro

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

Games

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

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

  • [DONE] Provide rotating PM point for ongoing projects.
  • [DONE] PM assignee for Search Hijacking project.
    • Actual project got pushed out.
  • [DROPPED] PM assignee for Blackhole project.

Mobile

  • [AT RISK] Ship Fennec Native project by end of Q1
    • [DONE] 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.
  • [DONE] Plan for MWC
    • Capture MWC demo plan, schedule and HW requirements.
  • [DONE] Document clear Beta and Release shipping criteria for Native Fennec 1.0.
  • [DEFER] Initial plan for Native Fennec 12, 13 and 14

Cross Product

Crashkill

  • [DONE] Track Socorro Q1 goals - features/bugs we would like to see implemented in Q1 to support the mandate of crashkill and needs in engineering
  • [DEFER] Dashboard for managing crash landscape - showing incoming crash rate, fixes crash rate, per component breakdown, top crashes, reproducible crashes and release to release comparisons
  • [DONE] Triage and cleanup of crash sub lists
    • Reproducible crashes
    • Plugin crashes
  • [DONE] Clear list of quality criteria for stability program management and tracking

Telemetry

  • [DEFER] 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
    • [ON TRACK] Complete interviews and reports - all data published on the wiki.
    • [DEFER] Presentation summarizing the results
    • [DONE] Clear set of first recommendations to implement for better bug management
    • [DEFER] Identify 2 programs/projects to pilot recommendations

Other

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

Stuff not included

  • List of projects that have requested PM help but are not on the list or staffed...
    • Browser ID
    • Taking a picture feature
    • Sync (help with integration/tracking in general)
    • Memshrink
    • New UI
Retrieved from "https://wiki.allizom.org/index.php?title=Program_Management/Firefox/2012-Q1-Goals&oldid=637811"