Now that we have seen how to run projects with Scrum, it is time to take a look at the other agile methodology Jira Software supports—Kanban. Compared to Scrum, Kanban is a much simpler methodology. Unlike Scrum, which has a backlog and requires the team to prioritize and plan their delivery in sprints, Kanban focuses purely on the execution and measurement of throughput.

In Jira, a typical Kanban board will have the following differences compared to a SCRUM board:

• There is no backlog view by default. Since Kanban does not have a sprint-planning phase, your board acts as the backlog. We will see how to enable backlog for Kanban in later sections.
• There are no active sprints. The idea behind Kanban is that you have a continuous flow of work.
• Scrum and Kanban have different type of reports that are specifically designed for each of the methodologies.
• Columns can have minimum and maximum constraints.
• Columns will be highlighted if the constraints are violated. As we can see in the following screenshot, both the Selected for Development and In Progress columns are highlighted because of constraint violation: