Agile Development

The ServiceNow® Agile Development application helps you manage and track software development lifecycle through an iterative, incremental, and flexible approach.

When you have multiple standalone tools for development, testing, and project tracking, there is a disconnect between enhancements and fixes, originating operations, change processes, and deployment. Agile Development pulls these software development lifecycle work flows together in one system. Agile Development manages scrum or waterfall development, and manages the backlog of tasks throughout the lifecycle, from inception through testing and deployment. Ultimately, you gain increased visibility into the entire software development lifecycle.

Prior to Jakarta, there were the following two places for supporting agile based execution:

Agile Development 2.0

Starting with Jakarta, Agile Development 2.0 also supports agile based execution. It 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 provides a unified agile development environment, and offers an enhanced user experience. It is not mandatory for existing customers to activate the Agile Development 2.0 (com.snc.sdlc.agile.2.0) plugin, however, you should use this plugin to take the advantage of enhanced 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. Ability to maintain a unified backlog:
  • Maintain all your backlog in one location and associate backlog stories to a product or a project or both as desired.
  • Ability to select stories from backlog and execute them as a project.
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. Allows backlog stories to be categorized by themes, and epics.
Team versus Assignment Group Uses Release Team. Uses Assignment Group. Uses Assignment Group to create an assignment group of type Agile Team. It eliminates the confusion between when to use release team versus assignment group.

It also allows you to convert an existing release team 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. Generate sprints for Assignment Groups. It allows different groups to use different sprint schedules or all the groups can follow the same schedule.
Sprint Planning Uses Planning Board Uses Sprint Planning Board One Sprint Planning Board for groups to plan their sprint work.
Task Progress board and Story progress board Uses Task Progress board and Story progress board Use of VTB (Visual Task Board) is recommended. Uses Task Progress and Story Progress boards as base system. Customers can create custom VTBs as required.

Upgrade and new customers

Existing Agile Development customers can upgrade to Agile Development 2.0. They should evaluate upgrade information before applying the new plugin.

All new customers, or the customers who have never activated the Agile Development must activate the Agile Development 2.0 plugin.