STAGE 04 / CHAPTERS 13-16
Build working components
Build in small slices. Keep the requirement, changed files, and actual check results together.
THE WORK TO DO
- 01
Break the release into complete, testable outcomes. Make dependencies and missing access visible.
- 02
Implement, review, and connect the interface, server, database, and provider integrations.
- 03
Demonstrate against the agreed criteria. Record the checked version and the impact of new requests.
WHAT YOU LEAVE WITH
Repeatable working slices, reviewed changes, actual check results, and visible unfinished work.
BEFORE MOVING FORWARD
The demonstrated outcome meets the shared quality conditions on an identified build.
A repeated payment result must not create an extra confirmation action. The corrected version is checked again, with the result retained.
WHO DOES WHAT / STAGE 04
Build a complete path through the product.
Frontend Developer
Builds browser behavior and shows actual server outcomes.
Backend Developer
Implements rules, permissions, and durable work.
Tech Lead
Reviews how the pieces fit together.
Tester
Checks each integrated change and reports reproducible failures.
DevOps Engineer
Maintains repeatable builds and test environments.
THE HANDOFF
Integrated change → observed result → correction and repeat
Developers integrate one usable path. The Tester checks the named build, then sends any difference back with conditions and records.
Work with: Designer, Analyst, Project Manager, Security Engineer.
Additional expertise when the work needs it: UI Engineer, Full-Stack Developer, Mobile Developer, Test Automation Engineer, Systems Analyst.
See the team across all eight stages →