Skip to content

[Anchor Proposal]: Thin Vertical Slice #422

Description

@cpoepke

Proposed Term

Thin Vertical Slice

Context (Optional)

A delivery technique where one small, complete feature is implemented end-to-end across all system layers (UI → logic → persistence) in a single increment. Keeps each increment releasable and avoids integration surprises. Primary use is in the inception phase (proving first-feature delivery is achievable), but applies throughout agile delivery.

Category: System Inception Patterns (see #414)
(Note: also applicable as an ongoing agile delivery technique beyond inception)

Why it qualifies:

  • Precise: well-established in agile and DDD communities with clear scope (end-to-end, feature-oriented, thin)
  • Rich: activates concepts around continuous integration, feature-driven delivery, cross-layer coordination, incremental development
  • Consistent: clearly distinguished from horizontal slicing and from architectural styles
  • Attributable: Jimmy Bogard (Vertical Slice Architecture blog, 2018); broader agile lineage

Key distinction — Thin Vertical Slice vs Vertical Slice Architecture:

  • Thin Vertical Slice: a delivery technique (how you increment work)
  • Vertical Slice Architecture (Bogard): a structural code organization style
    These are complementary but not the same concept.

Distinguishes from:

  • Walking Skeleton — feature-delivery focused vs system-viability validation
  • MVP — single increment unit vs product-level hypothesis test
  • Spike Solution — shippable feature vs technical decision experiment

References:

Pre-submission Checklist

  • I have searched existing anchors and this term is not already included
  • This term refers to a well-established concept (not something I invented)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions