Release-based development use case in Agile Development
An example of release-based development and delivery model using Agile Development.
The usual activities involved in a release-based agile development are:
- Maintain 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 for the list of all the stories. You can filter the list for a specific product.
- 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.
- Assignment of stories: In Agile Development 2.0, navigate to . Select the stories that you want to assign to a release and select Assign to release/group. Specify a team that you want to associate these stories with.
- 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 .