Estimate and Plan a 6-Week MVP for a Local Logistics Startup
Overview
What this challenge is about.
Read the product brief and decompose it into 8-12 modules (driver app, dispatcher console, shipper portal, billing, etc.). Estimate each module using 3-point estimation (optimistic, most-likely, pessimistic) and a planning-poker session with two peer engineers. Produce a 6-week Gantt-style schedule covering 2 engineers working full-time. Author a risk register (top 8 risks with likelihood, impact, mitigation, owner). For each module, recommend build vs buy (e.g. buy auth via Clerk, buy maps via Mapbox, build dispatcher console). Deliver an estimate spreadsheet, the 6-week schedule, the risk register, the build-vs-buy memo, and a 25-minute readout deck.
The Brief
What you'll do, and what you'll demonstrate.
Estimate, schedule, and de-risk a 6-week MVP build for a 3-founder startup with one shot at runway.
Earning criteria — what you'll demonstrate
- Apply 3-point estimation to real software modules
- Sequence a 6-week schedule with realistic buffer
- Author a risk register that drives action, not just documentation
- Recommend build-vs-buy with cost + lock-in trade-offs
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Product Manager
Product managers who can co-author a build-vs-buy memo with engineering avoid the year-one cost spirals that kill seed-stage startups.
This challenge sharpens
- build-vs-buy
- mvp-scoping
- stakeholder-communication