Input
Every change starts somewhere.
An incident report, a product idea, a dependency update, or an automated system can all become Input.
Input can come from any source in your delivery system.
Framework
The framework is built on four concepts: Input, Development, Validation, and Ship.
Read the model first, then use the concept sections for definition and detail.
Ship It! assumes
- Software changes continuously.
- Not every change carries the same risk.
- Different changes may require different delivery processes.
- Teams do not necessarily need a new methodology.
These assumptions are the conceptual foundation of the framework. For the rationale behind them, see the Manifesto.
Read the graph from left to right: Input flows through Development and Validation to Ship. If Validation fails, it creates new Input and work returns for further Development.
The four concepts
Development
Development transforms an input into a change.
That work may involve people, AI systems, automation or entire teams.
How Development happens depends on the change and the team.
Validation
Validation provides confidence that the change solves the intended problem and can survive in production.
Validation may involve tests, reviews, monitoring, experimentation or human judgment.
If Validation fails, it creates new Input and the workflow continues.
Ship
Shipping is the moment a change becomes available.
Deployment and release are sometimes the same step, and sometimes separate.
Ship It! focuses on the outcome rather than the mechanism.