align-toparrow-leftarrow-rightbackbellblockcalendarcamerachatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-crosscrosseditemptyheartfacebookfullheartglobegoogleimagesinstagramlocation-pinmagnifying-glassmailmoremuplabelShape 3 + Rectangle 1outlookpersonplusImported LayersImported LayersImported Layersshieldstartwitteryahoo

Practical Estimation

Let's have some fun and take a hands-on approach to Practical Estimation. There will be a bit of theory, a bit of discussion, and some Agile games, as we explore topics such as:

- What is an estimate and why do we need one?
- What are we estimating? Size? Effort? Complexity?
- What units should we estimate in? Story points? T-shirt sizes? Dogs? Fruit?
- What can we do with estimates?

Please note that seating is more limited for this event.

Join or login to comment.

  • Johnny H.

    For anyone interested in alternatives to estimation, check out Monte Carlo:

    Probabilistic Project Planning with Dimitar Bakardzhiev (Webinar Recording and Slides)

    1 · June 20, 2014

  • Gordon W.

    Very thought provoking. Group exercises was super fun!

    June 16, 2014

  • Tim

    I always try to take something away from a meeting like this. I particularly like it when that take away is a pithy, repeatable bon mot that I can share with others (sometimes to their dismay). Tonight I took away two. One participant (with incredible knowledge of American Kennel Club breeds) suggested that, during each scrum, one should ask "How confident are we that we will meet our objectives for this sprint?" This kind of question allows early detection of concerns and early escalation, if necessary.

    The other take away was, when asked for an estimate, ask "What are you going to use this for?" If this answer is "to tell customers when to expect delivery" then I will know that the person asking plans to use the estimate as a commitment.

    Thanks Susan (and anyone else involved) for organising this meeting.

    3 · June 16, 2014

  • Nico P.

    Great Meetup tonight. Was shaking my head yes that I learned something new. Thanks for organizing the event.

    1 · June 16, 2014

  • Harnek

    Estimate gives you a rough idea about how much you think it will take to finish. Agreed it could be wrong but with the history you can learn and possibly provide better estimates. Estimation will completely be meaningless if you are trying to estimate a huge PBI, slice them down and then the estimate could become meaning full.

    June 16, 2014

  • Johnny H.

    As soon as you realize your estimation unit is meaningless, it becomes useful.

    Also, a sprint "commitment" is now a "forecast".

    2 · June 13, 2014

  • Tim

    At the last Agile discussion on estimation, I loved the one quote from a panelist: "Estimates are not commitments". So accurate and yet understood by so few people in management. They may "get" it, but they don't "grok" it.

    1 · June 12, 2014

  • Susan P.

    Please change your RSVP if you are unable to come to the event so that people on the waiting list can attend. This looks like there will be quite a crowd.

    June 12, 2014

  • Juan

    What is an estimate? What is a guess? What is and educated guess? What are the differences? Does it really matter?

    June 9, 2014

  • Ammar

    In my opinion, its all about estimation, right from submitting the proposal to project sign-off.

    And for PM to do an effective estimates, he needs a technical background, and/or the assistance of the technical lead.

    June 9, 2014

  • Gordon W.

    I always half jokingly say we estimate and plan so we can identify cases, scenarios and outcomes that definitely won't happen!

    June 9, 2014

  • Johnny H.

    But estimation is waste! ;-)

    1 · June 9, 2014

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy