Vertical slicing
Vertical slicing is the practice of breaking work into thin slices that cut through every layer of the architecture — UI, business logic, data, infrastructure — so each slice delivers end-user value independently. The opposite, horizontal slicing, splits by layer ('do all the UI first, then the API'), which delivers no value until every horizontal layer is complete.
Vertical slicing is the operational principle behind several agile concepts: INVEST stories should each be a vertical slice; user-story mapping releases work by picking one vertical slice across the journey; a walking-skeleton release is the thinnest possible vertical slice. The discipline pays off when projects slip: with horizontal slicing, halfway through means nothing ships; with vertical slicing, halfway through means half the slices are live and the customer is using them. The hardest part is the first slice — it forces all the layers to exist, which feels like extra work upfront but compounds for every subsequent slice.
Related terms
- Story splitting
Story splitting is the practice of breaking a large user story into smaller stories that each independently deliver value.
- INVEST criteria
INVEST is a mnemonic — coined by Bill Wake in 2003 — for the qualities of a good user story: Independent (can be worked on without depending on other stories), Negotiable (not a rigid contract, room to discuss the implementation), Valuable (delivers value to the user or business), Estimable (the team can size it), Small (fits in a single sprint), Testable (acceptance criteria can be verified).
- User-story mapping
User-story mapping, formalised by Jeff Patton in his 2014 book of the same name, is a workshop technique for organising product backlogs around the user's journey rather than as a flat list.