An estimation is used to assign a measurable value to the work that must be done to complete a project or task. An estimate seeks to determine the effort or cost of a project or task.
It is important that when estimating stories, the team has a shared awareness of the "value" of the estimate. Regardless of whether a team uses the [Fibonacci sequence](/en/agile-dictionary/fibonacci sequence/ "Fibonacci Numbers in Scrum") sequence, t-shirt sizes, or other values.
The agile team must agree on a common estimate of the effort or duration required to complete a task after each team member's personal estimates. This can take the form of Planning Poker, for example. While estimating, it is important that the team gets a common understanding of the tasks at hand and that concerns of individuals are heard.
=> Become a Certified Scrum Product Owner
=> Become a Certified ScrumMaster
Scrum Academy GmbH
Sohrab is a long-standing Certified Scrum Trainer (CST) and CEO of the Scrum Academy GmbH based in Cologne. He is a trained medical doctor and worked for Bain & Company as a consultant and as a CIO at SE-Consulting, among others, before founding the Scrum Academy. As a consultant and trainer, he has been supporting companies from a wide range of industries for over a decade on topics related to agile transformation, innovation and organizational development.
Learn how to create a product goal as a product owner and get a free download of our product goal canvas for your team!
Roman Pichler explains in this recording how you can deal with difficult stakeholders as a product owner! Learn from the best and listen to his agile100 session!
When was Scrum invented and why is it so popular? We answer all your questions about Scrum and Agile in our Foundations!