nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

One project, 2 boards

Pebble Hlubi

Hi All

I have been battling with sprint reports due to QA that doesn't always cover all the Dev Complete issues within a Sprint and therefore skews my reporting.

I have resorted to working with duplicate boards (Board A Dev - To Do, Dev In Progress and Done) and Board B which is essentially QA Board (Duplicates from Board A To Do, Dev In Progress and Done and has 3 additional columns Ready for QA, QA In Progress and QA Complete)

The structure of the boards works well for the team as once a card is Dev Complete and ready for QA the Devs move it on the Board B to Ready for QA.

The problem now is that when the cards are tested and have passed QA (on Board , they need to reflect/reverse back on/to the Done column so that I can complete the Sprint and reflect the cards that are actually done in terms of testing. This conflicts now because Done is already used for Dev complete.

Is there a better way to manage this or just have 2 separate boards to monitor Dev and QA independently?

Accepted answers

Jack Brickey

Hi Pebble (great name BTW!) and welcome to the Community!

I had a very similar situation and solution in a previous life. Ultimately I elected to completely separate QA from DEV. For the sake of explanation simplicity lets just say my workflow was To Do --> In Progress --> Done. Here is what I did:

I would create two tasks for one Story: Story1_Dev and Story1_QA, e.g. Develop New UI Search Field and Test New UI Search Field
I would link the two e.g. Test New UI Search Field is blocked by Develop New UI Search Field
When Develop New UI Search Field was DONE then the QA scrum master of kanban master could elect to move the testing forward.

Now, this isn't ideal in an agile world but we don't always live in an agile world.

Scott Theus

Hi Pebble,

If I am reading your post correctly, QA Complete is the same as Done and there is not another status in between. Is that right?

If so you could probably eliminate the QA Complete status and just have QA mark the issue Done once it passes testing and put the Done status on the QA board as well.

If there is another step where the SM or PO reviews the QA Completed items before moving them to Done and completing the sprint, you could add the QA Complete status to the Dev board.

-Scott

All comments

Jack Brickey

Hi Pebble (great name BTW!) and welcome to the Community!

I would create two tasks for one Story: Story1_Dev and Story1_QA, e.g. Develop New UI Search Field and Test New UI Search Field
I would link the two e.g. Test New UI Search Field is blocked by Develop New UI Search Field
When Develop New UI Search Field was DONE then the QA scrum master of kanban master could elect to move the testing forward.

Now, this isn't ideal in an agile world but we don't always live in an agile world.

Scott Theus

Hi Pebble,

If I am reading your post correctly, QA Complete is the same as Done and there is not another status in between. Is that right?

If so you could probably eliminate the QA Complete status and just have QA mark the issue Done once it passes testing and put the Done status on the QA board as well.

If there is another step where the SM or PO reviews the QA Completed items before moving them to Done and completing the sprint, you could add the QA Complete status to the Dev board.

-Scott

Pebble Hlubi

Thanks a ton Jack for the name compliment and the response. Its helpful indeed. Like you say Agile as we like to be we can't always live up to it. Thank you so much

Pebble Hlubi

Thank you Scott. There's a step in between and looks like it would be best to just have separate boards and eliminate any more issues and challenges.

Scott Theus

Perhaps you could add that in-between step to both boards? That's an easy edit for the boards, and if it doesn't work for you it's easy enough to change back.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud