SBP-Regulated Delivery — Raast R2P & Kisaan Card
Delivered central-bank-mandated financial products against hard regulatory deadlines — Raast Request-to-Pay and the Kisaan Card — at a ~90% on-time release rate across 75-day sprint cycles.
- On-time release rate
- ~90%
- Sprint cycles (~800 mandays)
- 75-day
- Missed regulatory deadlines
- 0
Context
The State Bank of Pakistan (SBP) mandates certain financial products with hard regulatory deadlines — missing them is not an option. JazzCash was tasked with delivering Raast Request-to-Pay (R2P) and the Kisaan Card, central-bank-mandated programmes that combine payment-network integration, compliance, and tight delivery windows. I ran these as regulated programmes across 75-day sprint cycles, leading cross-functional squads of 9–15.
Problem
Central-bank-mandated financial products come with hard regulatory deadlines that cannot slip. The challenge was delivering Raast R2P and the Kisaan Card on time while meeting compliance, payment-network, and integration requirements.
Approach
Ran regulated programmes across 75-day sprint cycles (~800 mandays each), leading cross-functional squads of 9–15. Each sprint was structured around clear milestones, with compliance and engineering workstreams sequenced so the regulatory deadline stayed the fixed point everything else moved around.
Impact
Delivered with zero missed regulatory deadlines at a ~90% on-time release rate. Both Raast R2P and the Kisaan Card shipped on schedule, meeting SBP requirements.
Insight
When the deadline is regulatory, the delivery plan inverts: every other dependency, scope decision, and risk has to move around the fixed regulatory date, not the other way around.
Learning
Regulated delivery taught me to treat the regulatory deadline as an immovable constraint and design the entire programme backwards from it — sequencing compliance and engineering so neither becomes the long pole at the end.
Key takeaways
- Regulatory deadlines are immovable — plan backwards from them.
- Sequence compliance early so it can't block the cutover.
- Fixed-date delivery needs its own cadence, not a standard sprint.
More case studies