The challenge.
Stand up a next-generation digital lending platform capable of loan approval and disbursement within 5 minutes, launch within 6 months, and onboard millions of users from day one — against strict banking regulation, non-standard patterns for Pega-plus-cloud DevOps, and the need to scale a 200+ person delivery team faster than the talent market typically allows.
The constraints.
- Regulatory: Strict banking regulations governing AWS environments. Non-standard Pega + cloud DevOps patterns required engineering invention against an audit floor.
- Scale: 50+ regulated AWS environments to manage in parallel. Complex integration across Pega, risk engine, microservices and channels.
- Talent: Stand up 200+ FTE across multiple skill domains rapidly. Skill availability within the timeline posed major delivery risk.
- Communication: Primary stakeholders communicated in their native language; language and cultural barriers were a delivery risk, not an inconvenience.
- Timeline: 6 months. No slack for serial discovery-design-build-test.
The architectural approach.
POD-based leadership, squad-based delivery.
Three POD types ran in parallel:
- Delivery Lead PODs — owning execution, timelines, dependencies.
- Architecture PODs — owning Pega, risk engine, microservices, integration patterns.
- PMO PODs — owning planning, reporting, risk and governance.
Squads aligned to platform components, functional modules and business capabilities — not to org-chart silos.
Local engagement model.
Local client-facing PMOs paired with internal delivery PMOs across regions. The structure absorbed language and cultural diversity instead of fighting it.
Skill-based, not role-based, resource planning.
Skill requirements identified bottom-up; talent head-hunted across JAPAC based on capability fit, not role titles. Task-level timelines defined by individual capability — the most predictable delivery shape at this scale.
Engineering foundation.
Automation-first testing approach. Containerisation as standard practice. Mandatory code and pipeline reviews. The 50+ regulated AWS environments were managed to support parallel development, testing and release without the usual collision tax.
- Workflow & decisioning Pega
- Backend Go-lang microservices
- Risk processing FIS Risk Engine
- Frontend Microservice-based (mobile + web)
- Cloud platform AWS (50+ environments)
- DevOps Containerisation + CI/CD
Outcomes.
disbursement
on commitment
& squads
environments
go-live
Predictable delivery velocity despite the team scale. Parallel delivery across multiple squads without blocking dependencies. Stable operations across the 50+ regulated AWS environments. Strong stakeholder trust established through local PMO engagement and clear communication across language barriers.
Large-scale digital transformation succeeds not by adding more people, but by adding the right structure, clarity, and automation.
Five lessons from the programme.
- Speed and regulation are compatible. Regulated environments can move fast with appropriate architecture, automation and governance.
- Structure enables scale. POD- and squad-based models prevent chaos when delivery teams exceed 150–200 people.
- DevOps is the foundation, not the optimisation. Automation, containerisation and CI/CD were essential for managing 50+ environments without slowing delivery.
- Local engagement multiplies trust. Language and cultural alignment via local PMO structures significantly improved decision-making and stakeholder trust.
- Skill-based beats role-based at scale. Task timelines aligned to individual capability delivered far more predictable outcomes than traditional role-based assignment.