Recommended Epic scope
In order to give you fast feedback on whether your solution hypothesis is correct, each Epic should meet one of the following criteria:
- a deliverable that, when completed, will "move the needle" on at least 1 Key Result
- work required to give you the information you need to set a reasonable target for one or more Key Results
- work required to build a system for measuring the metric for a Key Result
Just-in-time hierarchical decomposition of Epics
It's typical for teams to not decompose Features into Stories until they are ready to work on them. In this "just-in-time" approach to Feature decomposition, teams assign a rough estimate to each Feature, knowing that this estimate will be obsolete once the Feature has been decomposed. The rough estimate for the Feature is still valuable for estimating the size of the parent Epic.
OKRsignal supports this "just-in-time" way of working by using only estimates from an Epic's leaf nodes to estimate the total size of the Epic. OKRsignal automatically traverses the Epic > Feature > Story hierarchy each time it does any calculations, and uses only estimates for the leaf nodes in this hierarchy. When a Feature is decomposed into Stories, the Feature is no longer a "leaf node" because it now has child Stories. OKRsignal ignores the Feature's estimate and uses the child Story estimates.
