It is possible for each circle to configure exactly which parts of Value estimation are relevant. Read more about the general principles of Value estimation here.
When you change estimation configuration, the system will automatically update all the affected stories etc. according to the changes. Since this might result in overwriting or removing existing estimates, a warning might be displayed when saving.
Before estimating the value numerically, it is beneficial to consider how a story should be classified. The circle can be configured to use one of two different systems for Value Classification: Must-have classification and Kano classification.
With the simple is/is not Must-have classification, each story is categorized as either being a Must-have or not being a Must-have. Since a Must-have needs to be included no matter what, there is no real point in estimating its numerical value. It cannot have a value in the sense of prioritization, because it is a requirement. Setting a story as a Must-have will therefore hide the value field. Non Must-haves on the other hand can have a numerical value.
Furthermore, if an epic is set as a Must-have, this will automatically be inherited by all its children, unless they are explicitly categorized as non Must-haves. Read more about working with Must-haves here.
With Kano classification, each story can be classified using more categories. It is still possible to classify a story as a Must-have, which will work exactly as with the simpler classification described above. However, stories can also be classified as Satisfiers and Exciters (and Reverse/Indifferent). Read more about Kano classification here.
A numerical value estimate is the quantification of how much value is obtained by completing a story. If enabled, you can set value estimates for stories and epics, and choose whether or not to accumulate value estimates for epics.
Value Worst-case Estimation
If value estimation is enabled, worst-case estimates can be enabled. If enabled, you will be required to set two estimates for each story: an expected and a 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.
With both an expected and a worst-case estimate, the value uncertainty in percentage of stories can be derived. Read more about working with uncertainties.
Number Series for Value
If no number series is set, value estimates can be freely set. If set, only the digits included here can be set as value estimates.
If a story or epic is not yet estimated, it will count as having no value. Unless a default (provisional) value is set, which will count as the estimate until a real estimate is set. The default value estimate will be shown in brackets e.g. (2).
Default value estimates can be set individually for the different types.
Allowed Methods for Worst-case Value Accumulation
If worst-case value is enabled, the accumulated worst-case value estimate of stories, releases, sprints and preplanned lists can be derived using one of two methods. It depends on whether you assume all the children (cards found under any major card) to be mutually independent (i.e. if one story takes more time, this does not necessarily affect the others) or if you assume the children to be mutually dependent (i.e. if one story takes more time, so will all the rest most likely probably). Based on this assumption, the worst-case value can be derived using either of the two methods:
- Root-sum-squared for mutually independent children – less than a simple sum of worst-case estimates: expected – √(∑(worst – expected)2)
- Simple sum of worst-case estimates for mutually dependent children
Either one or both of these methods can be allowed or disallowed for use in the entire Circle. If both are allowed, you can choose which method to use for each individual epic, release, sprint and preplanned list.
Enabled Value Warnings
This is a list of all the different value warnings that can be explicitly enabled and by so doing, the affected items within the Circle will be flagged with the right warning. Read more about these warnings here.
Value Uncertainty Warning Threshold
For individual types custom uncertainty thresholds can be set to evaluate whether value uncertainties are too high. This will only have an effect if the value warning Value uncertainty is too high is enabled. If the value uncertainty exceeds the percentage threshold, the story or epic will be flagged with the warning.