I have a project that I inherited that is not set up how the team wants it to operate into the future.
I have a project that is set up with a Kanban board. So, I have the Kanban board with its columns and also a backlog list. When I view the backlog I see one of the columns in the Kanban board at the top of the backlog view as a group then I see a group of backlog items that have not been added to the board. When an item is moved to a later state in the Kanban workflow, it no longer appears in either the workflow state seen on the backlog view nor in the backlog state on the backlog view.
The team still wants to move to sprints. For an active Sprint, they want to manage it using a Kanban-style view. But they want to be able to plan future sprints. So, they want the backlog view to show the backlog and then groups for each planned sprint.
How do I shift from the current state to the future state?
Welcome to Atlassian community!
Analyzing the description of your Future State, it seems your team is looking for a Scrum Board, where you can organize and track your teamwork based on Sprints.
In fact, you can create and plans future Sprints in a Scrum board, grouping your Stories into Sprints that are ordered by execution and having a backlog view for the not planned Stories.
In order to use the mentioned view, you can simply create a Scrum board by performing the steps below:
1 - Navigate to your current Kanban Board > Click in the board menu > Create new board:
2 - Choose the option Board from an existing project and choose the options of the client as you want
3 - Once it is created, create your Sprints as you need and map the issues according to your team progress
Additionally, you can check the differences between Kanban and Scrum in the link below:
P.S: you can switch between your current Scrum board and the inherited Kanban project by the board menu, in case you would like to compare both and configure any similarities.
Let me know if this is the option you are looking for.
The way both classic and Next-gen boards work are similar, the main difference is that Next-gen customization options are very limited, not allowing you to configure a custom board filter, Card layouts, and many other features available for the classic board.
In fact, the Next-gen template was designed for those users who felt overwhelmed by the complexity of JIRA Classic template and requested a simpler option, straight to the point with fewer options of customization.
Let me know if there is anything specific you want to know about it.
Thank you for reaching out.
Although there is not a simple button to convert a Kanban board to Scrum, can you please try the steps I provided in my first answer to Todd?
Performing those steps, you will create the exactly same board you currently have in your project with the same issues, however, using the Scrum methodology (Sprints) instead of Kanban.
That would be the easiest way to convert your project/board to Scrum.
Let me know if it works for you.
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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