Program Management/Firefox/2014-Q3-Goals: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Candice==


==Chris==
==Chris==
* Geolocation:
* Geolocation:
** Define clear roadmap and B2G QA story.
** {{miss|}} Define clear roadmap and B2G QA story.
** Geofencing WebAPI: work with QC to write API proposal for W3C standardization.
** {{defer|}} 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.
* {{done|}} 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.
* {{done|}} Shumway: define milestones and drive to enable Shumway (in Nightly) by end of Q3.
* RR2P:
* RR2P:
** Test drive Trello for Geolocation and report experience: [https://trello.com/b/TCwBhEYd/mozilla-geolocation mozilla-geolocation board]
** {{done|}} Test drive Trello for Geolocation and report experience: [https://trello.com/b/TCwBhEYd/mozilla-geolocation mozilla-geolocation board]
** Maybe interview engineering managers about their planning/project tools and write a report.
** {{drop|}} Maybe interview engineering managers about their planning/project tools and write a report.
* Browser Benchmark Automation:
* Browser Benchmark Automation:
** Work with A-Team to build and deploy automation and reporting servers.
** {{done|}} Work with A-Team to build and deploy automation and reporting servers.
** Identify Gecko teams interested in adding new benchmarks.
** {{done|}} Identify Gecko teams interested in adding new benchmarks.


==Erin==
==Erin==
Line 29: Line 28:


==Marco==
==Marco==
* Implement and evaluate V1 Desktop iteration process changes.  
* Implement and evaluate V1 Desktop iteration process changes initiated on Iteration 34.2 (Tuesday August 5):
* Implement and evaluate using data from only the latest 5 iterations for the median and velocity range.
** {{done|}} Point estimation will be conducted asynchronously with the whole team.
* '''Note:'''  Further goals will be added based on the implemented V1 Desktop iteration process changes.
** {{done|}} Establish a point cap where the whole team will select bugs up to the median value of the velocity range at the planning meeting.
 
** {{done|}} Each planning group will have its own point cap based on their own production capability.
==Michael==
** {{done|}} 'Review+' bug status will now be considered work in progress and count towards the point cap during the planning meeting.
* Successful launch of Flame and Foxtrot programs.
* Aim to achieve the following performance gains based on the above mentioned process changes at the conclusion of Iteration 35.2 (Monday September 29):
* Continue with OWDCRB meetings and tasks
** {{done|}} Reduce the average percentage of points selected by 25%.
* Launch FxOS Branding Certification with 1st device
*** Achieved:  average percentage point selection decreased by 28%.
** {{done|}} Increase the average percentage of completed work to 75%.
*** Achieved:  average percentage complete increased from 56% to 76%.
** {{done|}} Reduce the average percentage of carry over work to 25%.
*** Achieved:  average percentage carry over decreased from 44% to 24%.


==Sheila==
==Sheila==
* Fill open Program Manager req.
* Fill open Program Manager req (moved to FirefoxOS)
* Create a set of dashboards for Bob to help track Platform work and bottlenecks.
* Create a set of dashboards for Bob to help track Platform work and bottlenecks (In progress)
** Figure out what we want to measure.
** Figure out what we want to measure.
** Work with Kyle to get something up and runninng.
** 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.
* 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.
* 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==
==Shell==

Latest revision as of 22:21, 13 October 2014

Chris

  • Geolocation:
    • [MISSED] Define clear roadmap and B2G QA story.
    • [DEFER] Geofencing WebAPI: work with QC to write API proposal for W3C standardization.
  • [DONE] e10s: Focus on add-on compatibility with organized testing and reaching out to add-on developers.
  • [DONE] Shumway: define milestones and drive to enable Shumway (in Nightly) by end of Q3.
  • RR2P:
    • [DONE] Test drive Trello for Geolocation and report experience: mozilla-geolocation board
    • [DROPPED] Maybe interview engineering managers about their planning/project tools and write a report.
  • Browser Benchmark Automation:
    • [DONE] Work with A-Team to build and deploy automation and reporting servers.
    • [DONE] 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 initiated on Iteration 34.2 (Tuesday August 5):
    • [DONE] Point estimation will be conducted asynchronously with the whole team.
    • [DONE] Establish a point cap where the whole team will select bugs up to the median value of the velocity range at the planning meeting.
    • [DONE] Each planning group will have its own point cap based on their own production capability.
    • [DONE] 'Review+' bug status will now be considered work in progress and count towards the point cap during the planning meeting.
  • Aim to achieve the following performance gains based on the above mentioned process changes at the conclusion of Iteration 35.2 (Monday September 29):
    • [DONE] Reduce the average percentage of points selected by 25%.
      • Achieved: average percentage point selection decreased by 28%.
    • [DONE] Increase the average percentage of completed work to 75%.
      • Achieved: average percentage complete increased from 56% to 76%.
    • [DONE] Reduce the average percentage of carry over work to 25%.
      • Achieved: average percentage carry over decreased from 44% to 24%.

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=1024688"