Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Agile Development

Log in to subscribe to topics and get notified when content changes.

Agile Development

The ServiceNow® Agile Development application helps you deliver software projects more efficiently by managing and tracking software development life-cycles using 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 life-cycle work-flows together into one system. Agile Development manages scrum or waterfall development, and helps you manage the backlog of tasks throughout the lifecycle, from inception through testing and deployment. Ultimately, you gain increased visibility into the entire software development lifecycle.

Following are the variants of Agile Development:
Agile under Project Management
See the documentation at Agile integration with Project Portfolio Suite for project-based agile development.
Agile Development 1.0
See the documentation at Agile Development 1.0 for more information.
Agile Development 2.0
Agile Development 2.0 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. Watch this two-minute video for an introduction.
Capabilities are continually refined so that you can harness the power of agile to enhance your software development efforts. To match your service level with the Agile Development application that best meets your needs, consult the following information and table carefully.
If you have Agile Development 1.0 and you upgrade to Agile Development 2.0, Agile Development 2.0 will replace Agile Development 1.0. If you are installing Agile Development for the first time and you are on Kingston or a later release, you should install Agile Development 2.0.
Table 1. Agile Development variants — Notable differences
Feature Agile

(Project Management)

Agile Development 1.0

(PPS and existing customers)

Agile Development 2.0
Backlog A story can be associated to only a project. A story can be associated to a product. A personalized backlog can be created by defining filter criteria.
Release A project story cannot be associated to a release. A story can 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 cannot be associated to a theme, or epic. A story can be associated to a theme, or epic. Backlog stories can be categorized by themes and epics.
Team versus Assignment Group Assignment Group is used. Release Team 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 assignment group based. Each group can have its sprint schedule. Sprints are release-based. Each team cannot have a different 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 Sprint Planning Board is used. The Planning Board is used. The Agile Board Sprint Planning tab is used.
Task Progress board and Story progress board VTB (Visual Task Board) is used. The Task Progress board and Story progress board are used. The Agile Board Sprint Tracking tab is used.