A project roadmap is the high-level plan that sequences tasks, timing, dependencies, and delivery phases. Build it after confirming the client context, data stores, team structure, and availability, then share it with the team and stakeholders. section 4.7
Organize the roadmap around three adjustable delivery phases:
- Sprint 1: acquire data, build infrastructure, and begin UX work where early designs clarify nonfunctional model requirements. section 4.7
- Sprint 2: build, evaluate, and select models. section 4.7
- Sprint 3: integrate the system and prepare it for production. section 4.7
- Move components forward or delay them when delivery circumstances change, but agree on the revised course with client stakeholders. section 4.7
Treat the roadmap as a governance and communication artifact, not only a scheduling document. Pair it with approved documentation deliverables that clarify what will be delivered, to whom, and when. section 4.3.5
