-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: None
-
None
-
2
Currently, Jira Align in based on an idealised version of SAFe in which nothing ever spills over from one program increment to the other. This isn't realistic.
The current experience means that for any features that are not finished in a Program Increment, we have to split the feature and put the second part of the feature in the next increment, even if it's only one or two stories left.
This creates unnecessary admin and is confusing for Product and other stakeholders who are trying to track the overall value of a feature.
It also means that lead and cycle time of features in Jira Align is not representative of the actual time it took to deliver the value defined in the original feature.
A better experience would be to use the same approach as with Epics in Jira Align, where multiple quarters can be tagged to a feature. This would give us the ability to track the complete object over multiple quarters where necessary and give an accurate indication of lead and cycle time.
- is related to
-
ALIGNSP-28938 Loading...