Risk Register and Budget for a Regulated Mobile Banking Launch
Overview
What this challenge is about.
Read the launch brief (28 pages) and the regulatory inventory (12 obligations). Build a top-25 risk register categorized (technical, security, regulatory, vendor, operational) with likelihood × impact scoring, mitigation, residual risk, and named owner. Build the budget in a workbook: engineering (12 FTEs × 24 weeks), vendor (KYC vendor, fraud-screening vendor, app-store), security audit + penetration test, contingency (25 percent). Sequence the 24-week schedule around 6 hard regulatory milestones with cut-over criteria per milestone. Author a 1-page joint memo between the CTO and Head of Compliance covering the top 5 risks and the 3 risks that block launch. Deliver risk register, budget workbook, schedule, and joint memo.
The Brief
What you'll do, and what you'll demonstrate.
Build a risk register, budget, and regulatory-milestone schedule for a 24-week mobile banking launch that cannot afford another slip.
Earning criteria — what you'll demonstrate
- Build a risk register categorized across technical / regulatory / vendor dimensions
- Sequence a project schedule around hard regulatory milestones
- Budget for security audit + penetration test as first-class line items
- Communicate risks to a joint engineering + compliance audience
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 read a top-25 risk register fluently make better trade-off calls with the CTO + Compliance during launch.
This challenge sharpens
- risk-management
- vendor-management
- stakeholder-communication