05 · Territory · Deliver and release
Shipping
How do we shorten the time from decision to real feedback?
Map20 skills
5 capabilitiesClick a tile to open a skill
- 05.1Iterative deliveryDelivering in small steps that each reach users, so feedback arrives early and plans can change cheaply.
- 05.2Release engineeringThe pipelines and practices that take a change from merge to production reliably and repeatably.
- 05.3Controlled releasesSeparating deploying code from releasing features, so changes reach users gradually and can be switched off.
- 05.4Release readinessMaking sure a release is ready for users, support and operations before it goes out.
- 05.5Delivery managementKeeping work moving: estimating it, spotting risks early and clearing what blocks it.
About Shipping
05Shipping is getting working software into users' hands, often and safely. Every week a change sits unreleased is a week without feedback. This territory covers delivering in small pieces, automating releases, exposing changes gradually, preparing a launch and keeping work moving. Teams that ship small and often learn faster and break less.
What a product engineer should be able to do here
Deliver useful software frequently and safely, avoiding large releases that postpone learning.