MozillaWiki

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

< Program Management
 
(32 intermediate revisions by 2 users not shown)
Line 7: Line 7:
==Firefox Android==
==Firefox Android==
;Features, Releases, and Roadmap
;Features, Releases, and Roadmap
* Reinstate Fx Android Program Status to convey recent accomplishments, progress of features compared to roadmap POR, and risk profile around market share initiatives  
* {{done|}} Reinstate Fx Android Program Status to convey recent accomplishments, progress of features compared to roadmap POR, and risk profile around market share initiatives  
* Reinstate live walk-throughs to showcase features in progress
* {{done|}} Reinstate live walk-throughs to showcase features in progress
* Collaborate with Product to refine cadence of Product Planning weekly
* {{done|}} Collaborate with Product to refine cadence of Product Planning weekly
* Firefox Android Work Week  
* {{done|}} Fx19, Fx20
* Fx19, Fx21
* {{miss|}} Firefox Android Work Week <== this happened without me but my real work begins, now!
;MWC 2013
;MWC 2013
* Orchestrate delivery of all cross-functional and core-engineering technical requirements to ensure a successful Fx Android Presence at MWC 2013  
* {{done|}}Orchestrate delivery of all cross-functional and core-engineering technical requirements to ensure a successful Fx Android Presence at MWC 2013  
* Converge Readability 2.0: Finalize UX, Engineering, and QA POR and resulting schedule
* {{done|}}Converge Readability 2.0: Finalize UX, Engineering, and QA POR and resulting schedule


==Firefox Metro==
=={{done|}}Firefox Metro==
<h3>Q1-2013</h3>
 
