Agile Development

The ServiceNow® Agile Development application is an iterative and incremental process for software development environments. Agile Development application is enhanced with Agile Development 2.0.

Previously, there were the following two places for supporting agile based execution:
  • Agile Development module. If you have not upgraded to Agile Development 2.0, see the documentation at Agile Development (for upgraded customers only) for agile development.
  • Agile under Project Management. See the documentation at Agile integration with Project Portfolio Suite for project-based agile development.
    Note: If you are an existing Agile Development user on a release prior to Jakarta, you are using Agile Development activated through the Agile Development (com.snc.sdlc.scrum.pp) plugin.

Agile Development 2.0 provides a unified agile development environment for release, and/or project-based delivery. Refer the documentation at Agile Development 2.0.

The table provides a high-level overview about how Agile Development 2.0 enables a unified agile development environment and provides an enhanced experience. It is not mandatory for existing customers to activate this plugin. However, you should use the new plugin to take advantage of new features.
Feature Agile Development

(PPS and existing customers)

Agile

(Project Management)

Agile Development 2.0
Backlog A story can be associated to a product. A story can be associated to only a project. A personalized backlog can be created by defining filter criteria.
Release A story can be associated to a release. A project story cannot be associated to a release. A release is a definite timeline to execute prioritized stories from backlog.
  • Project-based execution - It allows release backlog to be executed as one or more projects.
  • Non project-based execution - It allows release backlog to be executed by one or more assignment groups using their sprint schedules within a release timeline.
Theme and Epic A story can be associated to a theme, or epic. A story cannot be associated to a theme, or epic. Backlog stories can be categorized by themes and epics.
Team versus Assignment Group Release Team is used. Assignment Group is used. Assignment Group is used to create an assignment group of type Agile Team. The confusion between when to use release team versus assignment group is eliminated. An existing release team can be converted into an assignment group.
Sprints Sprints are release-based. Each team cannot have a different sprint schedule. Sprints are assignment group based. Each group can have its sprint schedule. Sprints are generated for Assignment Groups. Different groups can use different sprint schedules or all the groups can follow the same schedule.

The Agile Board Sprint Planning tab is used to create sprints.

Sprint Planning The Planning Board is used. The Sprint Planning Board is used. The Agile Board Sprint Planning tab is used.
Task Progress board and Story progress board The Task Progress board and Story progress board are used. VTB (Visual Task Board) is used. The Agile Board Sprint Board tab is used.

Upgrade and new customers

To use the new agile functionality, customers must upgrade or activate the Agile Development 2.0 plugin, which requires Project Portfolio Suite with Financials to be installed.