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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 17: Line 17:
* 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===
* Plan and organize Games Summit


===Rapid Response Projects===
===Rapid Response Projects===
Line 38: Line 41:
===Responsiveness===
===Responsiveness===


===Games===
* Plan and organize Games Summit


==Mobile==
==Mobile==

Revision as of 00:22, 11 January 2012

Projects & Programs

Desktop

  • Support team in highest priority initiatives for Q1

Silent Update

  • Manage effort running weekly meetings
  • 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

  • Attend regular coordination meetings
  • Keep wiki pages/lists updated with status

Windows Metro

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

Games

  • Plan and organize Games Summit

Rapid Response Projects

  • Coordination and PM assistance for Blackhole security project.
  • Coordination and PM assistance for Search Hijacking project.
  • Craft process for rapid response project management that can be used going forward.

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 clean up of crash sub list and ongoing triage
    • Explosive crash list
    • Plugin crash list
  • Clear list of quality criteria for stability program management and tracking

Telemetry

  • (TBD)

Responsiveness

Mobile

Performance

Process

  • Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews
    • Complete interviews and reports
    • Presentation of results
    • Clear set of recommendations to implement for moving forward
    • Start piloting recommendations
    • Dashboard for measuring progress

General Program Management

  • [MISSED] Develop initial template/tool for managing programs consistently
  • [DONE] Elaborate program management related material (wiki) and continue to educate engineering teams about pm
Retrieved from "https://wiki.allizom.org/index.php?title=Program_Management/Firefox/2012-Q1-Goals&oldid=385825"