Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • tim_ottinger_-_agile_productivity • middle_management_struggling_with_the_change_anti-pattern • simulating_wip_effects_with_balls_and_a_banana • i_am_going_to_wait_for_the_training_anti-pattern • how_should_we_initially_track_release_progress • what_is_the_purpose_of_estimation • how_should_we_initially_track_sprint_progress • what_are_the_steps_to_establish_a_development_manager • how_do_we_use_story_point_estimates_to_forecast
what_is_the_purpose_of_estimation

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
what_is_the_purpose_of_estimation [2019/01/21 08:14] – Note on change in thinking hpsamioswhat_is_the_purpose_of_estimation [2020/06/10 12:52] (current) – ↷ Links adapted because of a move operation hans
Line 6: Line 6:
   * How much will it cost to get this capability?   * How much will it cost to get this capability?
   * Are we making progress to delivering 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. 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.
Line 21: Line 21:
   * [[can_we_trust_story_points_as_a_measure_of_effort|Can We Trust Story Points as a Measure of Effort?]]   * [[can_we_trust_story_points_as_a_measure_of_effort|Can We Trust Story Points as a Measure of Effort?]]
   * [[is_generating_an_estimate_a_waste_of_time|Is Generating an Estimate a Waste of Time?]]   * [[is_generating_an_estimate_a_waste_of_time|Is Generating an Estimate a Waste of Time?]]
-  * [[blog:our_estimates_are_terrible|Our Estimates are Terrible!]]+  * [[our_estimates_are_terrible|Our Estimates are Terrible!]]
  
 {{tag>Team Estimates Forecast FAQ Points EstimationApproach}} {{tag>Team Estimates Forecast FAQ Points EstimationApproach}}
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/what_is_the_purpose_of_estimation.1548087275.txt.gz · Last modified: 2020/06/02 14:26 (external edit)