Hamburger method
It was proposed by Gojko Adzic in January 2012 for teams that can only think in terms of technical layers. The layers involved (the bun and the ingredients) are listed, together with each layer's options from lowest to highest quality. A minimum level is then chosen for each layer, so that the "first bite" goes through the whole hamburger. It is a way of using layered thinking to arrive at a vertical slice.
Description
The goal is to ensure that all aspects of a large story are taken into account when breaking it down, making estimation, prioritization, and incremental implementation easier.
The hamburger is made up of three layers:
- Top bun: the goal or user value that the story must deliver. The "what for" of the large story.
- Filling ingredients: the different dimensions or layers of functionality that can be developed incrementally. Each "layer" can become an independent story.
- Bottom bun: the acceptance criteria and the Definition of Done that apply to all the derived stories.
How to apply it
- Identify the epic or large story that needs to be split.
- Define the top bun: what user goal or value must this epic deliver?
- Identify the ingredients: along which dimensions can the story be split? Possible splitting axes: by user type, by workflow, by data type, by interface, by business rule, and by level of complexity.
- Build the stories for each layer: each ingredient becomes a story that delivers value on its own.
- Check the bottom bun: make sure that each derived story has clear acceptance criteria and meets the Definition of Done.
Relationship with SPIDR
The hamburger method is complementary to the SPIDR story-splitting strategy. While SPIDR identifies which axis to split along (Spike, Path, Interface, Data, Rules), the hamburger provides the visual structure to ensure that the split produces complete and coherent stories.
Common mistake
Splitting horizontally instead of vertically. A split that creates stories such as "the technical part of feature X" or "the database part of Y" cuts along technical layers: none of the pieces can be delivered or assessed on its own. The correct split is vertical, that is, a slice that cuts through all the necessary layers and delivers an observable change in behavior, however small.
Resources
🏦 Skill User storiesState of the art and development guide · Skill Arena
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.