Description
Frequent Releases is a looser and more relaxed version of Continuous Deployment. Their primary purpose is to put new or updated products into the hands of the end-user community quickly to gather feedback and respond rapidly to change requests. A release plan is used to define the frequency and timing of releases, and they can occur after each sprint or on a calendar schedule. Monthly releases that include the product increments of two two-week sprints are common among large agile organizations.
Typical Roles
Agile Team
Product Owner
Desired Behaviors
- 1.
Develop a frequent release plan. Include the agile team(s) and any other roles that are responsible for development and deployment in the creation of the frequent release plan.
- 2.
Define the timing of each release.
- 3.
Groom and define the epic and user story content of the next two to three releases.
- 4.
Keep the frequent release plan up to date.
- 5.
Display the frequent release plan in the agile team’s workspace using visual information management systems.