Phasing a solution
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
break a solution into phases using value, risk, and dependency.
Planned topics
- Slice vertically, by capability a user can use (web ordering for one range), not horizontally by layer (database first, UI last).
- Order slices by value and by risk: put the scariest unknown (ERP integration) early with a thin version.
- Keep phases a size the organization can absorb: change fatigue in stores is real.
- Each phase has a scope statement, an out-of-scope list, and an owner.
Draft outline details
Demonstration
a table of candidate phases for Larkspur: web ordering with ERP stock, click and collect, store returns, loyalty, analytics; columns value, risk, depends on.
Check your understanding
Why slice vertically?
Show answer
A vertical slice gives users a working capability each phase; layers deliver nothing usable until all are done.
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.