Program Management/Firefox/2012-Q1-Goals: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 5: | Line 5: | ||
===Minimal Impact Update=== | ===Minimal Impact Update=== | ||
* Oversee all pieces of Silent Update and changes for Add-On compatibility through release | * {{prev|Oversee all pieces of Silent Update and changes for Add-On compatibility through release}} | ||
===Web Apps Integration=== | ===Web Apps Integration=== |
Revision as of 21:42, 11 January 2012
Projects & Programs
- PM Goals and projects should directly support highest engineering and product priorities.
Desktop
Minimal Impact Update
- [CARRY OVER] Oversee all pieces of Silent Update and changes for Add-On compatibility through release
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.
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
- (TBD)
Responsiveness
- Organize and run regular Snappy meetings.
- Track responsiveness initiatives targeted for Q1 through completion.
- Asa has a list of 3 projects
- Taras has another list of 4-5 projects
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
Non Goals
- 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