Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Agile Development

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 an agile software development environment for product-based or project-based efforts, using the scrum agile framework. Offers the flexibility to implement a pure agile approach over the entire life-cycle of a product, or a hybrid approach using agile methods within a traditional project structure. In Kingston, Agile Development 2.0 includes a new user interface called Agile Board. Watch this two-minute video for an introduction.

The following 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 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.