How To Use Story Points in Agile and Story Point Estimation

In this video titled How To Use Story Points in Agile, software developer and Agile coach Steve Bishop discusses the purpose of story points in Agile estimation, how they should be used, how story points relate to time, and a rubric for deciding how many points a story should have.

User stories are one of the most common tools used by Agile software development teams, but they are also commonly misused. After watching this video you will have a rubric to help you and your team decide how many story points a story should have, and solutions to some of the most common problems encountered when working on user stories.

#Agile Development
----------
Become a member today for only $5 a month!

When you join, here’s what you’ll get:
* Your name in the credits
* A form to ask me for help on your project
* 10% off in the Teespring store (discount code)
----------
Looking for DAILY news and commentary? Join us on my other channel “Coffee With Steve” for daily videos where we discuss Technology, Software Development, Politics, Culture, and many other things.

[quentinlefebvre]

I'm not a programmer myself and have only a limited participation in projects so far, but this is a well-made video.
It's clear, the narration is dynamic, meaning the attention stays.
I have watched several Agile related training videos these last weeks and loads make you fall asleep due to the monotonous narration.
Good job on this one!
As a suggestion, since the video is quite long, can you maybe add chapters, so you can easily go back to specific topics of the presentation?

[brandonl.underwood]

Hi Steve - love the channel! Quick question about your story point rubric: how do you account for volume of work in a particular story? I believe Mike Cohn once gave an example where you could have 2 stories that involved creating simple text based forms on a website, but the first story only had 2 fields, and the other had 100. Neither story is complex in the sense that all the fields were simple text, and we could assume no unknowns or communication issues as well. Thoughts?

[marco.garofalo]

This video is really well done, offers a lot of examples and good strategies, but I strongly disagree on the premise that story points are in some way related to value delivered to the user, those are two completely orthogonal dimensions. I was also thinking that Ideally you don't even need story points as long as you can identify complexity/unknowns/comms issues, so instead of using arbitrary numbers/vakues/sizes/etc, use the criteria you proposed as the definition of ready, so the question goes from "how many point we set on this story?" to "can we potentially start working on this story now?", if the answer is negative then use spikes or story splitting/slicing or comms mitigations techniques until the answer is affirmative.

[professordrabhijitsayamber]

Om shanti k good day please find attached