Confirmed users
2,473
edits
Program Management/Firefox/2011-Q4-Goals: Difference between revisions
Program Management/Firefox/2011-Q4-Goals (view source)
Revision as of 21:18, 30 January 2012
, 30 January 2012→Telemetry
No edit summary |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
* {{done|Manage effort running weekly meetings}} | * {{done|Manage effort running weekly meetings}} | ||
* {{done|Engage with Engagement, Product Management, releng, Security, and QA and keep them involved in the project}} | * {{done|Engage with Engagement, Product Management, releng, Security, and QA and keep them involved in the project}} | ||
* {{ | * {{miss|Kill major update pain points in 4Q}} | ||
** {{done|Micro goal - have all update work items on a release train by end of 2011}}. Some of this spilled over to 2012 but I am going to declare success here. | ** {{done|Micro goal - have all update work items on a release train by end of 2011}}. Some of this spilled over to 2012 but I am going to declare success here. | ||
| Line 16: | Line 16: | ||
* {{done|Socorro Q4 goals - features/bugs we would like to see implemented in Q4 to support the mandate of crashkill}} | * {{done|Socorro Q4 goals - features/bugs we would like to see implemented in Q4 to support the mandate of crashkill}} | ||
** https://wiki.mozilla.org/CrashKill/Plan/Priorities#Q4.2F2011 | ** https://wiki.mozilla.org/CrashKill/Plan/Priorities#Q4.2F2011 | ||
* {{ | * {{miss|Dashboard for managing crash landscape - incoming crash rate, fixes crash rate, per component breakdown and release to release comparison}} | ||
** Blocked on metrics work. | ** Blocked on metrics work. | ||
* {{done|Triage process for handling new crash bugs logged}} | * {{done|Triage process for handling new crash bugs logged}} | ||
| Line 22: | Line 22: | ||
===Telemetry=== | ===Telemetry=== | ||
* {{ | * {{done|Work with engineering teams to identify and implement probes for top three Blizzard questions.}} | ||
* {{ | * {{miss|Improve adoption rate from current 2% on release and nightly.}} | ||
==Mobile== | ==Mobile== | ||
| Line 29: | Line 29: | ||
* Create standards of legitimacy for responsiveness tests - clear methodology and configuration for running tests. | * Create standards of legitimacy for responsiveness tests - clear methodology and configuration for running tests. | ||
** {{done|Startup path}} | ** {{done|Startup path}} | ||
** Battery usage | ** {{miss|Battery usage}} | ||
** {{done|Page load}} | ** {{done|Page load}} | ||
** {{done|Zooming}} | ** {{done|Zooming}} | ||
| Line 43: | Line 43: | ||
=Process= | =Process= | ||
* {{ | * {{miss|Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews}} | ||
** Did pretty well with this but goal is now end of Jan 2012. | ** Did pretty well with this but goal is now end of Jan 2012. | ||
* {{drop|Weekly, high functioning meeting where project managers and product managers get together and track the status and issues around features, programs and bugs - "Directly Responsible Individual" (DRI) meeting.} | * {{drop|Weekly, high functioning meeting where project managers and product managers get together and track the status and issues around features, programs and bugs - "Directly Responsible Individual" (DRI) meeting.}} | ||
** We weren't quite ready for this and don't have enough PMs to do this yet. | ** We weren't quite ready for this and don't have enough PMs to do this yet. | ||
* {{ | * {{miss|Proposal for tracking triage of incoming bugs.}} | ||
=General Program Management= | =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}} | * {{done|Elaborate program management related material (wiki) and continue to educate engineering teams about pm}} | ||