§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.
...