Let’s talk High Low in Story Point Estimation

  1. Our Product Owner gives an overview of the story
  2. The team asks questions to clarify their understanding of the story
  3. We confirm acceptance criteria for the story
  4. Each person in the team gives an estimate of the story points **at the same time** — based on the effort required to complete that story
  1. All members give the same estimate — then we’re good to go, the story has been estimated and the team has agreement OR
  2. We get a range of estimates — this is where it gets juicy!




Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Top 5 Product Management Tools To Make The Process Easier

Product discovery — the new holy grail

3 Common Mistakes When Fighting Customer Churn

How to Build AI Powers Modern Product Lifecycle Management

How to spot and fix issues with a cumulative flow diagram

5 signs you should go Scrumban, rather than Scrum or Kanban

Scrumban or bad agile practice of Scrum and Kanban?

What the hell is a Product Manager, and What does a PM do?

What NOT to measure in B2B product companies.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


More from Medium

Scrum Guild at Leaseweb

What is Scrum?

The start stop continue method

Who uses agile?