Starting sprints with a Kanban project - will there be limitations that we'll run into?

[lborncamp]

Hi,

Our project is set up as a classic Kanban one. Now we'd like to start using sprints and follow the Scrum methodology. We've added a new Scrum Board to our project so we can assign tasks to a sprint, which allows us to add estimates to an issue.

We have to decide if we should set up another project as Scrum and transfer the issues to that new Scrum project or if we can continue under the Kanban project with a Scrum Board. 

From what I can tell, the difference is that when a project is set up as Scrum, you can add time estimates to issue as you create the issue, whereas with a project set up as Kanban you cannot. However, the addition of a Scrum board allows estimates when working in the Backlog of that board.

Question: Are there some unforeseen things we should know about that we'll find out later that would prevent us from taking full advantage of what Jira offers in terms of following Scrum methodology if our project was not set up as a Scrum project? 

Thanks, 

[Stephen Wright _Elabor8_ · Accepted solution]

Hi @lborncamp

There are no Kanban or Scrum projects - just project templates that provide a set of standard fields / workflow steps / etc depending on which one you choose.

In classic, there are only Kanban and Scrum boards - where their behaviour differs. Setting up a Scrum board to replace your Kanban board won't cause an issue - although I'd suggest not controlling issues from both boards as it could impact ranking between the two.

If there are fields that you'd like to add to your existing project (based on time estimate fields comment above) - as a Site Admin you can:

• Go to Jira Settings > Issues > Screens
• Locate the screen in question for your project
• Add / Remove fields from here

Ste

[lborncamp]

Very helpful. Thank you, Ste!

[Warren · Accepted solution]

Hi @lborncamp 

Totally agree with what Stephen has said. We did it the other way around - we had a project which had a Scrum board and after 3 years we decided to move to Kanban. All we did is add another (Kanban) board and that's been working well for more than a year now.