Slicing work vertically
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
split a feature into independently deliverable slices.
Planned topics
- A vertical slice cuts through all layers (API, logic, database) and delivers a small piece of user value.
- A horizontal slice (all tables first) delivers nothing usable until the end.
- Slice by workflow step, rule, data variation, or happy path before edge cases.
- Each slice can be merged, tested, and released behind a feature flag.
- Aim for slices of one to three days.
Draft outline details
Demonstration
returns slices: request a return, approve it, refund full amount, partial refund, notify customer.
Check your understanding
Why is "create all return tables" a bad slice?
Show answer
It is horizontal and delivers no user value by itself.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.