Program Management/Firefox/2013-Q4-Goals: Difference between revisions

Revision as of 22:31, 16 October 2013

JS: Increase visibility of JS team progress with a 12-month roadmap, monthly status reports for management, and a more informative JS home page on wiki.mo.
e10s: Work with vlad/billm/dvander to create a Q4/Q1 roadmap, drive dependencies on other teams, and share monthly status reports.
WBGP (Tom's Hardware's Web Browser Grand Prix): Work with naveed/jandem to track and optimize WBGP benchmark performance.
Geolocation: Complete Legal and Privacy reviews so the project can announce itself and work with Mozillian and WiFi stumbling communities.
Developer Productivity: Gather productivity suggestions, create a prioritized list of actionable items, and contact teams that would implement the highest priority items.
Personal Development: TBD

Ensure we're on the road to a performance-defensive environment for Firefox OS. (Need more detail here)
Do a "people" post, introducing the players and teams involved in FxOS performance.
All FxOS functional teams using team keywords and target milestones for identification of current work (shared with all other FxOS EPMs).
Finish MVP items for http://people.mozilla.org/~dietrich/board/board.html.
Complete the contribution path metrics

Achieve M1 goals for Shumway, get it landed into Nightly (done), and get roadmap together for M2 (desktop, mobile, games); roll engineering status into weekly platform meeting
UX plan/build shared vision for Shumway
Evaluate needs for Mobile platform team (blassey) and come up with a gameplan/workflow
Start to help maire out with Web Audio
Start to publish weekly status via blog

Determine overall efficiency of the stability program (via bug 915438)
Establish short- and long-term goals and priorities for stability based on Stability Week results
Make sure basic needs for B2G analysis are met in Socorro and partner processes follow our stability analysis requirements
Expand personal PM role and skills (strategic planning, communication)
Make FHR into an actual project, figure out its PM needs and next steps to take there

Increase visibility of mobile Web compat project
Increase non performance team participation in performance program (layout, network, b2g perf, etc.)
Wrap up Summit with debriefs and work with facilitators to publish next steps
Complete Q4 staff related activities (reviews, hiring, new reqs) for program management and mobile Web compat teams
Learn about story structure and how to tell an effective story (follow-up from Tribe session #3)

Release Metro on Firefox 27 Aurora on October 29.
Release Metro on Firefox 27 Beta on December 10.
Conclude Development Iterations #16 - #21 and Deliver Release Builds to Product Manager and QA Department for review.

@@ Line 15: / Line 15: @@
 * All FxOS functional teams using team keywords and target milestones for identification of current work (shared with all other FxOS EPMs).
 * Finish MVP items for http://people.mozilla.org/~dietrich/board/board.html.
+* Complete the contribution path metrics
 ==Erin==