Program Management/Firefox/2011-Q4-Goals: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
(10 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}}
* {{risk|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}}
** {{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==
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
* {{risk|Dashboard for managing crash landscape - incoming crash rate, fixes crash rate, per component breakdown and release to release comparison}}
* {{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===
* {{ok|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.}}
* {{ok|Improve adoption rate from current 2% on release and nightly.}}
* {{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}}
** {{not done|Battery usage}}
** {{miss|Battery usage}}
** {{done|Page load}}
** {{done|Page load}}
** {{done|Zooming}}
** {{done|Zooming}}
** {{done|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=
* {{risk|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}}
** 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.
* 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.}}
* Proposal for tracking triage of incoming bugs.
** 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}}
* {{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}}

Latest revision as of 21:18, 30 January 2012

Projects & Programs

Desktop

Electrolysis

  • [DONE] Provide management assistance running meetings
  • [DROPPED] Identify 4Q goals for project and track short term goals to completion

Silent Update

  • [DONE] Manage effort running weekly meetings
  • [DONE] Engage with Engagement, Product Management, releng, Security, and QA and keep them involved in the project
  • [MISSED] 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

Crashkill

  • [DONE] Socorro Q4 goals - features/bugs we would like to see implemented in Q4 to support the mandate of crashkill
  • [MISSED] 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

  • [DONE] Work with engineering teams to identify and implement probes for top three Blizzard questions.
  • [MISSED] Improve adoption rate from current 2% on release and nightly.

Mobile

Performance

  • Create standards of legitimacy for responsiveness tests - clear methodology and configuration for running tests.
    • [DONE] Startup path
    • [MISSED] Battery usage
    • [DONE] Page load
    • [DONE] Zooming
    • [DONE] Panning
  • [DONE] Create repeatable process for the above testing to benchmark.
  • [DROPPED] 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.
    • [DONE] Skipped over project plan and got Robotium standing up

Java UI

  • [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

  • [MISSED] 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.
  • [DROPPED] 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.
  • [MISSED] Proposal for tracking triage of incoming bugs.

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/2011-Q4-Goals&oldid=391898"