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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
=Projects & Programs=
=Projects & Programs=
* Goals should support the highest priority engineering initiatives in Q1.
* We will be involved with the following projects in Q1.


==Desktop==
==Desktop==
* Support team in highest priority initiatives for Q1
===Silent Update===
===Silent Update===
* Manage effort running weekly meetings
* Follow through on all pieces of silent update and add-on compatibility changes through release cycle.
* Engage with Engagement, Product Management, releng, Security, and QA and keep them involved in the project
* Kill major update pain points in Q1
** Follow through all pieces of silent update and add-on compatibility changes through release.


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


===Windows Metro===
===Windows Metro===
* Manage early stage project kickoff tasks and coordination
* Manage early stage project kickoff tasks and coordination.
* Hire full time PM to oversee initiative
* Hire full time PM to oversee initiative


===Games===
===Games===
* Plan and organize Games Summit
* Plan and organize Games Summit in Toronto.


===Rapid Response Projects===
===Rapid Response Projects===
* Coordination and PM assistance for Blackhole security project.
* PM assistance for Blackhole security project.
* Coordination and PM assistance for Search Hijacking project.
* PM assistance for Search Hijacking project.
* Craft process for rapid response project management that can be used going forward.
* Rotating PM help for ongoing rapid release projects.  


==Cross Product==
==Cross Product==
Line 31: Line 29:
** 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
* Dashboard for managing crash landscape - incoming crash rate, fixes crash rate, per component breakdown and release to release comparison
* Triage and clean up of crash sub list and ongoing triage
* Triage and triaging crash sub lists
** Explosive crash list
** Explosive crashes
** Plugin crash list
** Plugin crashes
* Clear list of quality criteria for stability program management and tracking
* Clear list of quality criteria for stability program management and tracking


Line 40: Line 38:


===Responsiveness===
===Responsiveness===
* Organize and run regular Snappy meetings.
* Track responsiveness initiatives targeted for Q1 through completion.


==Mobile==


==Mobile==
* Ship Fennec Native project by end of Q1
===Performance===
** 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=
==Process==
* Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews
* Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews
** Complete interviews and reports
** Complete interviews and reports
** Presentation of results
** Presentation of results to broader audience
** Clear set of recommendations to implement for moving forward
** Clear set of first recommendations to implement for better bug management
** Start piloting recommendations
** Select program to piloting recommendations
** Dashboard for measuring progress  
** 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}}

Revision as of 05:39, 11 January 2012

Projects & Programs

  • Goals should support the highest priority engineering initiatives in Q1.
  • We will be involved with the following projects in Q1.

Desktop

Silent Update

  • Follow through on all pieces of silent update and add-on compatibility changes through release cycle.

Web Apps Integration

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

Windows Metro

  • Manage early stage project kickoff tasks and coordination.
  • Hire full time PM to oversee initiative

Games

  • Plan and organize Games Summit in Toronto.

Rapid Response Projects

  • PM assistance for Blackhole security project.
  • PM assistance for Search Hijacking project.
  • Rotating PM help for ongoing rapid release projects.

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 - 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
Retrieved from "https://wiki.allizom.org/index.php?title=Program_Management/Firefox/2012-Q1-Goals&oldid=385930"