Program Management/Firefox/2011-Q4-Goals

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
• [AT RISK] Kill major update pain points in 4Q
  • [DONE] Micro goal - have all update work items on a release train by end of 2011

Cross Product

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
• [AT RISK] 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

• [ON TRACK] Work with engineering teams to identify and implement probes for top three Blizzard questions.
• [ON TRACK] 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
  • style="background:#ff9090; color:black; vertical-align: middle; text-align: center; " class="table-no" | Battery usage
  • [DONE] Page load
  • [DONE] Zooming
  • [DONE] Panning
• [DONE] Create repeatable process for the above testing to benchmark.
• Template:Dropped
• A project plan to retrofit automated test harnesses to be Java compliant.
  • [DONE] Skipped over project plan and got Robotium standing up

Java UI

• Project plan and schedule for development.

Process

• [AT RISK] 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.
• 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.

General Program Management

• Develop initial template/tool for managing programs consistently
• [DONE] Elaborate program management related material (wiki) and continue to educate engineering teams about pm