|
Features needing a 1-pager
Update the SpecStatus of features that need a 1-pager, or mark the feature as SpecStatus=Not Needed. |
|
|
Features in the past should be either closed, or moved to the target quarter or CLE\Future
Features that are in the past should be closed if completed. Otherwise, update Iteration Path. |
|
||||||
|
Features missing a SWAG
P1/P2 features should have at least one PBI with the Story Points field set. Story Points may be set to zero to indicate no engineering work is required |
|
|
Features in the future should be marked as 'New'
For proper tracking, features that are not being worked on should be marked as State=New. |
|
||||||
|
Features with planning issues
This section keeps track of P1/P2 features tagged as PlanningIssue, meaning they need some attention to unblock the planning. Once the issue is resolved and planning is unblocked, remove the PlanningIssue tag. |
|
|
Ongoing quarter's P1 and P2 features should be 'Approved' or 'Active'
If the work is actually happening this quarter, set Status='Approved' or 'Active'. Otherwise, set Priority=3 (if Painful Cut) or move the feature to the target quarter or CLE\Future. |
|
||||||
|
All features should be parented to an initiative
Features are too granular for conversations with RDX LT. Initiatives provide a higher abstraction level by grouping multiple features accruing to a given business outcome. One-off features could be grouped under "BAU" initiatives, e.g. BAU - One-off Partner asks. |
|
|
P3 features should not be 'Approved' or 'Active'
If the work is actually happening, set Priority=1 or 2. Otherwise, set State='New' and move the feature to the target quarter or CLE\Future. |
|
||||||
|
All Moved In tags should be reset at the beginning of the period
Moved In tags should be cleared from features at the beginning of the period. |
|
|
All Moved Out tags should be reset at the beginning of the period
Moved Out tags should be cleared from features at the beginning of the period. |
|
||||||