Program Management/Weekly-Status-Reports/2013-04-09: Difference between revisions

Line 36: Line 36:
** Those features selected for removal will be taken into account in the production release forecast of the Iteration #5 status report.  
** Those features selected for removal will be taken into account in the production release forecast of the Iteration #5 status report.  
* Merged the project's 'On Hold' and 'To Be Planned' backlogs into one [https://bugzilla.mozilla.org/show_bug.cgi?id=841997 (Planning)] to simplify the process of organizing stories (features, defects and changes) which require modification before entering the story backlog for selection in upcoming iterations.  
* Merged the project's 'On Hold' and 'To Be Planned' backlogs into one [https://bugzilla.mozilla.org/show_bug.cgi?id=841997 (Planning)] to simplify the process of organizing stories (features, defects and changes) which require modification before entering the story backlog for selection in upcoming iterations.  
* Created a new Defect and Change backlog to manage the project's existing, and upcoming, defect and change stories [https://bugzilla.mozilla.org/show_bug.cgi?id=859003 (View Metro V1 Defect & Change Backlog)] to better prioritize them in isolation.  
* Created a new backlog to manage the project's defect and change stories [https://bugzilla.mozilla.org/show_bug.cgi?id=859003 (View Metro V1 Defect & Change Backlog)] to better prioritize them in isolation.  
* A cap on the number of defect and change story points allocated to each upcoming iteration will be implemented.  
* A cap on the number of defect and change story points allocated to each upcoming iteration will be implemented.  
** This initiative will assist in managing the contingency fund allocated to defect and change stories so the project does not deplete them too soon.  
** This initiative will assist in managing the contingency fund allocated to defect and change stories so the project does not deplete them too soon.  
Confirmed users
4,174

edits