§1: 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 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.
- T1 (Antti): board #16 (search filter: link)
- T2 (Juha): board #17 (search filter: link)
- T3 (Abdulwahid): board #18 (search filter: link)
- T4 (Itamar): 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
§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.
§3: To access JIRA or to be assigned JIRA items you must have a free LF (Linux Foundation) account and you must have logged in at least once into LF's JIRA. Please ask your team mates to do so.
§4: The workflow is generally (a) TO DO → (b) selected for development → (c) in progress → (d) in review → (e) done. The state "in review" is a bit badly named, but it is optional for teams to use and it describes the situation that a development team considers the item as done, but the PO (product owner or similar representative/delegate of the team) has not formally accepted it yet. As of Jan-2020 this state only used by team T4 (Itamar).
§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. A release ZZZ_future is used to indicate items that are not yet planned to be worked on any time soon. A release ZZZ_never is used to indicate items we never plan to work on (Jira's Resolution field (with the state "won't do") is not used for anything). This way at least (new) epics that do not have any release version as "fix version", must be analyzed still on when they are to be worked on.
§6: Each team creates their own 3 week sprints (and names) as per the 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), Bronze-R4: Sprint B.D1 (Feb-03 ... Feb-22)
- RICP_T1 Sprint B.D2 (week 11-13) Bronze-R4: Sprint B.D2
- RICP_T1 Sprint B.D3 (week 14-16), Bronze-R4: Sprint B.D3
- RICP_T1 Sprint B.D4 (week 17-19), Bronze-R4: Sprint B.D4
- RICP_T1 Sprint B.D5 (week 20-22), Bronze-R4: Sprint B.D5 (Apr-28 .. May-17)
- RICP_T1 Sprint B.D6 (week 23-25), Cherry-R5: Sprint C.D6
§7: Some useful direct links to Jira:
- Filter: All items mapped to sprint "Sprint B.P1" : filter10308 (adapt filter string (13,14,...) to point to sprint names for the sprint your are interested in. Note you need to list seven sprints, as each team (RICP_T1..7) has its own sprint).
- Filter: All items mapped to release Bronze mapped to your team: use filters from §1 and add this to the search filter: "AND fixVersion in (Bronze-R3,Bronze-R4)" before the "ORDER" part of the filter.
- Filter: All RICP items (epics, user stories, ...) mapped to release Bronze: filter10400 and bronze-epics only (i.e. no user stories or others) filter10401 and bronze-R4-epics only filter10509.
- Filter: All RICP items that are not yet done: all = epics only + non-epics.
- Test Epic and test user story Use RICP test epic RIC-42 and the linked test user story RIC-43 to experiment with JIRA. Right now these are mapped to team/board for team T1: board #16 .
- All Epics (not only RICP): link
- To delete an item please add the string "DELETE_ME" into the summary of the item. The RICP PTL (Thoralf Czichy ) will delete such items every once in a while using this filter: filter10510. Additionally, you may also send an e-mail to the PTL asking for deletion of an item.