Confirmed users
4,160
edits
Program Management/Firefox/2013-Q3-Goals: Difference between revisions
Program Management/Firefox/2013-Q3-Goals (view source)
Revision as of 04:57, 27 September 2013
, 27 September 2013→Firefox Metro
| (29 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
==Firefox Desktop== | ==Firefox Desktop== | ||
* | ;Updates | ||
* Research issues that cause Firefox instances to stay on older versions | |||
==Firefox Android== | ==Firefox Android== | ||
* | * Product Announcements test and subsequent hand-off to Winston's team (hopefully) | ||
* Privacy and Security reviews for | |||
* Project Plan for Shumway | |||
* Manage risk for all features shipping in Fx23, Fx24 | |||
* Mobile Work Week | |||
* Help manage WebRTC automation plan of attack | |||
* Check out Webmaker.org and see where I can get involved, even if is just to help test | |||
==Firefox Metro== | ==Firefox Metro== | ||
<p> </p> | <p> </p> | ||
* '''Total Goals:''' | * '''Total Goals:''' 13 | ||
* '''Completed Goals:''' | * '''Completed Goals:''' 11 | ||
* '''Missed Goals:''' | * '''Missed Goals:''' 2 | ||
<p> </p> | <p> </p> | ||
'''Project Management''' | '''Project Management''' | ||
* Conduct a review of the Story Backlog and revise the priority levels of feature stories by the conclusion of Q3. | * '''{{done|}}'''Conduct a review of the Story Backlog and revise the priority levels of feature stories by the conclusion of Q3. | ||
* | ** Completed at the end of Iteration #11 on July 26. | ||
** All P3 Feature Stories and Defect/Change Stories are no longer considered a blocking bug and not mandatory for a V1 release. | |||
** All P3 Feature Stories and Defect/Change Stories have been moved to V2. | |||
** All new Feature Stories and Defect/Change Stories will now be triaged for inclusion as part of the Metro Preview as well as priority ranking. | |||
<p> </p> | <p> </p> | ||
'''Quality Management''' | '''Quality Management''' | ||
* Maintain quality performance indicators (across Iterations #10 - #14) at the following levels by the conclusion of Q3: | * '''{{miss|}}'''Maintain quality performance indicators (across Iterations #10 - #14) at the following levels by the conclusion of Q3: | ||
** Minimum Average Pass Rate - 89% | ** Minimum Average Pass Rate - 89% | ||
** Maximum Average Fail Rate - 11% | ** Maximum Average Fail Rate - 11% | ||
** Minimum Average Coverage Rate - 85% | ** Minimum Average Coverage Rate - 85% | ||
* | ** The QA Team was able to achieve a better than expected Pass and Fail Rate but failed to achieve the desired test coverage due to a lack of dedicated resources: | ||
* Conduct a second Metro Test Day by the conclusion of Q3. | *** Minimum Average Pass Rate - 94% | ||
*** Maximum Average Fail Rate - 6% | |||
*** Minimum Average Coverage Rate - 76% | |||
* '''{{done|}}'''Conduct a second Metro Test Day by the conclusion of Q3. | |||
** Completed on Friday August 30 by Samvadena and Anthony from the QA Department. | |||
<p> </p> | <p> </p> | ||
'''Product Development''' | '''Product Development''' | ||
* '''{{done|}}'''Conclude Development Iteration #10 and Deliver Release Build to Product Manager and QA Department. | * '''{{done|}}'''Conclude Development Iteration #10 and Deliver Release Build to Product Manager and QA Department. | ||
** Completed at the end of Iteration #10 on July 12. | ** Completed at the end of Iteration #10 on July 12. | ||
* Conclude Development Iteration #11 and Deliver Release Build to Product Manager and QA Department. | * '''{{done|}}'''Conclude Development Iteration #11 and Deliver Release Build to Product Manager and QA Department. | ||
* Conclude Development Iteration #12 and Deliver Release Build to Product Manager and QA Department. | ** Completed at the end of Iteration #11 on July 26. | ||
* Conclude Development Iteration #13 and Deliver Release Build to Product Manager and QA Department. | * '''{{done|}}'''Conclude Development Iteration #12 and Deliver Release Build to Product Manager and QA Department. | ||
* Conclude Development Iteration #14 and Deliver Release Build to Product Manager and QA Department. | ** Completed at the end of Iteration #12 on August 12. | ||
* Conclude Development Iteration #15 and Deliver Release Build to Product Manager and QA Department. | * '''{{done|}}'''Conclude Development Iteration #13 and Deliver Release Build to Product Manager and QA Department. | ||
* | ** Completed at the end of Iteration #13 on August 26. | ||
* '''{{done|}}'''Conclude Development Iteration #14 and Deliver Release Build to Product Manager and QA Department. | |||
** Completed at the end of Iteration #14 on September 10. | |||
* '''{{done|}}'''Conclude Development Iteration #15 and Deliver Release Build to Product Manager and QA Department. | |||
** Completed at the end of Iteration #15 on September 24. | |||
* '''{{done|}}'''Identify the feature stories, defects and changes required for a Firefox Metro Preview Release consisting of start (top sites, bookmarks, and history), basic navigation, tabbed browsing, smooth panning, scrolling and zooming. | |||
** Completed during Iteration #12 - [https://bugzilla.mozilla.org/show_bug.cgi?id=899390 View Metro Preview Release Backlog] | |||
* '''{{done|}}'''Develop the initial development complete forecasts for the Firefox Metro Preview Release. | |||
** Completed at the end of Iteration #12. The Metro Preview Release is scheduled for Firefox 26 - [https://wiki.mozilla.org/Firefox/Metro#Metro_Preview_Release See Full Schedule] | |||
* '''{{done|}}'''Develop the initial development complete forecasts for the Metro V1 Public Release. | |||
** Completed at the end of Iteration #14. The Metro V1 Public Release is scheduled for Firefox 27 - [https://wiki.mozilla.org/Firefox/Metro#Metro_V1_Public_Release See Full Schedule] | |||
<p> </p> | <p> </p> | ||
'''Team Performance''' | '''Team Performance''' | ||
* Establish a minimum median velocity of 50 | * '''{{miss|}}'''Establish a minimum median velocity of 50 and an actual velocity range that falls between 46 and 63 by the conclusion of Iteration #15. | ||
* | ** Established a median velocity of 51 with a 90% likelihood that the actual velocity would fall between 43 and 75. | ||
** The median velocity of 51 was higher than forecasted but the development team failed to achieve the forecasted velocity range. | |||
<p> </p> | <p> </p> | ||
| Line 42: | Line 67: | ||
==Platform== | ==Platform== | ||
* | ;Performance | ||
* Improve visibility into engineering performance work via reporting and change in communication tactics | |||
* Iterate on existing project definitions and define new projects as required | |||
;Engineering Effectiveness | |||
* Continue to iterate on engineering meeting to provide more value for engineers | |||
* Drive creation of initial Git read-only mirror of Mozilla Central hosted and supported by Mozilla | |||
;JS | |||
* Engage with JS team and determine how and where to support the team | |||
* Facilitate the landing of Generational GC | |||
;Geolocation | |||
* Review geolocation project and provide initial project definition and structure | |||
==Stability== | |||
*Move bulk of daily watching of crash stats (back) to QA | |||
*Organize Stability Work Week | |||
*Figure out B2G stability process (partner requirements, web tools, daily analysis, ...) | |||
==Mobile Web Compatibility== | ==Mobile Web Compatibility== | ||
* | * Reinvigorate Web compatibility effort via MoCo funded staffing and community participation | ||
* Establish compatibility measure/benchmark in order to measure progress and target effort | |||
* Make significant headway in removing Firefox OS UA overrides | |||
* Engage with other companies that are also investing in mobile Web compatibility | |||
==Program/Project Management== | ==Program/Project Management== | ||
* | * Onboard cpeterson to team | ||
* Create a team project backlog (active projects and unstaffed) | |||