Confirmed users
4,174
edits
Firefox/Metro: Difference between revisions
Jump to navigation
Jump to search
→Release Plan
| Line 56: | Line 56: | ||
The Release Plan is a guideline that reflects expectations about which features from the Product Backlog will be implemented and when they are completed across multiple iterations for specific target releases. It also serves as a base to monitor progress with the ongoing development of the product. The Release Plan is not static and will be revisited and updated at the conclusion of each iteration. | The Release Plan is a guideline that reflects expectations about which features from the Product Backlog will be implemented and when they are completed across multiple iterations for specific target releases. It also serves as a base to monitor progress with the ongoing development of the product. The Release Plan is not static and will be revisited and updated at the conclusion of each iteration. | ||
<p> </p> | <p> </p> | ||
'''30C-29A-28B Release Cycle''' | |||
<p> </p> | |||
* '''For IT-30C-29A-28B.1:''' | * '''For IT-30C-29A-28B.1:''' | ||
** With a median velocity of 59 points per iteration there is a 90% likelihood that between 141 and 204 points of work, with a median value of 177, can be completed over the three iterations of the 30C-29A-28B release cycle. | ** With a median velocity of 59 points per iteration there is a 90% likelihood that between 141 and 204 points of work, with a median value of 177, can be completed over the three iterations of the 30C-29A-28B release cycle. | ||
| Line 103: | Line 101: | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
<p> </p> | |||
==Iteration Backlog== | ==Iteration Backlog== | ||