Risk first: spikes and prototypes
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
reduce the biggest unknowns early.
Planned topics
- List the riskiest assumptions: unknown API, performance, data quality, unclear rule.
- A spike is a time-boxed investigation (for example one day) that ends with an answer, not production code.
- A prototype tests an idea cheaply; throw it away.
- Order work so risky slices come first.
- Write down the result; update the plan and estimates.
Draft outline details
Demonstration
a risk table: assumption, impact, likelihood, spike to test it.
Check your understanding
What does a spike produce?
Show answer
Knowledge: an answer that reduces uncertainty.
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.