Discovery as the architect's first deliverable
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
treat discovery as a planned deliverable, not a warm-up.
Planned topics
- Discovery output: requirements baseline, constraints, assumptions, stakeholder decisions, open questions.
- Skipped or rushed discovery shows up later as rework and scope fights.
- The architect asks different questions from a product owner: quality, integration, data, failure.
- Done means signed off by owners, not merely written.
Draft outline details
Demonstration
a Larkspur discovery plan outline: objectives, participants, sessions, outputs, sign-off date.
Check your understanding
What marks discovery as done?
Show answer
A baseline accepted by the owners, with open items owned and dated.
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.