# Planning 1 - Estimation Concepts

AgileEstimationPlanning

# Planning 1 - Estimation Concepts

Created 3 years ago

Duration 0:07:17
565
Select the file type you wish to download
Slide Content
1. ### Slide 1 - Planning 1: Estimation Concepts

• Emerson Murphy-Hill
• Creative Commons Attribution 4.0 License.
• Material Produced by NCSU Software Engineering Faculty.
2. ### Slide 2 - Estimating and Planning

• Estimating – estimating the [resources, time, size] required to develop a [user story, feature, or requirement]
• Planning – putting the estimates together to formulate a project plan and schedule

• Desired
• Features
4. ### Slide 4 - Estimating size: measures of time

• Story point: unit of measure for expressing the overall size of a user story, feature, or other piece of work. The raw value of a story point is unimportant. What matters are the relative values.
• Related to how hard it is and how much of it there is compared to other requirements
• NOT related to amount of time or # of people
• Unitless, but numerically-meaningful
• Ideal time: the amount of time “something” takes when stripped of all peripheral activities
• Example: American football game = 60 minutes
• Elapsed time: the amount of time that passes on the clock to do something
• Example: American football game = 3 hours
5. ### Slide 5 - Estimating story points

• Choose a medium-size story and assign it a “5”
• Estimate other stories relative to that
• Twice as big
• Half as big
• Almost but not quite as big
• A little bit bigger
• Only values:
• 0, 1, 2, 3, 5, 8, 13, 20, 40, 100
• Near term iteration
• “stories”
• A few iterations away
• “epic”
6. ### Slide 6 - Estimating ideal days

• Ideal days vs. elapsed time in software development
• Supporting current release
• Sick time
• Meetings
• Demonstrations
• Personal issues
• Phone calls
• . . . .
• When estimating ideal days, assume:
• The story being estimated is the only thing you’ll work on
• Everything you need will be on hand when you start
• There will be no interruptions
7. ### Slide 7 - Ideal days vs. Story points

• Favoring story points:
• Help drive cross-functional behavior
• Do not decay (change based on experience)
• Are a pure measure of size (focus on feature, not person)
• Estimation is typically faster in the long run
• My ideal days are not your ideal days (focus on person and their speed )
• Favoring ideal days:
• Easier to explain outside of team
• Estimation is typically faster at first