---
title: Project-based development use case in Agile Development
description: An example of project-based development and delivery model in Agile Development.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-business-management/agile-development/project-based-agile-development-use-case.html
release: australia
product: Agile Development
classification: agile-development
topic_type: concept
last_updated: "2026-10-09"
reading_time_minutes: 2
breadcrumb: [Agile Development use cases, Exploring Agile Development 2.0, Agile Development 2.0, Agile Development, Strategic Portfolio Management]
---

# Project-based development use case in Agile Development

An example of project-based development and delivery model in Agile Development.

The usual activities involved in a project-based Agile Development include the following:

-   Product Backlog: Product owners maintain the product backlog. They continuously groom their backlogs by adding stories, prioritizing and estimating them.

    In Agile Development 2.0, navigate to **Agile Development** > **Backlog** > **All Stories** for the list of all the stories.

-   Project Backlog: Product owners select the prioritized stories and assign them to one or more projects, thus creating the project backlog. 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.

    In Agile Development 2.0, navigate to **Agile Development** > **Stories** and select **Assign to project** to assign stories to a new or existing project.

    You 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.

-   Assignment of stories: Assign the stories of the project to an assignment group so that the team can pick these up in the upcoming sprints.

    In Agile Development 2.0, select the stories that you want to assign to a release, select **Assign to release/group** and specify an assignment group.

-   Sprint planning: The scrum teams define their sprint schedule such as two-week sprint or three-week sprint. They work with the product owner, and select stories from the release backlog that should be completed in each sprint to create Sprint Backlog. The group members along with product owner and scrum master decide stories for each sprint using Sprint Planning.

    In Agile Development 2.0, navigate to **Agile Development** > **Agile Board** > **Sprint Planning**.


**Parent Topic:**[Agile Development use cases](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-business-management/agile-development/agile-workflow-use-cases.md)