§11a+ $1b+ $1c + §1d: RICP development is done by teams, each with their own PO (Product owner). §1a: Each team has its own scrum (not kanban) backlog which is generated based on filter that is based on a mapping of components to that team. This mapping of of component-to-team is visible in the RICP repository list page. §1b: For this to work - by convention - we mark each JIRA item only exactly belonging to one component; the primary component. We do not have teams as "JIRA components" - even if that might come in handy for items that are not mapped to a component yet (the PTL can create components in JIRA quite quickly). Two exceptions: the component ricp-integration for team T6 and the component ricp-e2e for team T7. §1c: In board views you see only epics mapped to a component of your team. User stories of your team that are mapped to epics of other teams are only visible if you click on "all issues" in the epic selection box. §1d ...
- T1 (Antti): board #16 (search filter: link)
T2 (Juha): board #17 (search filter: link)team dissolved in Q12020 and work moved to T1 and T3- T3 (Abdulwahid): board #18 (search filter: link)
- T4 (Avinoam): board #19 (search filter: link)
- T5 (Matti): board #20 (search filter: link)
- T6 (Lusheng): board #21 (search filter: link)
- T7 (Bharath): board #22 (search filter: link)
- T8 (Ojus): board #24 (search filter: link) - currently no RIC platform work
- subteam-s1 (Rahul+Arun): list of all items subteam S1 is driving or participating in (link).
- subteam-s2 (Timothy): list of all items subteam S2 is driving or participating in (link).
- subteam-h1 (Alok+Sangeetha): list of all items subteam H1 is driving or participating in (link).
$1e: Subteams are typically small (1-3 developers) and do not focus on specific RICP components. Therefore they do not have their own scrum backlog, but rather the items are managed (JIRA states, subitem management) by the "owning" team (T1..T8) . We mark the fact that a subteam has picked up a JIRA item by marking the item as assigned to a person from that team and at the same time we also add one of the subteam labels (subteam-s1, subteam-s2, subteam-h1) to the item. Subteam members may use the filters in §1d for listing what they are currently planned to work on.
§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. 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. Epics are primarily for very high level release planning and not that relevant in sprint planning.
...
- 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), Bronze-R4: Sprint B.D1 (Feb-03 ... Feb-23)
- RICP_T1 Sprint B.D2 (week 11-13) Bronze-R4: Sprint B.D2 (Feb-24 ... Mar-15)
- RICP_T1 Sprint B.D3 (week 14-16), Bronze-R4: Sprint B.D3 (Mar-16 ... Apr-5)
- RICP_T1 Sprint B.D4 (week 17-19), Bronze-R4: Sprint B.D4 (Apr-6 ... Apr-26)
- RICP_T1 Sprint B.D5 (week 20-22), Bronze-R4: Sprint B.D5 (Apr-27 ... May-17)
- RICP_T1 Sprint B.D6 (week 23-25), Cherry-R5: Sprint B.D6 (May-18 ... Jun-7)
- RICP_T1 Sprint C.P1 (last week of previous release plus week 1 - this is exceptionally only 2 weeks), Cherry-R5: Sprint C.P1 - EXCEPTION in 2020 (3 weeks): Jun-8 ... Jun-28
- RICP_T1 Sprint C.P2 (week 2-4), Cherry-R5: Sprint C.P2 (Jun-29 ... Jul-19)
- RICP_T1 Sprint C.P3 (week 5-7), Cherry-R5: Sprint C.P3 (Jul-20 ... Aug-9)
- possibly add to Cherry-R5: RICP_T1 Sprint C.D1 (week 8-10), Cherry-R5: Sprint Sprint C.D1 (Aug-10 ... Aug-30) *exceptionally added to Cherry-R5 (2020) thereby shortening Cherry-R6
§7: Some useful direct links to Jira:
...