Program Management/Firefox/2014-Q4-Goals

From MozillaWiki
Jump to: navigation, search

Chris

  • Firefox Desktop:
    • e10s: Drive e10s team and add-on developers to ship e10s.
    • EME: Drive media team and partners to ship EME on Windows.
    • Shumway: Drive Shumway to be enabled in Nightly for ads.
    • Shumway: Test Shumway viability for go/no-go product decision in Q1.
    • Benchmark Automation: Work with engineering teams to identify and automate relevant benchmarks.
  • Firefox OS:
    • Geolocation: Improve our geolocation QA story for Firefox OS.
    • Geolocation: Significantly increase map coverage with MozStumbler in Google Play Store and Mozilla Reps events.
  • Company All-Hands Goal:
    • Organize MozStumbler competition to map Portland.
    • Organize brainstorming session about a Platform Engineering meeting format.

Erin

Jenn

  • Develop and establish a better method of Program Level management and reporting for Fennec - feature level tracking and reporting.
  • Investigate tools to better support feature level tracking and reporting (Trello, Kanbanize, other automation)
  • Improve mapping of the roadmap features down to bug level activities that happen on a weekly basis - how are we really progressing toward those roadmap goals?
  • Create a template for a Program Level status report, and establish a regular distribution
  • All Hands Goal - find time to have a process & reporting discussion with both Karen and Jonath. What would he like to see?

Lawrence

Marco

  • Implement V2 Desktop iteration process changes initiated on Iteration 35.3 (Tuesday September 30):
    • [DONE] Iteration 35.3 Implementation - 'In Review' bug status will now be considered work in progress and count towards the point cap during the planning meeting.
    • [DONE] Iteration 36.1 Implementation - 'Landed' bug status will now be considered work in progress and count towards the point cap during the planning meeting.
    • [DONE] Iteration 36.1 Implementation - Establish new baseline velocity range (for use in determining point cap) and growth rate from Iteration 32.2 onwards when the full Desktop team was integrated into the iterative process.
  • Aim to achieve the following performance gains, based on the above process changes, across Iteration 35.3 to Iteration 37.2:
    • [DONE] Achieve an average completed work percentage from 75% to 80%.
      • Team achieved an average work completion rate of 75%.
  • Company All-Hands Goal:
    • [MISSED] Meet with another team lead interested in establishing an iterative development model.
  • Develop mitigation strategies to deal with the following known risks:
    • [DONE] Iteration 37.1 - Occurs during the company wide work week which will have an impact on performance.
      • GMC notified of production impact and decided to carry forward with IT 37.1. Minimum production capacity used to establish Release 37 goal.
    • [DONE] Iteration 37.3 - Occurs during the holiday break which will have an impact on performance.
      • GMC notified of production impact and decided to cancel IT 37.3. Iteration cycle resumes on Tuesday January 6 with IT 38.1

Sheila

  • Hire a Program Manager for Firefox Desktop.
  • Keep the Platform Backlog up to date with current status.
  • Develop a template and send out a regular Platform status report.
  • Plan a session for the Dec all-hands on Program/Project Management at Mozilla.
    • How has it evolved
    • What works well, what doesn't work well
    • What tools, processes need to be in place for use to be more effective.

Shell

Retrieved from "https://wiki.mozilla.org/index.php?title=Program_Management/Firefox/2014-Q4-Goals&oldid=1045807"