Software Engineering Project 1 - 4010-561-14.20082 : Estimation Techniques
This page last changed on Apr 10, 2009 by exm3763.
We will be using XP/Scrum agile estimation techniques based on "Agile Estimating and Planning" by Mike Cohn which are outlined below.
The features implemented for each sprint will be pulled from the product backlog, a list of user stories/features prioritized by the product owner. Sprint review meetings will be held at the end of each sprint. During these reviews, new functionality and capabilities that were added during the sprint are demonstrated to stakeholders and feedback is received. The product backlog will be reviewed and priorities adjusted if necessary.
When possible, historical values for the target velocity will be used. For example, the target velocity for the next sprint will be set to the average velocity of the previous sprint. In the case that there are significant technology changes, the historical velocity value will be used along with a observed velocities in technology spikes and a velocity forecast. Velocity forecasts will be determined by:
A goal will be determined that succinctly describes what we would like to accomplish as a team during the sprint. For example "All X features are finished" or "make progress on X". The sprint goal will be a unifying statement about what will be accomplished during the iteration and does not have to be very specific.
Wirox will then meet with the product owner(s) to select stories that combine to meet the sprint goal. This selection process will be driven by the priority of each story. For example, a user story related to the goal that has a very low priority may not be included in the iteration. The selected stories will be marked for the sprint on the product backlog page.
Next, Team Wirox will decompose each user story into the tasks necessary to deliver the new functionality for that story. This will include:
Task estimates will be expressed in terms of ideal time. Tasks should be created with an approximate size so that each developer is able to finish an average of one per day. Large tasks greater than a day will be refined into smaller ones. Planning poker and Wide Band Delphi techniques will be used to estimate the size of user stories.
|Document generated by Confluence on May 21, 2009 10:23|