§1: RICP development is done by teams, each with their own PO (Product owner). Each team has its own scrum (TODO-not-kanban) backlog which is generated based on filter that is based on a mapping of components to that team. This mapping of component-to-team is visible in the RICP repository list page. For this to work - by convention - we mark each JIRA item only exactly belonging to one component; the primary component. TODO-to we also have teams as "JIRA components" for items that are do not have a primary component?
- T1 (Antti): board #16
- T2 (Juha): ...
§2: Backlog sprint planning is done for JIRA (user) stories. Stories are linked to higher-level JIRA Epics (which from team planning perspective are not particularly interesting) via the "Epic link" property of a story. TODO-proposal Epics can be either project specific, e.g., a RICP EPIC, or RSAC-defined (o-ran-sc's Requirement steering and architecture committee) Epics that touch many subprojects. TODO any further discussion needed on the use of Epics
§3: TODO how to make sure that everyone has access. Proposal: likely this requires that someone has logged in at least once to JIRA. Suggest to ask everyone to do so.
§4: 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 has not formally accepted it yet (originally suggested by TelA).
§4: TODO Do we introduce a field called "real component" and continue the versatile JIRA field "component" to be used as team.
§5: JIRA has a concept of releases (aka versions). We use this naming convention: Bronze-R3, Bronze-R4, Cherry-R5, Cherry-R6. R3 and R4 are the first and second half of Bronze.
§6: TODO-discuss: Each team creates their own 3 week sprints (and names) as per this naming scheme aligned with Bronze (B) and Cherry (C) timeline:
- 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)