Monday, February 5, 2018

The Scrum Estimation Meeting | Supreme Agile

תוצאת תמונה עבור ‪scrum estimates‬‏

I will start with one simple clarification about this meeting and will say that it is NOT an official scrum event, now that it’s on the table, we can move forward and explain why this meeting can be a great addition to your team.

So, what is the meaning of the "Estimation" meeting…? Well, this meeting is created to fulfills some major goals that will allow the team to increase the effectiveness of the planning meeting, these goals are:
  1. The team members will gain an earlier familiarity with the user stories of the next sprint.
  2. The team members will acquire the necessary information about the scale of the expected work.
  3. The team members will get the chance to assess the range of activity and effort that is needed to deliver the list of stories.
  4. The team members will have the chance to reduce the amount of time spent during the planning meeting of breaking down the stories.
  5. Based on the tea inputs, New Stories can be added, modified and large stories will break down into smaller items.

Who should participate? 

The meeting stakeholders are the product owner (PO), the Scrum Master (SM) and the team. 


Same as any other meeting in the scrum, this meeting is also timeboxed for a specific amount of time. based on my experience this meeting should be restricted to 60 minutes to really allow the team to become familiar with the stories and for the product owner to make the adjustment in the product backlog

The Frequency and When 

In two weeks iteration, we will schedule this meeting once at the end of the first week (Usually day after the refinement meeting) and once again in the following week. Now, this suggestion can be modified based on the maturity of the team and the readiness of the product backlog. 


You can run this meeting with the different steps that may change between one team to another, but the bassline that always worked for me is as follows: 
  1. The scrum master will schedule the meeting and invite the relevant participants, the invitation will include the meeting agenda, location, and goals.
  2. Once everyone has arrived, the product owner (PO) will review the TOP prioritized stories that represent the candidates of the next iteration which need to be estimated by the team.
  3. The team will ask the product owner the necessary questions to retrieve the missing information that will help them to estimate the stories
  4. Once the team gains the necessary knowledge, they will start to estimate the stories (Relative or Absolute estimations based on what is more suitable for the team).
  5. Based on the team inputs, the product owner will update the product backlog accordingly. 

Action Items 

As I already described in the paragraphs above, there are some great outputs that we can generate by running this meeting:
  1. The product backlog has a better prioritization.
  2. User Stories are created, modified and removed.
  3. User stories that contain a rough estimation.
  4. User stories with written tasks (Not Estimated!). 

No comments:

Post a Comment

My Presentations