|Agile Construction Team|
- Developing the metric is a mechanism for individuals to share their understanding of the requirement, ask questions, and to discuss any complexities with the implementation.
- It provides feedback to the product owner, architects, and stakeholders on the overall complexity of the Story. If a story is sized high, it may cause one to challenge the priority of the story or provide grounds to question the team on approach.
Conducting a Sizing Meeting
- The backlog was displayed on a large monitor for all teams to see.
- Remote team members participated including QA.
- The Lead (tech lead on our teams, ScrumMaster may be appropriate for others) read the story.
- The Lead called out each person on the team to relay their thinking of the story and to announce and justify the size.
- The Lead decided on the final size - often taking the maximum set by team members. Stories that could not be sized or where there was too much variance by individuals were not sized.
- The story was updated with the agreed on size in the backlog.
- The meeting was conducted efficiently going from one story to the next until all stories ready for sizing were reviewed.
Valuable, efficient, and productive.
Note that in the Agile practices I sponsor, Sizing is a distinct and separate process than Estimation as you can see from my earlier post on How and Why to Estimate in Agile. I'll connect these two processes in my next post.