Release strategies
Jump to navigation
Jump to search
See http://pareltaal.nl/gouden_driehoek for basic mechanism.
Three primary release strategies:
- Custom-Planned Releases—scope is function of time
- release date estimated from initial feature set and velocity;
- snapshot delivery of whatever is ready by the date;
- scope changes require trade-offs if date remains fixed, consider money for nothing, change for free;
- Fixed Release Cadence—scope is function of time
- delivery on a fixed cadence, e.g. monthly or quarterly;
- snapshot delivery whatever is ready by the date;
- feature set frozen on latest responsible moment (driven by feature set risk profile)
- Multi-Team Releases—time is function of scope;
- epic feature sets split over multiple squads;
- dependencies tagged visually;
- regular joint reviews, e.g. scrum of scrums;
- delivery when a feature set’s components are ready for release.