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
| (23 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
==Desktop== | ==Desktop== | ||
===Electrolysis=== | ===Electrolysis=== | ||
* Provide management assistance running meetings | * {{done|Provide management assistance running meetings}} | ||
* Identify 4Q goals for project and track short term goals to completion | * {{drop|Identify 4Q goals for project and track short term goals to completion}} | ||
===Silent Update=== | ===Silent Update=== | ||
* Manage effort running weekly meetings | * {{done|Manage effort running weekly meetings}} | ||
* 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}} | ||
* Kill major update pain points in 4Q | * {{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. | |||
==Cross Product== | ==Cross Product== | ||
===Crashkill=== | ===Crashkill=== | ||
* 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. | |||
* {{done|Triage process for handling new crash bugs logged}} | |||
** Cleaned up subsets of bugs and have process for tracking incoming/outgoing. Top crashes and reproducible crashes. | |||
===Telemetry=== | ===Telemetry=== | ||
* Work with engineering teams to identify and implement probes for top three Blizzard questions. | * {{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== | ||
===Performance=== | ===Performance=== | ||
* 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. | ||
** Startup path | ** {{done|Startup path}} | ||
** Battery usage | ** {{miss|Battery usage}} | ||
** Page load | ** {{done|Page load}} | ||
** Zooming | ** {{done|Zooming}} | ||
** Panning | ** {{done|Panning}} | ||
* Create repeatable process for the above testing to benchmark. | * {{done|Create repeatable process for the above testing to benchmark.}} | ||
* Video stream capture for mobile devices set-up in engineering to get benchmarks. | * {{drop|Video stream capture for mobile devices set-up in engineering to get benchmarks.}} | ||
* A project plan to retrofit automated test harnesses to be Java compliant. | * A project plan to retrofit automated test harnesses to be Java compliant. | ||
** {{done|Skipped over project plan and got Robotium standing up}} | |||
===Java UI=== | ===Java UI=== | ||
* Project plan and schedule for development. | * {{done|Project plan and schedule for development.}} | ||
** Not a formal MS project plan but informal wiki pages up to date with schedule and dates. | |||
=Process= | =Process= | ||
* Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews. | * {{miss|Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews}} | ||
* 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. | ** 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.}} | |||
** 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= | ||
* Develop initial template/tool for managing programs consistently | * {{miss|Develop initial template/tool for managing programs consistently}} | ||
* 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}} | ||