FAQ
What is Ship It!?
Ship It! is a minimal software delivery framework.
It describes the minimum workflow required to move a software change from Input to Ship.
Who is Ship It! for?
Ship It! is for developers and teams who feel software delivery has become more complicated than necessary.
It is especially useful when the delivery process feels heavier than the change itself.
Is Ship It! a software development methodology?
No.
It defines a minimal delivery workflow.
Planning, estimation, ceremonies, team structure, and roles remain your team's choice.
Can Ship It! be used with Scrum or Kanban?
Yes.
Ship It! works with your existing way of working.
What is Input?
Input is the reason why a change exists.
It can come from developers, users, monitoring, business requirements or automation.
What is Development?
Development is the activity that creates or modifies the change.
It can be done by individuals, teams or automated systems.
What is Validation?
Validation provides confidence that the change solves the intended problem and can survive in production.
Validation may involve people, automation or both.
What is Ship?
Ship makes the validated change available.
How that happens depends on the team, the product and the change itself.
What happens when Validation fails?
Validation does not end the workflow.
Failed validation creates new Input.
The framework defines that work continues.
Is Ship It! an AI framework?
No.
Ship It! is technology-agnostic.
AI can participate in Development or Validation, but it does not redefine the framework.
Does Ship It! require any specific tools or technologies?
No.
Use whatever works for your team.
Why doesn't Ship It! prescribe how teams should work day to day?
Ship It! intentionally avoids prescribing day-to-day working practices. It does not define meetings, ceremonies, planning cadences, or team routines. Those are local decisions that depend on the team, organization, and context. Ship It! provides a shared language for reasoning about software delivery while allowing teams to keep the practices that already work well for them.
Why is the framework so small?
Because every new concept increases complexity.
It intentionally defines only the minimum workflow required to deliver validated software.
Will the framework grow over time?
Only when new ideas make the framework simpler, clearer or easier to apply.
Where does Ship It! come from?
It emerged from practical software delivery experience.
It was created by observing how software is actually delivered.
I want to contact you.
Mail to: captain <at> shipitframe.work.
If your question is about applying these ideas in real delivery situations, continue in Examples.