Release & Release Gating Frequency

Release Frequency

Deployment Frequency will be determined based on project-specific attributes. Though Agile methods are designed to enable deployment of a potentially shippable product at the end of each Sprint, that is only possible when the right mix of team experience, technical capabilities, quality assurance, and business participation are all in alignment. To determine their release rhythm, projects should consider the following:

The Business’ capacity and availability to Accept and authorize releases

The Team’s Experience

Seniority of Team Members (resource levels, experience with delivery)
Level of Experience with the technologies involved
Agile Experience & Certifications

The project’s technical capabilities to deploy Rapidly (this can also be budget-driven)

Test Automation
Continuous Integration
Scalable/Rapid Infrastructure

NOTE: It is common for Agile teams to fall somewhere within a 3-5 Sprint Release rhythm (6-10 weeks assuming 2-week Sprints)

Illustration: Release Frequency Determination

PMO Sprint Release Gate Frequency

The frequency with which an Agile team will have to return for PMO Sprint Release Gate Approval prior to deployments will also be based on project-specific attributes. The project will work with the PMO to establish an appropriate rhythm based on the team’s experience, technical capabilities to deliver rapidly while ensuring quality, and the complexity and risk of the project as a whole. In evaluating this frequency, the project team and the PMO should consider:

The Project’s Complexity & Risk

Are there New Technologies?
Are there New Interfaces to Critical Systems?
Are there Consumer/Brand Impacts?
Are there Company Financial Impacts?

The Project Team’s Experience, Technical Capability, and Quality Assurance

Agile Experience
Deployment Experience for Launch Legends

Test Automation
Continuous Integration
Scalable/Rapid Infrastructure

Release & Release Gating Frequency