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

Revision as of 05:27, 16 July 2014

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.

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

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.

Implement and evaluate V1 Desktop iteration process changes.
Implement and evaluate using data from only the latest 5 iterations for the median and velocity range.
Note: Further goals will be added based on the implemented V1 Desktop iteration process changes.

Fill open Program Manager req.
Create a set of dashboards for Bob to help track Platform work and bottlenecks.
- 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.

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

@@ Line 43: / Line 43: @@
 ** Figure out what we want to measure.
 ** Work with Kyle to get something up and runninng.
-* Launch regular meet-ups with "Roadblocks to Productivity" working group to tackle standardization initiatives.
+* 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.