From the course: Agile at Work: Planning with Agile User Stories

Unlock the full course today

Join today to access over 23,200 courses taught by industry experts.

Understand velocity

Understand velocity

From the course: Agile at Work: Planning with Agile User Stories

Start my 1-month free trial Buy for my team

Understand velocity

“

- How does an Agile team determine how much work they can start and finish in an iteration? First, the scope of work must be broken down into small enough requirements to enable this to happen. It is a good thing you've learned the most common and practical technique for de-composing higher level or more significant requirements, user and technical stories. Next, they need a point of reference for the size of those small requirements. For our good news, you have learned about relative sizing and story points. Great. Let's have a backlog filled with stories. How many should we plan to do in our next iteration? Well, if all of them were the same level of effort and complexity, we could calculate an average over time, and that is how many we could repeatedly do. With some experience and a few iterations under our belt, we find we can begin to complete approximately 10 stories per iteration. That sure would make planning easy. We identified the 10 stories we will do and off we go. Well…

Contents