Exercise 6 · The CTO review board: defend your decision pack
| Time | 23 minutes, at the end of Module 6 |
|---|---|
| Blueprint sections | 12 Implementation roadmap and CTO sign-off checklist, 11 Technical risks and architecture decision records |
| You need | Your Virtual CTO conversation; your Blueprint sections 1, 2, 4, 5, 7, 10 and 11; two other learners |
| You leave with | A phased roadmap, your decision records and the review board's feedback: your final decision pack |
| Safety tip | Present your product in general terms; don't share confidential figures or customer details with the group |
Where you are
You have priorities, an architecture, technology choices, a risk register and a delivery approach. Now you turn them into a roadmap the business can fund, and defend the whole pack to a sceptical review board, the way a CTO would to investors or a board.
What you will make
A phased roadmap: what each phase delivers, which risk it reduces and roughly what it costs. Two or three architecture decision records: decision, reason, alternatives, consequences and the trigger to revisit. And the review board's feedback, with what you will change.
For TutorDesk: phase 1 (months 1–2) accounts, bookings, payments and backups, with a penetration test and data protection review before launch; phase 2 (3–4) calendar sync, reminders and monitoring; phase 3 (5–6) reporting and scale tests. Decision record: modular monolith, not microservices, because a team of three can't run many services; revisit at three or more teams.
© 2026 MVP Studios Ltd. MVPAI™ and the MVP Studios Academy course materials, including the MVP Founders Programme and MVPAI in a Week, are original works of MVP Studios Ltd. All rights reserved. No copying, redistribution or commercial use without written permission. Course terms