Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • IT Business Management
Table of Contents
Choose your release version
    Home New York IT Business Management IT Business Management Agile Development Agile Development 2.0 Agile Development process flow Agile development use cases

    Agile development use cases

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Agile development use cases

    Different organizations follow different methods to deliver backlog/stories.

    Some of the typical delivery methods are:
    • Release based delivery
    • Project based delivery

    Agile Development 2.0 provides the ability to maintain a unified backlog for both types of delivery. You can maintain all your backlog in one place and associate backlog stories to a product or a project or both as desired. You can also select stories from backlog and execute them as a project.

    In addition, it also supports the execution of standalone project development.

    The following example shows how Agile Development 2.0 supports a unified backlog for both types of deliveries.
    Figure 1. Agile development workflow use cases
    Concept picture for different agile development use cases

    Release based development use case

    An example of release based agile development and delivery model is explained.

    The usual activities involved in a release based agile development include the following:

    • Maintain Product Backlog – Product owners maintain the product backlog. They continuously groom their backlogs by adding stories, prioritizing and estimating them.
    • Release Planning – Organizations have definite release cycles such as quarterly release, bi-yearly release, yearly release. The product owners select the prioritized stories from the product backlog that should be completed in a given release to form Release Backlog.
    • Sprint Planning – The scrum teams define their sprint schedule such as two weeks sprint or three weeks sprint. They work with product owner, and select stories from the release backlog that should be completed in each sprint to create Sprint Backlog.
    The following illustration provides a high-level overview of the workflow in a release based agile development environment.
    Figure 2. Release based agile development workflow example
    Concept picture for release based agile development workflow

    How to use Agile Development 2.0 for release based agile development

    Steps to perform release based development:
    1. Manage product backlog: Product owner maintains and grooms product backlog. Navigate to Agile Development > Backlog > All Stories.
    2. Release planning: Navigate to Agile Development > Planning > Release planning, and click Assign to release/group to assign stories from product backlog to release backlog.

      Simultaneously, specify a group name to assign stories to the specified group.

    3. Backlog planning: From release backlog, assign stories to groups that are planned to work in the release.
    4. Sprint planning: The group members along with product owner and scrum master decide stories for each sprint using Sprint Planning. Navigate to Agile Development > Agile Board > Sprint Planning.

    Project based development use case

    An example of project based agile development and delivery model is explained.

    The usual activities involved in a project based agile development include the following:

    • Maintain Product Backlog – Product owners maintain the product backlog. They continuously groom their backlogs by adding stories, prioritizing and estimating them.
    • Project Backlog – Product owners select the prioritized stories and assign them to one or more projects, which creates the Project Backlog. All product owners can create one or more projects and capture additional details such as required resources, cost, risk, strategic alignment. All these projects undergo portfolio prioritization process, and the selected projects are executed by the project teams.
      Note: Some organizations also define release cycles such as quarterly release, bi-yearly release, yearly release. They then move the stories from product backlog to the release backlog. In these cases, stories are assigned to the projects from the release backlog. For example, for SAP product, enhancements are delivered every quarter (quarterly release) and then projects are created to execute the release backlog.
    • Sprint Planning – The project scrum teams define their sprint schedule such as two weeks sprint or three weeks sprint. They work with their project manager, and select stories from the project backlog that should be completed in each sprint to create Sprint Backlog.
    The following illustration provides a high-level overview of the workflow in a project based agile development environment.
    Figure 3. Project based agile development workflow example
    Concept picture for project based agile development workflow

    How to use Agile Development 2.0 for project based agile development

    Steps to perform project based development:
    1. Manage product backlog: Product owner maintains and grooms product backlog. Navigate to Agile Development > Backlog > All Stories.
    2. Release planning [Optional step]: Navigate to Agile Development > Planning > Release planning, and click Assign to release/group to assign stories from product backlog to release backlog.
      Note: This step is required if the organization has a definite release cycle. In this case, after the release planning, one or more projects are created to execute the release backlog.
    3. Manage project backlog: Navigate to Agile Development > Backlog > All Stories, or Release Backlog. Then click Assign to project to create a project or assign stories to an existing project from product/release backlog.

      Users can also open an existing project and associate stories to the project from the backlog. These stories are then executed as part of project execution.

    4. Group assignment: The project manager can create one or more agile phases in the project, move stories under these agile phases, and assign groups to these phases. The assigned groups take care of executing these stories through sprints.
    5. Sprint planning: The agile group members along with project manager, and scrum master perform sprint planning. Navigate to Agile Development > Planning > Sprint planning to open sprint planning board.

    Standalone project development use case

    An example of a standalone project development and delivery model is explained.

    In this case, request (demand) for a new product or feature or system is raised. Demand managers capture the requirements in terms of stories. They also capture the other details for the demand such as resources required, cost, risks, and strategic direction. Such demands upon approval are converted into projects. Project managers can choose pure agile or hybrid mode of project execution. In hybrid mode, the initial phases such as planning, and analysis are taken up as waterfall tasks, and then the execution is done as agile phase. The agile phase is assigned to an agile group. The agile group then completes the work by sprint execution.

    The following illustration provides a high-level overview of the workflow for executing a standalone project development.
    Figure 4. Project based agile development workflow example
    Concept picture for Standalone development workflow

    How to use Agile Development 2.0 for standalone hybrid project development

    Steps to execute a standalone hybrid project:
    1. Create demand: Capture requirements at demand state in terms of user stories. Use Stories related list on demand form to create stories.
    2. Demand to Project conversion: When the demand is converted to a project, the stories in demand move to the project so that the project team (assignment group) can execute them. During the conversion, an Agile phase is also created, and the stories are assigned to the agile phase.
    3. Sprint planning: The agile group members along with project manager, and scrum master perform sprint planning. Navigate to Agile Development > Planning > Sprint planning to plan sprints.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Agile development use cases

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Agile development use cases

      Different organizations follow different methods to deliver backlog/stories.

      Some of the typical delivery methods are:
      • Release based delivery
      • Project based delivery

      Agile Development 2.0 provides the ability to maintain a unified backlog for both types of delivery. You can maintain all your backlog in one place and associate backlog stories to a product or a project or both as desired. You can also select stories from backlog and execute them as a project.

      In addition, it also supports the execution of standalone project development.

      The following example shows how Agile Development 2.0 supports a unified backlog for both types of deliveries.
      Figure 1. Agile development workflow use cases
      Concept picture for different agile development use cases

      Release based development use case

      An example of release based agile development and delivery model is explained.

      The usual activities involved in a release based agile development include the following:

      • Maintain Product Backlog – Product owners maintain the product backlog. They continuously groom their backlogs by adding stories, prioritizing and estimating them.
      • Release Planning – Organizations have definite release cycles such as quarterly release, bi-yearly release, yearly release. The product owners select the prioritized stories from the product backlog that should be completed in a given release to form Release Backlog.
      • Sprint Planning – The scrum teams define their sprint schedule such as two weeks sprint or three weeks sprint. They work with product owner, and select stories from the release backlog that should be completed in each sprint to create Sprint Backlog.
      The following illustration provides a high-level overview of the workflow in a release based agile development environment.
      Figure 2. Release based agile development workflow example
      Concept picture for release based agile development workflow

      How to use Agile Development 2.0 for release based agile development

      Steps to perform release based development:
      1. Manage product backlog: Product owner maintains and grooms product backlog. Navigate to Agile Development > Backlog > All Stories.
      2. Release planning: Navigate to Agile Development > Planning > Release planning, and click Assign to release/group to assign stories from product backlog to release backlog.

        Simultaneously, specify a group name to assign stories to the specified group.

      3. Backlog planning: From release backlog, assign stories to groups that are planned to work in the release.
      4. Sprint planning: The group members along with product owner and scrum master decide stories for each sprint using Sprint Planning. Navigate to Agile Development > Agile Board > Sprint Planning.

      Project based development use case

      An example of project based agile development and delivery model is explained.

      The usual activities involved in a project based agile development include the following:

      • Maintain Product Backlog – Product owners maintain the product backlog. They continuously groom their backlogs by adding stories, prioritizing and estimating them.
      • Project Backlog – Product owners select the prioritized stories and assign them to one or more projects, which creates the Project Backlog. All product owners can create one or more projects and capture additional details such as required resources, cost, risk, strategic alignment. All these projects undergo portfolio prioritization process, and the selected projects are executed by the project teams.
        Note: Some organizations also define release cycles such as quarterly release, bi-yearly release, yearly release. They then move the stories from product backlog to the release backlog. In these cases, stories are assigned to the projects from the release backlog. For example, for SAP product, enhancements are delivered every quarter (quarterly release) and then projects are created to execute the release backlog.
      • Sprint Planning – The project scrum teams define their sprint schedule such as two weeks sprint or three weeks sprint. They work with their project manager, and select stories from the project backlog that should be completed in each sprint to create Sprint Backlog.
      The following illustration provides a high-level overview of the workflow in a project based agile development environment.
      Figure 3. Project based agile development workflow example
      Concept picture for project based agile development workflow

      How to use Agile Development 2.0 for project based agile development

      Steps to perform project based development:
      1. Manage product backlog: Product owner maintains and grooms product backlog. Navigate to Agile Development > Backlog > All Stories.
      2. Release planning [Optional step]: Navigate to Agile Development > Planning > Release planning, and click Assign to release/group to assign stories from product backlog to release backlog.
        Note: This step is required if the organization has a definite release cycle. In this case, after the release planning, one or more projects are created to execute the release backlog.
      3. Manage project backlog: Navigate to Agile Development > Backlog > All Stories, or Release Backlog. Then click Assign to project to create a project or assign stories to an existing project from product/release backlog.

        Users can also open an existing project and associate stories to the project from the backlog. These stories are then executed as part of project execution.

      4. Group assignment: The project manager can create one or more agile phases in the project, move stories under these agile phases, and assign groups to these phases. The assigned groups take care of executing these stories through sprints.
      5. Sprint planning: The agile group members along with project manager, and scrum master perform sprint planning. Navigate to Agile Development > Planning > Sprint planning to open sprint planning board.

      Standalone project development use case

      An example of a standalone project development and delivery model is explained.

      In this case, request (demand) for a new product or feature or system is raised. Demand managers capture the requirements in terms of stories. They also capture the other details for the demand such as resources required, cost, risks, and strategic direction. Such demands upon approval are converted into projects. Project managers can choose pure agile or hybrid mode of project execution. In hybrid mode, the initial phases such as planning, and analysis are taken up as waterfall tasks, and then the execution is done as agile phase. The agile phase is assigned to an agile group. The agile group then completes the work by sprint execution.

      The following illustration provides a high-level overview of the workflow for executing a standalone project development.
      Figure 4. Project based agile development workflow example
      Concept picture for Standalone development workflow

      How to use Agile Development 2.0 for standalone hybrid project development

      Steps to execute a standalone hybrid project:
      1. Create demand: Capture requirements at demand state in terms of user stories. Use Stories related list on demand form to create stories.
      2. Demand to Project conversion: When the demand is converted to a project, the stories in demand move to the project so that the project team (assignment group) can execute them. During the conversion, an Agile phase is also created, and the stories are assigned to the agile phase.
      3. Sprint planning: The agile group members along with project manager, and scrum master perform sprint planning. Navigate to Agile Development > Planning > Sprint planning to plan sprints.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login