• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile Estimating
 

Agile Estimating

on

  • 5,167 views

An introduction to estimating projects using agile with scrum.

An introduction to estimating projects using agile with scrum.

Statistics

Views

Total Views
5,167
Views on SlideShare
4,684
Embed Views
483

Actions

Likes
4
Downloads
0
Comments
0

15 Embeds 483

http://rorblog.techcfl.com 127
http://blog.adsdevshop.com 98
http://www.agiledevelopmentwithscrum.com 81
http://www.agiledevelopmentwithrob.com 73
http://www.adsdevshop.com 67
http://www.slideshare.net 13
http://rorblog.adsdevshop.com 8
http://www.byteengine.net 5
http://adsdevshop.com 5
http://www.hanrss.com 1
http://health.medicbd.com 1
http://209.20.73.252 1
http://static.slideshare.net 1
http://safe.tumblr.com 1
http://translate.googleusercontent.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile Estimating Agile Estimating Presentation Transcript

  • Agile Estimating Robert Dempsey Atlantic Dominion Solutions
    • CEO, Atlantic Dominion Solutions
    • Certified Scrum Master (CSM)
    • Founder, Rails For All
    • Chair, acts_as_conference
    • Scrum Lunch and Learn
    • BA, Computer Science, Rollins
    • MBA, Crummer, 2009
    Robert Dempsey
  •  
    • Estimating with Story Points and Ideal Days
    • Techniques for Estimating
    Agenda
    • Estimating with Story Points and Ideal Days
    • Techniques for Estimating
    Agenda
  • Agile Estimating Overview Agile Estimating and Planning, Cohn
    • … to read the latest Scrum book?
    • … to drive to San Francisco?
    How long will it take…
  • Estimate size; derive duration Agile Estimating and Planning, Cohn
  • Measures of Size
    • Lines of code
    • Function points
    • Story points
    • Ideal days
    • Ideal hours
    Traditional Agile
    • How long would it take if…
      • All you worked on
      • No interruptions
      • Everything you need is available
    • Ideal time of a football game 60 minutes
      • 4, 15-minute quarters
    • Elapsed time is much longer
    Ideal Days
    • Overall size of a story
    • We look at
      • Amount of effort required
      • Complexity
      • Risk involved
    • Relative
    • No units
    Story Points
    • As a Site Visitor I can create an account so that I can use the site. - 2
    • As a User I can search other user so that I can add to my list of friends. – 8
    • As a User I can pay for my subscription using a credit card so that I can use the site. - 20
    Examples
    • Labrador retriever
    • Terrier
    • Great Dane
    • Poodle
    • Dachshund
    • German shepherd
    • Saint Bernard
    • Bulldog
    Dog Points
    • Pure measure of size and complexity
    • Relative; longer shelf life
    • Independent of the estimator
    • Typically faster
    • Easier to work with
    • “My ideal days are not your ideal days.”
    • Studies show we are better at relative estimating
    Advantages of Story Points
    • Easier to explain outside the team
    • Easier to estimate at first
    • Force companies to confront time-wasting activities
    Advantages of Ideal Days
  • Releases, Sprints, Velocity
    • A release is made up of many iterations
    • A sprint is a box containing a fixed amount of time
    • A sprint contains stories
    • Velocity = the number of story points in the box
    • Estimating with Story Points and Ideal Days
    • Techniques for Estimating
    Agenda
  • How Much Effort? Effort Accuracy 50 - 100 -
    • Select the smallest story, give it a “1”, and assign the rest
    • Select a story that is in the middle, assign it a middle value, assign the remaining stories relative to the middle one
    Approaches to Estimating
    • Comparing a user story to others
      • “This story is like that story, so its estimate is what that story’s estimate was.”
    • Don’t use a single gold standard
    • Triangulate
      • Compare the story being estimated to multiple other stories
    Estimate by Analogy
    • Can you distinguish a 1-point story from a 2?
    • Can you distinguish a 17 from an 18?
    • Use units that make sense
      • 1,2,3,5,8, 13
      • 1,2,4,8
    • Stay mostly in the 1-10 range
    Use the Right Units
    • An iterative approach to estimating
    • Steps
      • Each estimator is given a deck of cards, each card has a valid estimate written on it
      • Customer/Product Owner reads a story and it’s discussed briefly
      • Each estimator selects a cards that’s his or her estimate
      • Cards are turned over so all can see them
      • Discuss differences (especially outliers)
      • Re-estimate until estimates converge
    Planning Poker
  • Planning Poker – An Example Estimator Round 1 Round 2 Robert 3 5 Chad 8 5 Ken 2 5 Mark 5 8
  • Estimate This – Kitchen Remodel Backlog Item 1. Install new hardwood floor 2. Refinish (remove, sand, repaint) the cabinets 3. Install granite countertop instead of tile 4. Repaint entire kitchen 5. Lay shelf paper 6. Install recessed lighting 7. Replace electric stove with gas stove 8. Install built-in regrigerator 9. Install a new oven 10. Plumb the island and add a sink
    • When the relative size of a user story changes
    • Partially completed stories
      • All or nothing velocity
    Re-Estimating
  • Recommended Reading
  • THANK YOU
  • Questions? ADS techcfl.com ADWS agiledevelopmentwithscrum.com Twitter twitter.com/rdempsey LinkedIn linkedin.com/in/techcfl