hamburger-method

To break down large features into deliverable vertical slices, identify 3-6 architectural layers, generate 4-5 implementation options per layer, and select one option per layer to compose a minimal, fast-to-ship end-to-end slice.

The hamburger method for agile planning and story slicing is a technique that decomposes ambiguous features by listing 3-6 layers, generating manual to enterprise-grade options per layer, and filtering them into safe, incremental vertical slices that deliver value early.

To scope a complex feature for fast delivery and risk management, force radical slicing by generating 4-5 options per layer and asking what minimal end-to-end vertical slice could be shipped by tomorrow to reduce delivery risk.

Yes, you can use vertical slicing for poorly scoped features by identifying 3-6 layers across the complete flow, producing 4-5 options per layer from simple to advanced, and composing a fast, testable slice that aligns product and engineering teams.

A limitation of vertical slice planning is that it requires defining 3-6 distinct layers and generating multiple options per layer, which may not suit features lacking clear architectural layers or features that cannot be decomposed into manual and enterprise-grade options.

To plan follow-up iterations after delivering the first vertical slice, review the remaining 4-5 options across your 3-6 layers, select the next end-to-end slice, and progressively plan improvements to expand coverage and reliability.