3 different JIRA boards (3 different teams), with a 4th "masterboard" which combines all of them?

Question

Hey,

we're a scrum team with 3 different "areas". we are all working on the same sprint.

- first there are business analysts, specifying tickets. they use the columns "To do", "Doing" and "Specified"

- secondly there are developers, which implement those said tickets. So they grab the tickets from the "Specified" column of the BA's(=business analysts), put them into "In Progress" column while they're working on it. When they are done with it, they swap it over to "Fixed" column. When they end their working day, they put the fixed tickets into the column „In Deployment“. The next morning we have a automated deployment which brings those changes online.

- and thirdly we have testers, which test those implemented tickets. Each morning testers grab all the tickets which are in "In Deployment" column and put them into „Ready for Test“ column. Testers choose a ticket to test from the „ready for test“-column and put them into the status colum "In Testing" while theyre working on it. After they're done with that, the ticket goes to "PO Review"-column if the test was successful, or gets thrown back into "Specified" Column if it failed and a new cycle begins(at this point BA’s and developers are looking into it whether the ticket needs better specification or if developers implemented it wrong). If testers stumble upon a blocker while testing a ticket, they put the ticket into the „Tested“ column, waiting for the blocker to be dissolved to finish the test.

so as you can see for now we are all using 1 JIRA board together. see this screenshot:

i'd love to still remain this board as a "masterboard", which is good for our (online-)dailys to keep everything as transparent as possible. but additionally I'd love to have for each team 1 extra board, which is derived from the masterboard.

Example:

business analysts would have their own board with the same columns from masterboard "To Do", "Doing" and "Specified"

developers would have their own board with the same columns from masterboard "In Progress", "Fixed" and „In Deployment“. Additionaly they can see „Specified“ column (which contains all tickets ready for development) on their own developer board, so they can grab new tickets to work on.

and also the testers would have their own board with the same columns from masterboard "Ready for Test", "In Testing", "Tested" and "PO-Review". Additionally they can see „In Deployment“ on their own tester board, so they can grab those new implemented tickets and put them into „Ready for Test“

so the moment a developer puts a ticket into their „In Deployment“ colum on their own board, the same ticket gets visible on the tester board in the same colum „In Deployment“

same goes for „Specified“ ticket from Business Analyst board. As soon as a ticket reaches that status column, it gets visible on the developer board in the colum „Specified“

I hope I described it well, I’m looking forward to answers whether this is possible.

----

another point im trying to achieve with it:

i'd love to have 3 different estimation values on tickets. so in backlog refinements, when we are estimating tickets, we are getting 3 different values. for example BA's estimation, developer estimation and tester estimation.

and only the relevenant estimation value for each "team-board" gets shown on each ticket.

example: so if there is a ticket which got estimated with 1 point for BA's, 3 points for developers and 5 points for testing, if you are on the test-board right now you would see said ticket with 5points estimation. while if you are on the developer board, you see the estimation of 3points. and if you are on the masterboard, you see all 3 (if possible).

Chris Buzon · Answer

It's theoretically possible to have any number of fields that could be used for story point estimates, but I don't think making several custom fields for that purpose makes much sense. It's a lot of work for what I think is better fixed through team process.

I think the right way to do this would be to split the tickets into parts that are measured individually. There are some add-ons that can do what you want though, for example "Sum it Up!" .

You might want to discuss the options with your scrum masters or Project/Program managers for their thoughts on it, however.

inahgiam · Answer

thank you very much for your answer. so the idea i have is possible, thats great!

what about the different estimation values though? is it possible to have multiple estimation values (story points) for one single ticket?

or do we need to split a ticket apart into multiple tickets and label them? and then each ticket gets their own estimation value?

Chris Buzon · Answer

yes, this is possible.

It can be achieved in several ways too.  Quick filters would allow you to just show the tickets based on story points if you wanted.  Think of them as a filter that works ON TOP of the filter that drives the board.

You can also duplicate that board, then change the query that drives it to just see each of the teams you're looking for.  You could also just make 3 new boards, each using a query similar to the one the main board uses, but narrowed down to just see the work specific to each team that uses it.

The restriction you need to keep in mind here is that statuses/workflow steps are what you actually place within a column on the board. They can only exist in 1 column on each board, but on other boards can be in any column, or not tracked on the board at all.