Exercise 5 · Delivery planning: how your product is built, released and run
| Time | 16 minutes, after the Module 5 slides |
|---|---|
| Blueprint sections | 10 Development, testing and deployment approach |
| You need | Your Virtual CTO conversation; your priorities, architecture and risk register |
| You leave with | A delivery approach sized to your team and a production-readiness checklist |
| Safety tip | Real customer data stays in production. Plan testing with invented data only |
Where you are
You know what you're building and what could go wrong. Now you decide how changes get from an idea to customers safely: version control, review, automated tests, environments, CI/CD, monitoring and what happens when something breaks.
What you will make
A delivery approach: how code is written, reviewed, tested and released, sized for your real team. And a production-readiness checklist: ten to fifteen things that must be true before real customers rely on your product.
For TutorDesk: code in Git with reviewed pull requests; automated tests on every change, including permissions and double bookings; development, staging and production environments; deploy from the main branch several times a week; error alerts to the founder's phone; a written rollback step that takes under ten minutes.
© 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