Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

§4: The workflow is generally (a) TO DO → (b) selected for development → (c) in progress → (d) in review → (e) done. For now we do not have a state "ready for acceptance". If really needed, we can use "The state "in review" as a state that describes the situatio 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 (originally suggested by TelA. 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. 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.

...