'''Requirements Management'''
* '''Total Goals:'''  17
* Deliver full Metro Software Requirements Specification outling Minimum Viable Product (MVP) features.
* '''Completed Goals:'''  15
* Reorganize all 'legacy' (pre Iteration #1) bugs and use cases to conform to the new production framework.
* '''Missed Goals:'''  2
** {{done|}}'''Achieved During Iteration #2'''
 
* Resolve the status of all 'legacy' (pre Iteration #1) bugs and use cases to 'Fixed/Verified' status (QA test conducted and any defects resolved).
 
* Develop and execute test cases for all 'legacy' (pre Iteration #1) bugs and use cases and create new Defect Stories.
'''Project Management'''
* Deliver full Metro Software Requirements Specification outlining Minimum Viable Product (MVP) features.
** {{done|}}'''Confirmed by Product Manager During Iteration #3'''
* Integrate QA within development process to test and verify stories as they are completed within an iteration.
** {{done|}}'''QA has been testing stories upon completion since Iteration #2.'''
* Integrate QA within development process to test and verify entire release build at the end of each iteration.
** {{done|}}'''QA has been testing iteration release builds since Iteration #1.'''
* Resolve all 'to be planned' stories so they are ready for development in upcoming iterations.
** {{miss|}}'''Was previously completed but a new story requiring planning was added on March 27, 2013.  Will be carried over to Q2.'''
* Reorganize all 'legacy' (pre Iteration #1) stories to conform to the new production framework.
** {{done|}}'''Confirmed by Product Manager During Iteration #2'''
* Develop Expected Scenario Production Forecast.
** {{done|}}'''Confirmed by Project Manager During Iteration #3'''
* Resolve the status of all 'legacy' (pre Iteration #1) stories to 'Fixed/Verified' status (QA test conducted and any defects resolved).
** {{done|}}'''Confirmed by Project Manager During Iteration #4'''
* Modify all 'on hold' stories so they are ready for development in upcoming iterations.
** {{miss|}}'''Not completed during Q1 - 15 items remain to be resolved.  Will be carried over to Q2.'''


'''Scheduling'''
* Develop forecast schedule model for the following:
** Total value of project story points to complete the project.
** Total number of iterations to complete the project.
** Aurora Build Release date.
** Beta Build Release date.
** Public Launch Release date.


'''Product Development'''
'''Product Development'''
* Migrate Metro prototype to MC-Nightly.
* Migrate Metro prototype to MC-Nightly.
** {{done|}}'''Achieved During Iteration #2'''
** {{done|}}'''Achieved During Iteration #2'''
* Conclude four development Iterations and deliver MVP vertical-slice Iteration builds to Product Manager and QA Department.
* Conclude Development Iteration #1 and Deliver Release Build to Product Manager and QA Department.
** {{done|}}'''Iteration #1 Completed'''
** {{done|}}'''Iteration #1 Completed'''
* Conclude Development Iteration #2 and Deliver Release Build to Product Manager and QA Department.
** {{done|}}'''Iteration #2 Completed'''
** {{done|}}'''Iteration #2 Completed'''
* Conclude Development Iteration #3 and Deliver Release Build to Product Manager and QA Department.
** {{done|}}'''Iteration #3 Completed'''
* Conclude Development Iteration #4 and Deliver Release Build to Product Manager and QA Department.
** {{done|}}'''Iteration #4 Completed'''


'''Team Performance'''
'''Team Performance'''
* Scale team Iteration performance as follows (based on a forecast of 100 story points per Iteration):
* Iteration #1 - Team completes 20 points of of their committed Feature Stories.
** Iteration #1
** {{done|}}'''At the conclusion of Iteration #1 the team has surpassed the goal and completed 30 story points.'''  
*** Team completes 20 points of of their committed Feature Stories.
* Iteration #2 - Team completes 25 points of of their committed Feature Stories.
**** {{done|}}'''At the conclusion of Iteration #1 the team has '''surpassed the goal''' and completed 30 story points.'''  
** {{done|}}'''At the conclusion of Iteration #2 the team has surpassed the goal and completed 32 story points.'''  
** Iteration #2
* Iteration #3 - Team completes 30 points of of their committed Feature Stories.
*** Team completes 25 points of of their committed Feature Stories.
** {{done|}}'''At the conclusion of Iteration #3 the team has surpassed the goal and completed 33 story points.'''
**** {{done|}}'''At the conclusion of Iteration #2 the team has '''surpassed the goal''' and completed 32 story points.'''  
* Iteration #4 - Team completes 35 points of of their committed Feature Stories.
** Iteration #3
** {{done|}}'''At the conclusion of Iteration #4 the team has surpassed the goal and completed 63 story points.'''
*** Team completes 30 points of of their committed Feature Stories.
** Iteration #4
*** Team completes 35 points of of their committed Feature Stories.


==Firefox OS==
==Firefox OS==

Latest revision as of 02:21, 27 June 2013

Firefox Desktop

  • Ship FHR in Fx20 GA.
  • Define and execute performance projects for start-up and shutdown (Snappy)
  • Define and drive implementation of performance metrics
  • Support elaboration of platform technical roadmap

Firefox Android

Features, Releases, and Roadmap
  • [DONE] Reinstate Fx Android Program Status to convey recent accomplishments, progress of features compared to roadmap POR, and risk profile around market share initiatives
  • [DONE] Reinstate live walk-throughs to showcase features in progress
  • [DONE] Collaborate with Product to refine cadence of Product Planning weekly
  • [DONE] Fx19, Fx20
  • [MISSED] Firefox Android Work Week <== this happened without me but my real work begins, now!
MWC 2013
  • [DONE] Orchestrate delivery of all cross-functional and core-engineering technical requirements to ensure a successful Fx Android Presence at MWC 2013
  • [DONE] Converge Readability 2.0: Finalize UX, Engineering, and QA POR and resulting schedule

[DONE] Firefox Metro

  • Total Goals: 17
  • Completed Goals: 15
  • Missed Goals: 2


Project Management

  • Deliver full Metro Software Requirements Specification outlining Minimum Viable Product (MVP) features.
    • [DONE] Confirmed by Product Manager During Iteration #3
  • Integrate QA within development process to test and verify stories as they are completed within an iteration.
    • [DONE] QA has been testing stories upon completion since Iteration #2.
  • Integrate QA within development process to test and verify entire release build at the end of each iteration.
    • [DONE] QA has been testing iteration release builds since Iteration #1.
  • Resolve all 'to be planned' stories so they are ready for development in upcoming iterations.
    • [MISSED] Was previously completed but a new story requiring planning was added on March 27, 2013. Will be carried over to Q2.
  • Reorganize all 'legacy' (pre Iteration #1) stories to conform to the new production framework.
    • [DONE] Confirmed by Product Manager During Iteration #2
  • Develop Expected Scenario Production Forecast.
    • [DONE] Confirmed by Project Manager During Iteration #3
  • Resolve the status of all 'legacy' (pre Iteration #1) stories to 'Fixed/Verified' status (QA test conducted and any defects resolved).
    • [DONE] Confirmed by Project Manager During Iteration #4
  • Modify all 'on hold' stories so they are ready for development in upcoming iterations.
    • [MISSED] Not completed during Q1 - 15 items remain to be resolved. Will be carried over to Q2.


Product Development

  • Migrate Metro prototype to MC-Nightly.
    • [DONE] Achieved During Iteration #2
  • Conclude Development Iteration #1 and Deliver Release Build to Product Manager and QA Department.
    • [DONE] Iteration #1 Completed
  • Conclude Development Iteration #2 and Deliver Release Build to Product Manager and QA Department.
    • [DONE] Iteration #2 Completed
  • Conclude Development Iteration #3 and Deliver Release Build to Product Manager and QA Department.
    • [DONE] Iteration #3 Completed
  • Conclude Development Iteration #4 and Deliver Release Build to Product Manager and QA Department.
    • [DONE] Iteration #4 Completed


Team Performance

  • Iteration #1 - Team completes 20 points of of their committed Feature Stories.
    • [DONE] At the conclusion of Iteration #1 the team has surpassed the goal and completed 30 story points.
  • Iteration #2 - Team completes 25 points of of their committed Feature Stories.
    • [DONE] At the conclusion of Iteration #2 the team has surpassed the goal and completed 32 story points.
  • Iteration #3 - Team completes 30 points of of their committed Feature Stories.
    • [DONE] At the conclusion of Iteration #3 the team has surpassed the goal and completed 33 story points.
  • Iteration #4 - Team completes 35 points of of their committed Feature Stories.
    • [DONE] At the conclusion of Iteration #4 the team has surpassed the goal and completed 63 story points.

Firefox OS

Q1-2013

  • Deliver to FFOS Roadmap
    • FFOS v1 Code Freeze early January
    • FFOS Shira Code Freeze February
    • FFOS Leo Code Freeze
  • Partner Communication Plan
    • RACI or Actor profiles identifying R&R for Mozilla plus Partners
    • Cross-organizational alignment on communication plan

Q2-2013

  • Deliver to FFOS Roadmap
    • FFOS v1.0 Launch with TEF & ZTE Q2
    • FFOS v1.x (Shira) Launch with DT & TCL Q2
    • FFOS v1.x (Leo) Launch with TEF & LG Q3

Mobile Web Compatibility

  • Define measurable compatibility projects for 2013
  • Hire 2-3 technical/evangelism resources
  • Drive Webkit aliasing research

Program/Project Management

  • Expand team by 3 people
Retrieved from "https://wiki.allizom.org/index.php?title=Program_Management/Firefox/2013-Q1-Goals&oldid=670860"