Would Jira Kanban project pose any challenge in Jira Align with respect to dependency mgmt?

[Vinay Sharma]

We have Jira and Jira Align integrated. We are changing a Scrum Project to a Kanban project in Jira (Team project). Would it pose any challenge with respect to dependency management since it would not have target Sprint to plan the dependency completion (Needed By - Sprint & Committed By - Sprint)

Are there any other place(s) Kanban team project would pose challenge?

[Mark Cruth · Accepted solution]

@Vinay Sharma - in regards to dependency management, when you change a team from a "Agile Team" in Jira Align to a "Kanban Team" the Need By and Committed By dates will change to a date picker (vs selecting an anchor sprint). Here's what happens based on which team is changed...

• Requesting team is changed to a Kanban Team, the "Need By" date will change to the last day in the selected anchor sprint (eg. Sprint 27 changes to 6/30/2021)
• Requested team is changed to a Kanban Team, the "Committed By" date will be cleared out, but the dependency will remain committed if previously committed (this is a weird user experience, by can be easily remedied by updating the issue)

In regards to other implications of Kanban Team, take a look at this page:

https://help.jiraalign.com/hc/en-us/articles/360024712994-10X-Kanban-Teams-Overview-Jira-Align-Labs-

I hope this helps!

Mark

[Vinay Sharma]

Thanks Mark! It helps!