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

 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==Candice==
==Candice==
* Create burndown for 2.0 and 2.1 features in conjunction with captured team velocity and sprint metrics
* Socialize and capture sprint metrics from Productivity and Systems-Frontend
* Start weekly sprint report for Productivity and Systems-Frontend for increased visibility and communication
* Assist and share estimation best practices with other teams
* Improve dependency tracking and communication with other EPMs via new scrum of scrums in weekly sync


==Chris==
==Chris==
Line 16: Line 21:
*Pick up EPM support for games
*Pick up EPM support for games
*Help get Rust baseline and set them up for ongoing schedule tracking
*Help get Rust baseline and set them up for ongoing schedule tracking
*No new personal goal except to continue to refine time management and create more efficiency on my part; document lessons learned on how to successfully and smoothly transition projects


==Jenn==
==Jenn==
Line 32: Line 38:
* Work with Marco and Jenn to stand up remaining pieces of the Firefox Desktop process
* Work with Marco and Jenn to stand up remaining pieces of the Firefox Desktop process
** triage, product pitch meeting, demo session, backlog management tool
** triage, product pitch meeting, demo session, backlog management tool
* Work with Kyle and Sheila to create B2G dashboards to support engineering and QA activities
* Create additional Manager Hacking sessions on finance, legal, and diversity.
* Evaluate productivity survey responses and determine projects and next steps.


==Marco==
==Marco==
* Establish Desktop Triage process and teams.
* {{done|}} Transition Trial Desktop planning group into three permanent planning groups.
* Transition Trial Desktop planning group into three permanent planning groups.
* {{done|}} Implement median velocity and velocity range for use in iteration planning.
* Organize Firefox 31 & 32 demonstration sessions on Air Mozilla.
* {{done|}} Establish point based release forecasts based on team velocity range.
* Establish Point Estimation Meetings separate from Planning Meetings.
* Present median velocity and velocity range to Trial Desktop group for use in iteration planning.
* Assist Desktop Senior Management Team with developing a Release Plan.


==Martin==
==Martin==
Confirmed users
4,174

edits