---
sourceDocument: Australia Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-business-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Scrum and Kanban teams in an ART in EAP

# Scrum and Kanban teams in an ART in EAP {#ariaid-title1}

Release version: Australia  
Updated October 27, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Run Scrum and Kanban teams side by side in one Agile Release Train (ART) in Enterprise Agile Planning by setting the planning methodology for each Agile Team.

An ART can include teams that work in different ways. Each Agile Team follows one of two planning methodologies, Scrum or Kanban.

## Scrum and Kanban teams comparison {#scrum-and-kanban-teams-in-eap__section-methodology-compared}

Scrum
:   The team plans work in Sprints. Sprints follow the planning calendar of the team or its ART.

Kanban
:   The team works from a continuous backlog. Kanban teams have no Sprints and don't use the shared calendar of their ART.
{#scrum-and-kanban-teams-in-eap__dl-methodology-compared}

## Kanban team differences {#scrum-and-kanban-teams-in-eap__section-kanban-team-differences}

Because a Kanban team doesn't use Sprints, the following differences apply:

Backlog
:   The Create Sprint button isn't available on the team Backlog.

Sprint creation
:   When you create a Planning Interval for the ART, or add child Sprints, Sprints are created for Scrum teams only. Kanban teams are skipped.

Story forms
:   The Iteration field is hidden on the forms of stories assigned to a Kanban team.

Sprint states
:   You can't change the state of a Sprint that belongs to a Kanban team, except to complete or cancel it.

Home tab
:   The Home tab of a Kanban team shows the Kanban Team dashboard instead of the Scrum dashboards. For more information, see [Kanban Team dashboard in EAP](https://www.servicenow.com/docs/m3PFQ0Kffq024bFoksv~7Q "The Kanban Team Dashboard in EAP provides the work item status and progress metrics for the Agile teams following the Kanban configuration in the Enterprise Agile Planning (EAP) workspace.").

Planning board
:   The Planning board of an ART doesn't display its Kanban teams, because they don't use iterations. A message indicates that some teams might not be displayed. For more information, see [Perform PI planning in EAP](https://www.servicenow.com/docs/Kw8BsQanqnS0V1VTlVaouA "Using the Planning board of Enterprise Agile Planning, plan work for multiple teams across iterations (for example, Big Room Planning). Track the progress of work, create and visualize dependencies between work items, and reschedule work to react quickly to changes while confirming alignment with business priorities.").
{#scrum-and-kanban-teams-in-eap__dl-kanban-differences}

## Team planning methodology {#scrum-and-kanban-teams-in-eap__section-set-methodology}

The Planning methodology field appears above the Calendar field on the Agile Team form. New teams default to Scrum. ARTs, Solution Trains, and Portfolios don't have this field.

When you add Agile Teams to an ART, you choose the planning methodology first. The choice applies to all teams that you add in that batch. For more information, see [Define agile structure in EAP](https://www.servicenow.com/docs/3HEluJdJGFXClPgjy_2dfw "Add organizational entities and teams to an Enterprise Agile Planning (EAP) configuration so that users can plan work for them in the EAP Backlog and Planning Board.").

## Methodology after an upgrade {#scrum-and-kanban-teams-in-eap__section-methodology-after-upgrade}

When you upgrade, existing Agile Teams that have a calendar of their own or a calendar from their configuration are set to Scrum. All other existing Agile Teams are set to Kanban.

## Team methodology changes {#scrum-and-kanban-teams-in-eap__section-change-methodology}

To move a team from Scrum to Kanban, see [Switch an Agile Team to Kanban in EAP](https://www.servicenow.com/docs/EWwitmT7E3smge0Bg~G4tA "Change the planning methodology of an Agile Team from Scrum to Kanban in Enterprise Agile Planning so that the team works from a continuous backlog instead of sprints."). Switching a Scrum team to Kanban cancels the current and future Sprints of the team.