...
§5: The workflow is generally (a) TO DO → (b) selected for development → (c) in progress → (d) done. For now we do not have a state "ready for acceptance". If really needed, we can use "in review" as a state that the development team considers the item as done, but the PO (product owner or similar representative7delegate) has not formally accepted it yet (originally suggested by TelA).
...
§8: TODO-discuss: Each team creates their own 3 week sprints (and names) as per this naming scheme below which is aligned with the Bronze (B) and Cherry (C) timeline: . P1-P3 are mapped to "release planning sprints". D1-D6 to "release development (and integration) sprints".
- RICP_T1 Sprint B.P1 (last week of previous release plus week 1 - this is exceptionally only 2 weeks),
- RICP_T1 Sprint B.P2 (week 2-4),
- RICP_T1 Sprint B.P3 (week 5-7),
- RICP_T1 Sprint B.D1 (week 8-10),
- RICP_T1 Sprint B.D2 (week 11-13),
- RICP_T1 Sprint B.D3 (week 14-16),
- RICP_T1 Sprint B.D4 (week 17-19),
- RICP_T1 Sprint B.D5 (week 20-22),
- RICP_T1 Sprint B.D6 (week 23-25)