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

Jump to navigation Jump to search
m
Line 17: Line 17:
<p> </p>
<p> </p>
'''Project Management'''
'''Project Management'''
* Develop a revised Metro Software Requirements Specification outlining a new version of the Minimum Viable Product (MVP) feature set.
* '''{{done|}}''' Develop a revised Metro Software Requirements Specification outlining a new version of the Minimum Viable Product (MVP) feature set.
** '''{{done|}}''' Completed at the end of Iteration #5 on April 16.  Product Manager review of V1 Release List resulted in the removal of 9 Feature Stories to V2.
** Completed at the end of Iteration #5 on April 16.  Product Manager review of V1 Release List resulted in the removal of 9 Feature Stories to V2.
* Conduct a review of the Story Backlog and revise the priority levels of feature stories.
* '''{{done|}}''' Conduct a review of the Story Backlog and revise the priority levels of feature stories.
** '''{{done|}}''' At the conclusion of Iteration #6, the Product Manager revised the priority levels of the feature stories in the Story Backlog.  The revision resulted in:
** At the conclusion of Iteration #6, the Product Manager revised the priority levels of the feature stories in the Story Backlog.  The revision resulted in:
*** 30 feature stories shifted to a P1 priority level.
*** 30 feature stories shifted to a P1 priority level.
*** 1 feature story shifted to a P2 priority level.
*** 1 feature story shifted to a P2 priority level.
Line 26: Line 26:
*** 12 feature stories shifted to a P4 priority level.
*** 12 feature stories shifted to a P4 priority level.
* '''{{done|}}''' Develop a Pessimistic, Optimistic and Expected Release Scenario.  The initial figures will be presented following the conclusion of Iteration #6 and will be updated at the conclusion of each upcoming iteration.
* '''{{done|}}''' Develop a Pessimistic, Optimistic and Expected Release Scenario.  The initial figures will be presented following the conclusion of Iteration #6 and will be updated at the conclusion of each upcoming iteration.
** '''{{done|}}''' At the end of Iteration #6, the Metro project had enough performance data to establish the three release scenarios:
** At the end of Iteration #6, the Metro project had enough performance data to establish the three release scenarios:
*** Pessimistic Release Scenario - March 20, 2014:  The average velocity figure of the '''worst 3 iterations is 32'''.  If the team drops to this velocity figure, then development would be completed no earlier than '''19 iterations on March 20, 2014'''.   
*** Pessimistic Release Scenario - March 20, 2014:  The average velocity figure of the '''worst 3 iterations is 32'''.  If the team drops to this velocity figure, then development would be completed no earlier than '''19 iterations on March 20, 2014'''.   
*** Optimistic Release Scenario - October 02, 2013:  The average velocity figure of the '''best 3 iterations is 71'''.  If this velocity figure can be achieved and maintained, then development would be completed no later than '''9 iterations on October 02, 2013'''.   
*** Optimistic Release Scenario - October 02, 2013:  The average velocity figure of the '''best 3 iterations is 71'''.  If this velocity figure can be achieved and maintained, then development would be completed no later than '''9 iterations on October 02, 2013'''.   
Line 33: Line 33:
* Maintain 'planning' backlog at no more than 10 items at the conclusion of Q2.
* Maintain 'planning' backlog at no more than 10 items at the conclusion of Q2.
* '''{{done|}}''' Calculate a 90% confidence interval around the median velocity using a Binomial distribution.  The initial figure representing the velocity range will be presented following the conclusion of Iteration #5 and will be updated at the conclusion of each upcoming iteration.
* '''{{done|}}''' Calculate a 90% confidence interval around the median velocity using a Binomial distribution.  The initial figure representing the velocity range will be presented following the conclusion of Iteration #5 and will be updated at the conclusion of each upcoming iteration.
** '''{{done|}}''' At the conclusion of Iteration #5, for velocity values of 30,32,33,63,75, the Metro Team has a median velocity of 33 and there is a 90% likelihood that the actual velocity will fall between 30 and 75.
** At the conclusion of Iteration #5, for velocity values of 30,32,33,63,75, the Metro Team has a median velocity of 33 and there is a 90% likelihood that the actual velocity will fall between 30 and 75.
** '''{{done|}}''' At the conclusion of Iteration #6, for velocity values of 30,32,33,63,75,74, the Metro Team has a median velocity of 48 and there is a 90% likelihood that the actual velocity will fall between 30 and 75.
** At the conclusion of Iteration #6, for velocity values of 30,32,33,63,75,74, the Metro Team has a median velocity of 48 and there is a 90% likelihood that the actual velocity will fall between 30 and 75.
<p> </p>
<p> </p>
'''Quality Management'''
'''Quality Management'''
Line 42: Line 42:
<p> </p>
<p> </p>
'''Product Development'''
'''Product Development'''
* Conclude Development Iteration #5 and Deliver Release Build to Product Manager and QA Department.
* '''{{done|}}''' Conclude Development Iteration #5 and Deliver Release Build to Product Manager and QA Department.
** '''{{done|}}''' Completed at the end of Iteration #5 on April 12.
** Completed at the end of Iteration #5 on April 12.
* Conclude Development Iteration #6 and Deliver Release Build to Product Manager and QA Department.
* '''{{done|}}''' Conclude Development Iteration #6 and Deliver Release Build to Product Manager and QA Department.
** '''{{done|}}''' Completed at the end of Iteration #6 on April 30.
** Completed at the end of Iteration #6 on April 30.
* Conclude Development Iteration #7 and Deliver Release Build to Product Manager and QA Department.
* Conclude Development Iteration #7 and Deliver Release Build to Product Manager and QA Department.
* Conclude Development Iteration #8 and Deliver Release Build to Product Manager and QA Department.
* Conclude Development Iteration #8 and Deliver Release Build to Product Manager and QA Department.
<p> </p>
<p> </p>
'''Team Performance'''
'''Team Performance'''
* Iteration #5 - Team completes 40 points of of their committed Feature Stories.
* '''{{done|}}''' Iteration #5 - Team completes 40 points of of their committed Feature Stories.
** '''{{done|}}''' At the conclusion of Iteration #5 the team has surpassed the goal and completed 75 story points.
** At the conclusion of Iteration #5 the team has surpassed the goal and completed 75 story points.
* Iteration #6 - Team completes 45 points of of their committed Feature Stories.
* '''{{done|}}''' Iteration #6 - Team completes 45 points of of their committed Feature Stories.
** '''{{done|}}''' At the conclusion of Iteration #6 the team has surpassed the goal and completed 74 story points.
** At the conclusion of Iteration #6 the team has surpassed the goal and completed 74 story points.
* Iteration #7 - Team completes 50 points of of their committed Feature Stories.
* Iteration #7 - Team completes 50 points of of their committed Feature Stories.
* Iteration #8 - Team completes 55 points of of their committed Feature Stories.
* Iteration #8 - Team completes 55 points of of their committed Feature Stories.
Confirmed users
4,174

edits

Navigation menu