Everything starts with Input.
Features.
Bugs.
Security issues.
Customer requests.
Technical debt.
Anything requiring work becomes Input.
Ship It!
The minimal software delivery framework.
Build.Validate.Ship.
The Framework
Every piece of work starts as Input.
Development creates a solution.
Validation has only two possible outcomes.
The solution is ready for production.
Or validation creates new Input.
That's it.
- Input
- Development
- Validation
- Production
One Rule
Every change must be independently validated before it is shipped.
Validation may be performed by another developer, an automated process, or any combination that fits your team.
Manifesto
Software delivery should be simple.
- Every change begins with Input.
- Every Input becomes Development.
- Every Development deserves Validation.
- Validated work can be shipped.
- If validation fails, the work becomes new Input.
- Keep building.
- Keep validating.
- Keep shipping.
Principles
Development creates value.
How you build software is your choice.
Use Scrum.
Use Kanban.
Use AI.
Use pair programming.
Use whatever works.
Validation builds trust.
Independent validation is the heart of the framework.
If validation succeeds, ship it.
If not, create new Input.
Keep the framework minimal.
Ship It! intentionally defines as little as possible.
Teams should own their own implementation.
Works With
- Scrum?Yeah.
- Kanban?Yeah.
- GitHub?Yeah.
- GitLab?Yeah.
- Azure DevOps?Yeah.
- Jira?Yeah.
- Linear?Yeah.
- AI?Absolutely.
- Whiteboards?Sure.
- Sticky notes?Why not?
FAQ
Does Ship It! replace Scrum?
No.
It works perfectly alongside Scrum.
Does Ship It! require Kanban?
No.
Use whatever helps your team.
Can AI perform Development?
Yes.
Can AI perform Validation?
Yes.
Can one person validate their own work?
Sometimes.
Independent validation is recommended whenever possible.
Is this a process?
Yes.
A very small one.