Best Practices working with multiple consecutive sprints

rcdpanjaitan

Hello

currently we have one project where we have 2 consecutive sprints running paralel by 2 different teams. sometimes it have the same period (start and end sprint) but sometimes not. 

i know that jira already support to have consecutive sprints 

but, i want to ask what is the best practice of having this case in terms of:

- filtering

to separate the work of these two teams, do you use filtering? based on what usually? 

- status-es

can we apply different status for each sprint board?

for example for team A, the status is more simple: to-do, in progress, done

while for team B, the status is more complex: to-do, discovery, in design, tech review, done

if it's possible how to do so? 

- dashboard reporting

for dashboard, jira already have so many gadget that we can directly use. but again, filtering is pretty useful here. what kind of dashboard that u use to report each sprint?

Nic Brough -Adaptavist-

I am very confused here, you talk about consecutive sprints in the same sentence as parallel sprints - these are the opposite of each other.  Do you mean "concurrent" instead of "consecutive"?

Either way, we can answer most of the questions, as it doesn't matter which way you're working with sprints.

Yes, use the board filters to define what each board selects and displays

This can be based on status if you want it to.  The status is a function of the workflow in the projects the boards select the issues from though, so you have to set up the projects and issues to follow the workflow you need, then tell the board what to select

I tend to use dashboards that contain gadgets that show me what is happening that matters to me and my team.  The sprint health gadget can be quite a good starting point, but I can't really tell you how you want to report on your own processes and data