Hi @TFG Transfracht
How does a story move between the Development and Testing Teams?
For example, is this two separate issues (one for development, one for testing) - or is "done" for a developer a status part way through the workflow?
If it's the latter - a method I've seen used in the past is:
- Create two boards - one for development, one for testing
- Place the last status in the development board in their last column - from a report perspective, this is viewed as "done" for that board
- Set the same status within the first column for the testing board - treated as "to do" from a report perspective in this instance
- Map each team's statuses before (development) and after (testing) this linking status on each respective board
^ This means that issues which are done in one board are ready to be worked on in another!
This should be fine if it's a Kanban board - once the issue moved into the next status it will drop off the board. If it's a Scrum board and issues can continue to move in the same sprint, then the issue would be classed as "removed from sprint" - in this instance, you might want to put the last development status and all testing statuses in the last column of the development board, so it remains visible from a sprint completion / reporting perspective.
If this isn't what you're looking to achieve, please provide more information based on the questions above!
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.