Agile Project Management for Regulators Training Course

Duration 10 days 16 modules · 65 contact hours
Level Intermediate Certificate on completion
Who attends Regulatory programme managers, PMO managers and others
Fee from USD 2,200 KSh 190,000 for Kenyan organisations
Where 52 cities + online See dates by city
Next start 16 Nov 2026 Course code SD-AP-035

Before you join: Participants should have experience contributing to, managing or assuring projects, programmes, policy implementation, supervisory change or digital transformation.

Dates & prices

Two start dates a month in every city, and live online on weekdays or weekends. Fees are per participant; classroom fees include tuition, materials, lunch and refreshments, and the certificate.

Suggest a date or city

Showing the next six months. Later dates, other cities and private deliveries for your team are available on request.

Course overview

Regulatory bodies must deliver policy, supervisory, licensing, enforcement and technology change under public scrutiny, statutory deadlines and shifting priorities. Conventional project controls can struggle when evidence emerges late, consultation changes requirements, or urgent market events demand rapid reprioritisation. Agile project management offers useful ways to manage uncertainty, but regulators must apply it without weakening due process, auditability, independence, security or legal accountability.

This course equips participants to select and apply Agile approaches for regulatory work. Participants use Scrum, Kanban, AgilePM and hybrid governance techniques to define outcomes, organise backlogs, plan increments, manage dependencies and report progress to senior decision-makers. They learn to translate legislation, policy intent, supervisory commitments and stakeholder needs into testable requirements; establish proportionate controls; and maintain decision records suitable for assurance and audit.

Teaching combines short instructor briefings with regulator-focused cases, group planning work, simulations and structured peer review. Cases include supervisory technology implementation, licensing-process redesign, policy consultation delivery and response programmes following market disruption. Participants progressively build a regulatory Agile delivery pack, including a delivery charter, prioritised backlog, release plan, governance model, risk controls and performance measures. The final capstone requires them to present and defend the completed pack to a simulated regulatory steering group.

The course suits professionals who manage, sponsor, assure or govern change within regulators, central banks, public authorities and regulated financial institutions. It is particularly useful where teams need faster delivery while retaining clear accountability, documented decisions and credible oversight.

What you will be able to do

  • Assess Agile suitability using delivery uncertainty, regulatory risk and governance criteria
  • Define regulatory product outcomes, user needs and measurable acceptance criteria
  • Build and prioritise a regulatory backlog using MoSCoW and value-risk analysis
  • Plan iterative delivery using release roadmaps, sprint goals and dependency mapping
  • Establish Agile governance controls for assurance, audit trails and decision rights
  • Apply Kanban metrics to manage workflow, bottlenecks and service demand
  • Conduct Agile risk management using RAID logs, risk appetite and escalation thresholds
  • Present a complete Agile regulatory delivery pack to senior stakeholders

Benefits of attending

For you

  • Apply Agile methods without compromising regulatory accountability or audit evidence
  • Explain iterative delivery choices confidently to legal, risk and senior stakeholders
  • Produce clearer backlogs, release plans and decision records for regulatory initiatives
  • Identify when hybrid rather than pure Scrum delivery is appropriate
  • Build a practical delivery pack for immediate use on a live initiative

For your organisation

  • Shorter feedback cycles for policy, supervisory and service-improvement initiatives
  • Stronger traceability from regulatory intent to delivered outcomes and evidence
  • Earlier visibility of delivery risks, dependencies and blocked decisions
  • More consistent Agile governance across programmes, PMOs and delivery teams
  • Better stakeholder confidence through transparent prioritisation and progress reporting

Course modules

16 modules over 10 days

Participants can distinguish appropriate Agile, predictive and hybrid approaches for regulatory change.

  • Agile values interpreted alongside statutory duties, due process and accountability
  • Predictive, Agile and hybrid delivery models compared against regulatory uncertainty
  • Cynefin framework used to classify complicated and complex delivery conditions
  • Regulatory change typology covering policy, supervision, licensing and technology initiatives
  • Constraints from legislation, consultation, procurement, security and public transparency
  • Selecting delivery approaches through risk, uncertainty, urgency and control criteria

Participants can frame regulatory initiatives around measurable outcomes and user needs.

  • Outcome statements linked to statutory objectives, public value and supervisory priorities
  • Theory of Change maps connecting interventions, assumptions and intended results
  • Service users identified across regulated firms, consumers and internal specialists
  • Problem statements separated from preferred solutions and premature implementation choices
  • OKRs drafted for policy delivery, supervisory improvement and digital services
  • Benefits hypotheses tested through evidence, feedback and operational performance measures

Participants can convert regulatory needs into testable backlog items and acceptance criteria.

  • User stories written from regulator, firm, consumer and analyst perspectives
  • INVEST criteria applied to backlog items with legal and operational constraints
  • Acceptance criteria structured using Given-When-Then scenarios and evidence requirements
  • Non-functional requirements covering security, accessibility, retention and auditability
  • Traceability matrix linking legal obligations, requirements, controls and test evidence
  • Definition of Done adapted for approvals, records management and assurance

