Tag: story points

What Parkrun has taught me about Estimation

The duration of time to run 5kms will vary widely between runners due to complexity, fitness, elevation and effort. Relative Estimation is the key.

What to do when a User Story is 'not done'

Teams love to get credit for their efforts, but is that what you should do if a User Story gets 1/2 way there but doesn’t get to Done in the Sprint? What should you really do with the remainder of the work?

Demystifying Agile Estimation and Planning

Estimating in hours can be highly inaccurate. Estimating using relative wide band delphi like planning poker is key to understanding what you can do and when you can do it by as a team.

Estimating without a baseline

Agile Teams tend to use relative estimation rather than creating tasks, estimating hours, and then adding up all the hours. Adding up hours it fundamentally

Relative Estimating and Sizing Stories

How should we size Stories? Not by hours but through looking at new work relative to the size we gave to old work.

Getting Sizing Right with Cycle Time

Sizing in Story Points represents a significant shift from estimating in hours. Understanding cycle time is key to getting it right.

Patterns for breaking down usability and UX re-work

So you’ve just finished usability testing in your Sprint and have a pile of changes for your agile team to implement. How do you break down the UX changes that are needed to make a product useful, usable and accessible, into smaller, bite-sized User Stories?