...
§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§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 has not formally accepted it yet (originally suggested by TelA).
§4§6: TODO Do we introduce a field called "real component" and continue the versatile JIRA field "component" to be used as team.
§5§7: 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§8: 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:
...