Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira and Jira Align Integration: Switching Between Scrum and Kanban Teams

When switching from Agile type teams to Kanban Type teams:

1. Existing sprints associated to the team will persist in the Jira Align sprint grid.
2. Stories assigned to sprints from the team will maintain their sprint assignment
3. Newly created stories associated to the team and stories that were not assigned to a sprint but were associated to the team will lose their sprint field.
4. The team Room will change to Kanban views for all Team data being driven by throughout and PIs as opposed to sprints

When switching from Kanban type teams to Agile Teams:
1. The Team Room will change from a Kanban view back to the traditional scrum sprint view.
2. Stories associated to the team that did not have a sprint field will gain a sprint field.
3. Stories that maintained a sprint field if they were previously Agile will maintain their sprint field.
4. Stories without sprints (legacy stories) will be in the unassigned team backlog

Notes:
1. Kanban Teams are driven by PI. So it will be important to ensure PI's are assigned for the Kanban team's associated work.
2. If you flip from Agile to Kanban the stories that were in an active sprint will still be associated to that active sprint.
3. If you flip from Kanban to Agile then assign stories to an active sprint it would be reflected as scope change
4. There is an open bug tied to being unable to flip Kanban Teams back to Agile if there are multiple teams with the same Sprint Prefix which can be tracked here: https://jira.atlassian.com/browse/JIRAALIGN-809

Please let us know if there are any additional questions on specifics in the comments below!

Cheers!
Tim

7 comments

Is this scenario for changing from Scrum to Kanban / Kanban to Scrum where the teams live only in Jira Align?  Or, is this also true when at team in JIRA, that is synced to Jira Align, switches from Scrum to Kanban or Kanban to Scrum?

Tim Keyes Atlassian Team Aug 25, 2020

Hi @Shane Manke

Thank you for the question.  This scenario would be true whether or not the board (team) was integrated in Jira and whether or not the board was Kanban or Scrum type in Jira.  The Team type in Jira Align is the determining factor immaterial of the board type in Jira.


Cheers!
Tim

Hi Tim, 

Thanks for the article, its super helpful. I'm curious if when a team is changed from Agile to Kanban or vice versa, is there any impact/changes on historical data or forecasting? I suppose for forecasting that would depend on the team's velocity/throughput, but do you know how that is impacted when changing team type?

I'm also happy to see that the bug you mentioned is no longer open, but Closed - Fixed. Nice. 

Thanks!

Tim Keyes Atlassian Team Feb 18, 2021

Hi @Tracy Walton 

Thank you for the question.  I would reference the notes section of the article to look into specific scenarios and whether you are changing scrum to kanban or vice versa.

2. If you flip from Agile to Kanban the stories that were in an active sprint will still be associated to that active sprint.
3. If you flip from Kanban to Agile then assign stories to an active sprint it would be reflected as scope change


The historic data will persist on the backend it just might not be relevant to how forecasting is conducted for scrum/ kanban teams or how the data is rendered within the product.  For Dependency/ Objective delivery on the Program Board Stories associated to Scrum teams will have target completion dates based on the end date of their Scrum sprint while Stories associated to Kanban teams will have target completion dates based on the end date of the week of their expected completion based on backlog prioritization and the team's throughput. Referenced. This could lead to a delta between the target completion date for stories after changing the team type.

Outside of that there would be scope change for sprints that receive Stories mid sprint that were historically associated to a Kanban team.

 

Cheers!
Tim

Thanks @Tim Keyes , 

Follow up question on throughput.  If a team is configured to "Use calculated throughput", which is calculated based on the team's previous five weeks, does it matter if the previous five weeks they were an Agile team and not a Kanban team? Or will I need to use the Override Value when switching? 

 

Screen Shot 2021-02-18 at 9.02.47 AM.png

Tim Keyes Atlassian Team Feb 18, 2021

Hi @Tracy Walton,

Changing from an Agile team to a Kanban team will factor in stories that were historically accepted into the throughput calculations.  I have verified the functionality in one of our test sites.


Cheers!
Tim

@Tim Keyes Fantastic, thanks so much for verifying! 

Like Tim Keyes likes this

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Align

Helpful hints if you're rolling Align out to your entire enterprise

(Or, What to expect when you’re expanding.) Once you've completed your Jumpstart, or your initial assessment of Jira Align, you'll start to think about how you can roll it out to the rest of your e...

1,685 views 7 33
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you