Ship It!

The minimal software delivery framework.

Build.Validate.Ship.

Not every software change needs every step your process describes.

Most software delivery frameworks add concepts. Ship It! removes them.

The result is the minimum workflow every software change still follows.

Ship It! is a minimal software delivery framework.

Ship It! describes the minimum workflow required to move a software change from Input to Ship, using four concepts: Input, Development, Validation, and Ship.

InputDevelopmentValidationShip
Input, Development, Validation and Ship are four equally important Ship It! concepts.

An example

Situation

A small, low-risk update needs to be delivered quickly.

Question

Does this still need the same delivery model as a larger change?

Ship It!

  • Input: A small change request.
  • Development: Implement the update.
  • Validation: Verify that the update works as intended.
  • Ship: Release the change as soon as confidence is sufficient.

Takeaway

Ship It! describes the same four concepts regardless of the size or urgency of the change.

Most software delivery frameworks add concepts.

Ship It! removes them.

It describes the smallest workflow that still explains every software change.

Foundation

Software changes are becoming smaller, more frequent and increasingly AI-assisted.

Teams can produce changes faster than many delivery processes were designed to handle.

Most software delivery frameworks describe everything. Ship It! asks what remains after everything unnecessary has been removed.

The result is a minimal workflow that still describes every software change.

Ship It! is an exercise in reduction.

Continue reading