STAGE 02 / CHAPTERS 5-8
Agree on the result
Turn observed needs into a bounded release, explicit rules, and checkable outcomes.
THE WORK TO DO
- 01
Study actual customer and staff tasks, including exceptions. Resolve differences between studio rules.
- 02
Choose one useful release boundary. Keep deferred requests with reasons for waiting.
- 03
Describe success, failure, timing boundaries, and repeated actions. Estimate the selected work with assumptions and dependencies.
WHAT YOU LEAVE WITH
A release map, agreed rules, acceptance criteria, and an engineering estimate.
BEFORE MOVING FORWARD
The chosen path reaches a useful outcome. Decisions still missing are visible beside the work they block.
A cancellation is eligible exactly at its saved policy cutoff. An unconfirmed hold expires exactly at its deadline. Each rule needs its own check.
WHO DOES WHAT / STAGE 02
Turn the need into decisions the team can use.
Client
Approves priorities and operating rules.
Analyst
Writes scope, states, exceptions, and acceptance criteria.
Tech Lead
Checks feasibility and dependencies.
Designer
Makes the main task and unclear states visible.
Tester
Turns each promise into a checkable example.
THE HANDOFF
Approved rules + acceptance criteria → design and test planning
The Client settles product decisions. The Analyst passes approved rules and open questions to design, implementation, and testing.
Work with: Project Manager, Senior Administrator, Backend Developer, Security Engineer.
Additional expertise when the work needs it: Product Owner, Systems Analyst, Business Analyst.
See the team across all eight stages →