Differences

This shows you the differences between two versions of the page.

--- what_is_the_purpose_of_estimation [2019/01/21 08:12] – Significant refactor to isolate chapters hpsamios
+++ what_is_the_purpose_of_estimation [2019/07/01 13:20] – hpsamios
@@ Line 6: / Line 6: @@
   * How much will it cost to get this capability?
   * Are we making progress to delivering this capability?
-  * What is capabilities are coming up?
+  * What capabilities are coming up?
 From the business perspective, the main reason for estimates is to provide data to the business (through the Product Owner / Manager) to understand, manage, and forecast plans. They are trying to make sure that, for a given capacity for the organization (enterprise, program, or team), we make trade-off decisions about how to best use that capacity based on the strategy we have and the need for self-investment, and then understand progress against these decisions. A secondary reason is to help the organization understand their capacity so they do not over-commit; so they can establish a sustainable pace.
 Agile requires that we provide the business (through the Product Owner / Product Manager) with good enough data, that we work to improve the estimates when they do not provide the data required. In other words, when we say “make estimation work” what we mean is that the business can easily plan using the estimates and velocity and can make informed business decisions. If the business cannot make it work, it is up to the team / team-of-teams to help fix the problem.
+The agile approach to estimation stresses speed, full team involvement, and information that is accurate enough for the purpose intended, not pure precision. This is aimed at reducing the burden of estimation, while still providing the data needed.
 ====== Want to Know More? ======