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 1. 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 > Agile Board > Sprint Planning to open sprint planning.