Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
Program Management/Firefox/2013-Q4-Goals: Difference between revisions
Jump to navigation
Jump to search
Program Management/Firefox/2013-Q4-Goals (view source)
Revision as of 18:39, 2 December 2013
, 2 December 2013→KaiRo
m (→Chris) |
(→KaiRo) |
||
| Line 29: | Line 29: | ||
==KaiRo== | ==KaiRo== | ||
* Determine overall efficiency of the stability program (via {{bug|915438}}) | * Determine overall efficiency of the stability program (via {{bug|915438}}) | ||
** Have some "hand-crafted" data collection and graphs available as a prototype, on overall crash rates on release/beta over the last two years (desktop) or "the beginning of time" (for Android native). | |||
** Did some analysis on that data, it's mostly within expectations. | |||
* Establish short- and long-term goals and priorities for stability based on [[CrashKill/StabilityWeek2013|Stability Week]] results | * Establish short- and long-term goals and priorities for stability based on [[CrashKill/StabilityWeek2013|Stability Week]] results | ||
** Pushed back to end of quarter to free time for getting into FHR. | |||
* Make sure basic needs for B2G analysis are met in Socorro and partner processes follow our stability analysis requirements | * Make sure basic needs for B2G analysis are met in Socorro and partner processes follow our stability analysis requirements | ||
** After a number of investigations, found out that this requires {{bug|928051}}. Got this on the plans for the Web Engineering (Socorro) team. | |||
* Expand personal PM role and skills (strategic planning, communication) | * Expand personal PM role and skills (strategic planning, communication) | ||
** Mostly learning on the job, also did some reading up on development methodologies. | |||
* Make FHR into an actual project, figure out its PM needs and next steps to take there | * Make FHR into an actual project, figure out its PM needs and next steps to take there | ||
** Gathered information on involved people and teams, ongoing projects and status. | |||
** Started to write up public info into a [[FHR|wiki page]]. | |||
** Took part in some meetings and conversations to drive projects forward, including one case to get a feature unstuck in process and landed into code (L10n of the Android front-end). | |||
==Lawrence== | ==Lawrence== | ||