MozillaWiki

Program Management/Firefox/2014-Q3-Goals

< Program Management
Revision as of 15:59, 29 September 2014 by Smooney (talk | contribs)

Chris

  • Geolocation:
    • Define clear roadmap and B2G QA story.
    • Geofencing WebAPI: work with QC to write API proposal for W3C standardization.
  • e10s: Focus on add-on compatibility with organized testing and reaching out to add-on developers.
  • Shumway: define milestones and drive to enable Shumway (in Nightly) by end of Q3.
  • RR2P:
    • Test drive Trello for Geolocation and report experience: mozilla-geolocation board
    • Maybe interview engineering managers about their planning/project tools and write a report.
  • Browser Benchmark Automation:
    • Work with A-Team to build and deploy automation and reporting servers.
    • Identify Gecko teams interested in adding new benchmarks.

Erin

  • Continue to manage risk around delivering Find My Device for 2.0
  • Manage backlog for 2.1
  • Create new schedule for games delivery; manage convergence around in app payments and any graphics fixes
  • Q3 goals for games

Jenn

  • Pilot a group of tools to view the backlog for the Desktop and assess what might work - Kanbanize, Trello, ScrumWorks...
  • First stab at trying to visualize the Desktop roadmap similar to way we present the Android one. Working closely with Engineering and Product to tags but and create features buckets.
  • New template and status report for Desktop progress.

Lawrence

Goals listed under release management Q3 goals

Marco

  • Implement and evaluate V1 Desktop iteration process changes for Iteration 34.2 on Tuesday August 5:
    • Point estimation will be conducted with the whole team asynchronously.
    • Team will select bugs up to the median value of the velocity range.
    • Each planning group will have its own production cap based on the specific makeup of the group.
    • Planning meeting begins with the review, removal and/or redistribution of carry over work from the previous iteration.
    • The remaining point capacity, up to the median value of the velocity range, is used for new work on the priority list.
    • Additional work will be included in the iteration once all committed work selected in the planning meeting is at least at the review stage.
  • Aim to achieve the following performance gains based on the above mentioned process changes at the conclusion of Iteration 35.2 on September 29:
    • Improve the average percentage of verified work to 75%.
    • Reduce the average percentage of carry over work to 25%.
      • The breakdown for the 25% reduction in carry over work aims to be 5% for resolved work awaiting verification and 20% for incomplete Engineering/Design work.

Sheila

  • Fill open Program Manager req (moved to FirefoxOS)
  • Create a set of dashboards for Bob to help track Platform work and bottlenecks (In progress)
    • Figure out what we want to measure.
    • Work with Kyle to get something up and runninng.
  • Launch regular meet-ups and produce a set of short-term goals for the "Roadblocks to Productivity" initiative for standardization.
  • Work with Program Managers to explore a common way to view a teams backlog and priorities across all products; FFOS, Desktop, Android, Platform ie: pilot Trello to see if it will serve this purpose (in progress)

Shell

  • webRTC experimenting with 2 week sprints
  • Visibility:
    • Mark-up for new SCRUM tools and increase adoption
    • wiki useful and up to date, summaries.
    • weekly status reports to all stakeholders across teams (with Joanne, Helen for biz)
    • Learn scrum dashboard tools: https://trello.com/b/s8DRjWZe/talkilla
  • high pro-active collaboration with Desktop and Server in their rhythms
  • Metrics: coordinate gathering across 5 teams and exposing
  • documentation: https://wiki.mozilla.org/Media/Webrtc#Tracking_processes
Retrieved from "https://wiki.allizom.org/index.php?title=Program_Management/Firefox/2014-Q3-Goals&oldid=1019209"