Purpose

1. The Estimation Meeting serves two goals: The Team members get the necessary knowledge about the Stories in the Backlog as well as a clearer picture of the overall product.
2. The Team members estimate the range of functions of the Stories.
3. The break down of Stories and forming of new ideas during the Estimation Meeting lead to the creation of further Stories.

Basics

Only the Team estimates the functionality. A Product Owner needs to be present to help decide how a Story can be broken down into smaller Stories.

Ingredients

• The Product Backlog, which is prioritised by the Product Owner according to business value.

Coloured icon = mandatory participant

Grey icon = optional participant

Insider Tip: Try also using this method for estimating the business value of Stories together with other Product Owners.

Don't

1. ... estimate effort instead of functionality.
2. ... let the Product Owner estimate or facilitate the meeting.
3. ... estimate Stories during the Sprint Planning Meeting

Procedure

1. The Product Owner presents the Product Backlog Items that need to be estimated by the Team.
2. The Team uses either Planning Poker or Magic Estimation to estimate the size of these Backlog Items.
3. In case a Backlog Item is too large but needs to be developed within the next or subsequent Sprint, the Team will break down the Backlog Item into smaller Backlog Items. The new Backlog Item can be estimated by playing Magic Estimation for just that Item.
4. Re-estimate all Backlog Items that may be pulled during the next three Sprints.
5. Identify Backlog Items that need to be clarified by the Product Owner until the next Estimation Meeting.

Duration

Time-box this meeting to 35 mins or less.

These meetings should take place on a weekly basis.

Output

• Estimated Product Backlog
• Smaller, decomposed Backlog Items
• A list of Stories that need to be looked into more closely.