Participants can create a prioritised backlog that makes regulatory trade-offs explicit.

  • Product backlog structure separating outcomes, epics, features and user stories
  • MoSCoW prioritisation applied to mandatory obligations and discretionary improvements
  • Cost of Delay assesses urgency, risk exposure and public-interest consequences
  • WSJF calculations adjusted for regulatory deadlines and dependency constraints
  • Backlog refinement identifies ambiguity, dependencies, assumptions and decision owners
  • Prioritisation records capture rationale, dissenting views and approval authority

Participants can define delivery roles and decision rights for multi-disciplinary regulatory teams.

  • Product Owner accountabilities adapted for policy, supervision and service delivery
  • Scrum Master responsibilities distinguished from programme management and assurance roles
  • RACI matrix assigns decisions, approvals, consultation and escalation responsibilities
  • Three Lines Model clarifies management, risk oversight and independent assurance
  • Cross-functional teams combine legal, policy, data, technology and operational expertise
  • Delegated authority thresholds prevent delivery delay while preserving formal accountability

Participants can plan increments and releases around regulatory commitments and decision gates.

  • Release roadmap sequences minimum viable policy, service or technology outcomes
  • Sprint goals connect short-term work with approved regulatory outcomes
  • Planning poker estimates effort where expert judgement remains uncertain
  • Dependency mapping exposes legal, procurement, data and external-party constraints
  • Critical path analysis used selectively for fixed statutory milestones
  • Increment reviews scheduled around consultation, approval and implementation decision points

Participants can run Scrum events that produce decisions, evidence and delivery focus.

  • Sprint Planning converts prioritised backlog items into achievable delivery commitments
  • Daily Scrum focuses on progress, blockers, dependencies and immediate decisions
  • Sprint Review gathers evidence from sponsors, specialists and representative users
  • Retrospectives identify process improvements, control failures and recurring delays
  • Timeboxes protect delivery focus while allowing required formal approvals
  • Event records preserve decisions, actions, unresolved issues and accountable owners

Participants can design Kanban systems for variable regulatory demand and operational work.

  • Kanban boards visualise intake, analysis, decisions, review and closure stages
  • Work-in-progress limits reduce overload and expose stalled regulatory cases
  • Service classes distinguish urgent incidents, statutory work and improvement requests
  • Cumulative flow diagrams reveal queues, bottlenecks and unstable workflow patterns
  • Lead time and cycle time support service-level expectation management
  • Replenishment meetings select work using capacity, risk and priority criteria

Participants can embed proportionate risk and assurance controls within iterative delivery.

  • ISO 31000 principles applied to Agile delivery risks and opportunities
  • RAID logs integrate risks, assumptions, issues and interdependencies
  • Risk appetite statements set tolerances for delay, quality and compliance exposure
  • Control design identifies preventive, detective and corrective delivery controls
  • Assurance plans define evidence sources, review timing and reporting recipients
  • Escalation thresholds trigger sponsor intervention before regulatory commitments fail

Participants can establish Agile governance that supports scrutiny without excessive delay.

  • Governance cadence aligns delivery reviews with committees and statutory decision gates
  • Decision logs record options, evidence, authority, rationale and follow-up actions
  • Stage gates retained for irreversible commitments, funding and legal approval
  • Information radiators tailored for executives, delivery teams and assurance functions
  • Audit trails connect backlog changes, approvals, testing evidence and released outputs
  • Exception reporting distinguishes tolerable variation from material delivery concerns

Participants can plan iterative engagement while protecting regulatory independence and fairness.

  • Stakeholder mapping assesses influence, interest, impact and consultation obligations
  • Consultation plans define questions, evidence standards, channels and response governance
  • Feedback loops distinguish stakeholder input from formal regulatory commitments
  • Conflict-of-interest controls protect independence during industry engagement activities
  • Facilitation techniques surface disagreement, assumptions and unresolved policy trade-offs
  • Response matrices document consultation themes, decisions and reasons for rejection

Participants can coordinate suppliers and partners within an Agile regulatory delivery model.

  • Supplier backlogs align contracted outputs with evolving regulatory delivery priorities
  • Statement of Work clauses address increments, acceptance and change control
  • Interface control documents manage data, systems and operational handoffs
  • Dependency boards track external commitments, dates, owners and contingency actions
  • Commercial governance separates supplier performance discussions from product prioritisation
  • Acceptance testing confirms deliverables against documented regulatory and technical criteria

Participants can report Agile delivery performance without relying on misleading activity measures.

  • Outcome measures distinguish delivered activity from realised regulatory benefit
  • Burndown charts interpreted alongside scope change, quality and dependency information
  • Velocity used for team forecasting, not cross-team performance comparison
  • Throughput trends support capacity planning for casework and change portfolios
  • Confidence ratings communicate forecast uncertainty to senior decision-makers
  • Executive dashboards combine milestones, risks, decisions, outcomes and assurance status

