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 1. Release based agile development workflow example How to use Agile Development 2.0 for release based agile development Steps to perform release based development: Manage product backlog: Product owner maintains and grooms product backlog. Navigate to Agile Development > Backlog > All Stories. 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. Backlog planning: From release backlog, assign stories to groups that are planned to work in the release. 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.