Read more about the general principles of Value estimation here.
If the story is delegated from another circle and value is configured to automatically synchronize, then the displayed value will be set in that circle. Read more about delegation synchronization here.
/alh-replace have any warnings regarding the value, then they are displayed at the top of this box (Read More).
The customer satisfaction of the
/alh-replace is estimated using the Kano model. Read more about the categories in Kano classification.
/alh-replace is classified as a Must-have (or Reverse/Indifferent) it cannot at the same time have a numerical value. Read more about working with Must-haves here and how the Must-have state is inherited to children of epics.
/alh-replace is classified as a Satisfier or Exciter it can have a numerical value.
Must Have Classification
/alh-replace can be classified as being either a Must-have or not a Must-have. If it classified as a Must-have it cannot at the same time have a numerical value.
Read more about working with Must-haves here.
Numerical value is the quantification of how much value is obtained by completing this
/alh-replace. Whether value is estimated in story points or some other unit is optional in Agemba.
Until a value estimate is set, the
/alh-replacewill count as having no value – unless a provisional/default estimate is set for this circle. This estimate will be shown in brackets e.g. (2) until a real estimate is set.
Value is estimated with both an expected and worst-case estimate. The expected is the realistic estimate of the work needed with 50% certainty (it should not be confused with an optimistic best-case estimate). The worst-case estimate with a 90% certainty. The worst-case value estimate will always be less than the expected estimate.
Uncertainty of Value Estimate
Uncertainty is the distance between expected and worst-case effort in percentage. The higher the difference between the two, the higher the uncertainty. Read more about working with uncertainties.