Participants can coordinate multiple initiatives while retaining local team autonomy and oversight.

  • Portfolio Kanban manages demand, funding decisions and strategic delivery capacity
  • Quarterly planning aligns initiatives with statutory commitments and supervisory priorities
  • Cross-team dependency reviews resolve sequencing conflicts and shared-resource constraints
  • Common definitions standardise status, risks, benefits and assurance evidence
  • Communities of practice improve delivery consistency without imposing unnecessary process
  • Portfolio retrospectives identify systemic blockers, policy conflicts and governance delays

Participants can introduce Agile ways of working through controlled, evidence-led change.

  • Change impact assessment identifies affected roles, controls, systems and behaviours
  • ADKAR model structures adoption planning for new delivery practices
  • Pilot selection balances manageable scope, visible value and learning potential
  • Training needs analysis identifies role-specific knowledge, skills and reinforcement requirements
  • Improvement backlogs capture lessons from retrospectives, assurance reviews and incidents
  • Maturity assessments guide proportionate improvement rather than framework compliance

Participants can build, review and present a complete Agile delivery pack for a regulatory initiative.

  • Delivery charter defines mandate, outcomes, scope, constraints and accountable sponsor
  • Prioritised backlog includes user stories, acceptance criteria and traceability references
  • Release roadmap maps increments, dependencies, approvals and regulatory milestones
  • Governance model assigns forums, decision rights, controls and escalation thresholds
  • Risk and assurance plan specifies evidence, reviews, owners and reporting cadence
  • Steering-group presentation defends priorities, forecasts, trade-offs and implementation recommendations

Exercises and examples are adapted to each cohort's sectors and roles.

What you take back to work

  1. Regulatory Agile delivery charter template
  2. Prioritised regulatory product backlog
  3. Increment and release roadmap
  4. Agile governance and decision-rights matrix
  5. Risk, assurance and audit-trail checklist
  6. Executive delivery dashboard model

Who should attend

  • Regulatory programme managers — need adaptive delivery controls that withstand scrutiny
  • PMO managers — need governance models for iterative regulatory portfolios
  • Policy and supervision managers — need practical methods for delivering changing commitments
  • Digital transformation leads — need to align Agile teams with regulatory decision rights
  • Risk and assurance professionals — need evidence-based oversight of Agile delivery
  • Senior regulatory sponsors — need clearer progress information and intervention points

Skills and tools covered

Regulatory Agile governanceBacklog prioritisationIterative delivery planningKanban flow managementAssurance evidence designStakeholder decision-making

Tools and standards

Scrum Guide, Kanban Method, MoSCoW prioritisation, ISO 31000

How the course runs

Training methodology

The course uses short briefings to establish methods, followed by regulator-focused case work, facilitated group exercises, planning simulations and individual application planning. Participants work with realistic artefacts such as policy requirements, supervisory commitments, audit findings, risk registers and executive reporting packs. Instructor feedback focuses on proportional governance, evidence quality and decision clarity. Each module adds to a delivery pack, allowing participants to test methods against a current or recent initiative and receive structured peer challenge.

Requirements and prerequisites

Participants should have experience contributing to, managing or assuring projects, programmes, policy implementation, supervisory change or digital transformation. They should understand basic project concepts such as scope, milestones, stakeholders, risks and reporting. Familiarity with a regulatory, public-sector, central-bank or regulated-industry setting is helpful. No prior Agile certification, software development experience, coding knowledge or formal PMO qualification is required. Participants should bring a current or recent change initiative that they can use as a reference during planning discussions.

A typical training day

08:30 – 10:30First session
10:30 – 10:45Refreshment break
10:45 – 12:30Second session
12:30 – 13:30Lunch and networking
13:30 – 15:00Third session
15:00 – 15:15Refreshment break
15:15 – 16:30Workshop and daily review

Live online deliveries follow the same structure in East Africa Time, with shorter screen blocks and longer breaks.

What the fee includes

  • Instruction by a practitioner facilitator
  • Full course workbook and materials
  • Exercise files, templates and case studies
  • Refreshments and lunch on classroom deliveries
  • Certificate of completion
  • Post-course application plan

Frequently asked questions

You should understand basic project work, including stakeholders, risks, milestones and reporting. Previous Agile training or certification is not required, and the course does not assume software development experience.

Bring details of a current or recent regulatory, policy, supervisory, operational or technology change initiative. You will use it as a reference when developing your delivery pack, but confidential information can be anonymised.

It suits project and programme managers, PMO professionals, policy managers, supervision leaders, risk specialists and senior sponsors. It is designed for people working within regulators, central banks, public authorities or regulated firms.

General Agile courses commonly focus on product or software teams. This course addresses statutory duties, formal approvals, consultation, assurance, audit trails, regulatory independence and governance arrangements.

Participants develop a delivery charter, backlog, release roadmap, governance model and risk controls that can be adapted for a live initiative. The methods also apply to policy delivery, licensing, supervisory change, casework and digital services.

Each day runs from 08:30 to 16:30 and provides about 6.5 contact hours. The first week establishes delivery design, planning and team methods; the second week focuses on governance, assurance, scaling, reporting and the final capstone presentation.

Questions about this course?

Ask about dates, fees, group bookings or running it for your team. Our training team replies by email.