Cost estimation and Value estimation can be synchronized for delegated stories. Whether or not cost and value is kept in sync is configured for individual circle relations. It is thereby possible to e.g. keep cost in sync for some delegations between two specific circles, and not for delegations between other circles. An important remark is that value and cost should only be synchronized if the two circles use the same scales/references and units for estimation – otherwise cost and value should be kept in sync manually!
Note that only cost and value synchronization is configurable. The title, user story, state, etc is always kept in sync no matter what – and assigned to and planning is never kept in sync.
When you switch whether or not to synchronize cost and value, the system will automatically update all delegated stories. Since this might result in overwriting existing estimates, a warning might be displayed when saving.
Read more about the general principle of delegation here.
Synchronize cost for delegated
If cost is synchronized, effort, monetary cost and Cynefin estimates can only be set in the circle where the story is delegated to, because this is where the actual work completing the story takes place. The cost estimates will then automatically be mirrored to the other circle (the circle delegated from), allowing users in that circle to see the cost estimates and use them to e.g. keep track of accumulated cost for parent epics and releases.
If the delegated epic is decomposed into stories and set to accumulate cost in the circle delegated to, these estimates will also be mirrored to the circle delegated from – even though the epic on this side have no children. Users in the circle from which the epic is delegated cannot choose whether to accumulate cost – this is entirely controlled by the circle which the epic is delegated to.
If cost is not synchronized, it can be edited independently on both sides without interfering.
Synchronize value for delegated
If value is synchronized, numerical value and Kano/Must-have estimates can only be set in the circle where the story is delegated from, because this is where the story is requested and therefore those who should have an idea about the value. The value estimates will then automatically be mirrored to the other circle (the circle delegated to), allowing users in that circle to see the value estimates and use them to e.g. keep track of accumulated value for parent epics and releases.
If the delegated epic is marked as a Must-have in the circle delegated from, and then decomposed into stories on the other side, the children of the epic will inherit the Must-have state. Even though value cannot be set in the circle delegated to, a decomposed delegated epic will still accumulate must-haves to show if all, none or some of the children are marked as Must-haves. Read more about working with Must-haves.
If value is not synchronized, it can be edited independently on both sides without interfering.
