• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile Estimation And Planning
 

Agile Estimation And Planning

on

  • 20,544 views

http://fragmental.tw

http://fragmental.tw

Statistics

Views

Total Views
20,544
Views on SlideShare
20,514
Embed Views
30

Actions

Likes
28
Downloads
666
Comments
2

7 Embeds 30

http://lkappel.free.fr 11
http://www.slideshare.net 6
https://twitter.com 5
https://www.linkedin.com 5
http://www.lmodules.com 1
http://paper.li 1
http://coderwall.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

12 of 2 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • hi phi this very nice
    Are you sure you want to
    Your message goes here
    Processing…
  • Hi Phil,
    It seems by your presentation you are familiar to Jira and Greenhopper, am I right?
    We are using Jira and Greenhopper now and I am a bit stuck about the Velocity per team member. I am estimating the issue (task, not story point) and running different reports, but none of them really suit our needs because we need to have a estimated time per each assignee for the sprint. Maybe there are some suggestiong what I can use?
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Agile Estimation And Planning Agile Estimation And Planning Presentation Transcript

    • An Introduction to Agile Estimation and Release Planning Phillip Calçado pcalcado@thoughtworks.com © ThoughtWorks 2008
    • Agile Estimation 1 - Product Backlog ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks © ThoughtWorks 2008
    • 2 - Estimate Each Item ThoughtWorks How long is this going to take? -1 day? -1 week? -Forever? © ThoughtWorks 2008
    • 2 - Estimate Each Item ThoughtWorks Is #1 likely to take longer than #2 ? ThoughtWorks © ThoughtWorks 2008
    • How much longer? = ThoughtWorks ThoughtWorks ThoughtWorks #1 #1 ? #2 #1 ThoughtWorks #1 ThoughtWorks #1 ThoughtWorks ? ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks #1 #1 #1 #1 ? © ThoughtWorks 2008
    • How much longer? = ☑ ThoughtWorks ThoughtWorks ThoughtWorks #1 #1 ? #2 #1 ThoughtWorks #1 ThoughtWorks #1 ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks #1 #1 #1 #1 ? © ThoughtWorks 2008
    • Let’s create a unit =2 ThoughtWorks #1 © ThoughtWorks 2008
    • Let’s create a unit =2 ThoughtWorks #1 then =6 ThoughtWorks #2 © ThoughtWorks 2008
    • 2 - Estimate Each Item ThoughtWorks ThoughtWorks ThoughtWorks 2 6 4 ThoughtWorks ThoughtWorks ThoughtWorks 2 4 6 ThoughtWorks ThoughtWorks ThoughtWorks 2 4 4 © ThoughtWorks 2008
    • 2 - Estimate Each Item •Stories will change •Everyone estimates •Points aren’t a unit of time •Being consistent is more important than being accurate •Estimates must include uncertainty © ThoughtWorks 2008
    • 3 - Prioritise ThoughtWorks ThoughtWorks ThoughtWorks 2 6 4 ThoughtWorks ThoughtWorks ThoughtWorks 2 4 6 ThoughtWorks ThoughtWorks ThoughtWorks 2 4 4 © ThoughtWorks 2008
    • 3 - Prioritise ThoughtWorks ThoughtWorks ThoughtWorks 2$$$ 6 $ 4$$$ ThoughtWorks ThoughtWorks ThoughtWorks 2 $ 4 $ 6 $$ ThoughtWorks ThoughtWorks ThoughtWorks 2 $ 4 $$ 4 $$ © ThoughtWorks 2008
    • 3 - Prioritise ThoughtWorks ThoughtWorks ThoughtWorks 2$$$ 6 $$ 4 $ ThoughtWorks ThoughtWorks ThoughtWorks 4$$$ 4 $$ 6 $ ThoughtWorks ThoughtWorks ThoughtWorks 4 $$ 2 $ 2 $ © ThoughtWorks 2008
    • 3 - Prioritise •It is important to help the client prioritise •But the client has the final word •Technical dependencies are relevant •Priorities will change over time © ThoughtWorks 2008
    • 4 - Assess Velocity Points = Effort Duration = ? © ThoughtWorks 2008
    • Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Iteration 6 ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks 2 2 2 4 2 2 ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks 2 2 2 4 4 4 ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks 2 4 4 4 6 6 ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks 2 2 6 2 2 6 8 10 14 14 14 18 © ThoughtWorks 2008
    • Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Iteration 6 8 10 14 14 14 18 Velocity © ThoughtWorks 2008
    • 4 - Assess Velocity What’s our average Velocity likely to be? © ThoughtWorks 2008
    • 4 - Assess Velocity •Planned Velocity is useful only until we have real data - just an educated guess •“Yesterday’s weather” is more important than average •Iterations must create production-quality increments •Velocity is specific for a team © ThoughtWorks 2008
    • 5 - Candidate Schedule Say planned Velocity is 6 © ThoughtWorks 2008
    • 5 - Candidate Schedule Say planned Velocity is 6 Backlog is 34 points total © ThoughtWorks 2008
    • 5 - Candidate Schedule 34 / 6 = 6 Iterations © ThoughtWorks 2008
    • 5 - Candidate Schedule Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 5 Iteration 6 ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks ThoughtWorks 2 6 2 2 6 4 $$$ $$ $ $ $ $ ThoughtWorks ThoughtWorks ThoughtWorks 4 4 4 $$$ $$ $$ © ThoughtWorks 2008
    • 5 - Candidate Schedule •Ramp-up time usually has a huge impact •Pay attention to cost/scope/ time constraints •Aim at delivering early and often © ThoughtWorks 2008
    • 6 - Monitor and Adapt Plans are not that important. Planning is. © ThoughtWorks 2008
    • 6 - Monitor and Adapt Real World Example Original Plan Actual Total Scope 60 45 Points 30 15 0 Start 1 2 3 4 5 6 7 8 9 Iteration © ThoughtWorks 2008
    • 6 - Monitor and Adapt •You can’t embrace change and have a plan written in stone •Re-estimate whenever necessary •Don’t try and force real life to look like your plan - It’s the other way around © ThoughtWorks 2008
    • Concluding •This is just a framework - there are multiple variants •The customer is a partner during estimation and planning •Don’t try to change the world, change your plan © ThoughtWorks 2008