Agile PMO for Banking Transformation Projects Training Course

Course overview

Banking transformation programmes must deliver digital channels, core-platform change, regulatory remediation, data modernisation and operating-model improvements without weakening control, auditability or customer service. Traditional PMO reporting often cannot show whether agile teams are meeting regulatory commitments, managing cross-platform dependencies or consuming funding against measurable outcomes. This course addresses the practical gap between agile delivery teams and the governance, risk, finance and executive functions that must make confident portfolio decisions.

Participants learn how to establish an Agile PMO that supports Scrum, Kanban and scaled delivery while retaining banking-grade controls. The course covers portfolio intake and prioritisation, outcome-based roadmaps, quarterly planning, dependency mapping, regulatory traceability, RAID management, capacity and funding views, and executive dashboards. Participants practise translating team-level delivery data into portfolio measures such as value delivered, regulatory milestone confidence, flow efficiency, release readiness and risk exposure.

Teaching combines instructor-led models with a realistic banking transformation case involving mobile banking, KYC remediation and core-system integration. Teams configure a practical governance cadence, build portfolio artefacts, analyse delivery metrics and prepare an executive decision pack. Each participant leaves with a tailored Agile PMO implementation blueprint containing a governance model, reporting design, prioritisation approach, control map and 90-day adoption plan that can be adapted for their own bank or financial-services programme.

Course objectives

By the end of this course, participants will be able to:

• Design an Agile PMO operating model with defined decision rights, governance forums and escalation routes for banking portfolios
• Create an outcome-based portfolio roadmap that connects strategic themes, regulatory commitments, releases and measurable benefits
• Apply WSJF and weighted scoring models to prioritise banking change initiatives against risk, value, urgency and capacity
• Build a dependency map linking agile teams, core banking platforms, third parties, data services and release milestones
• Establish regulatory traceability from policy or supervisory commitments through epics, features, controls and evidence
• Configure a portfolio dashboard using flow, predictability, capacity, risk and benefits measures for executive reporting
• Facilitate quarterly planning and portfolio review cadences that align agile delivery commitments with funding and control gates
• Produce a 90-day Agile PMO implementation blueprint for a banking transformation programme

Benefits of attending

Target competencies

Who should attend

• PMO Managers — who need to redesign governance and reporting for agile banking delivery
• Transformation Programme Managers — who coordinate large-scale digital, regulatory or core-platform change
• Portfolio Managers — who prioritise investment across competing banking initiatives and constrained delivery capacity
• Delivery Leads and Release Train Engineers — who must surface dependencies and delivery confidence to senior governance forums
• Risk, Compliance and Regulatory Change Managers — who need traceable evidence through iterative delivery
• Business Change Managers — who connect product releases, operational readiness and benefits realisation

Requirements and prerequisites

Participants should understand the basic purpose of projects, programmes, milestones, risks and stakeholder reporting, and should have worked on, supported or governed a change initiative. Familiarity with Scrum terms such as backlog, sprint, product owner and retrospective is helpful, as is awareness of banking controls such as audit evidence, regulatory commitments or change approval. No prior Agile PMO role, certification, Jira administration skill, software configuration experience or advanced financial modelling is required. Complete beginners can attend, but should expect a foundation-level introduction to agile delivery before applying the governance methods.

Training methodology

The course uses short instructor-led briefings followed by applied work on a banking transformation case. Participants work in teams to prioritise a mixed portfolio of digital, regulatory and core-platform initiatives; create a dependency board; define control evidence; and interpret dashboard data from simulated delivery teams. Demonstrations show how Jira Software, Microsoft Project and Power BI can support the artefacts without turning the course into tool administration training. The final session is an implementation clinic in which participants refine their own 90-day Agile PMO adoption plan with instructor feedback.

Course outline

Day 1: Agile PMO foundations for banking transformation

• Agile PMO roles, services and operating-model choices
• Banking transformation portfolio types and delivery constraints
• Scrum, Kanban and scaled agile governance touchpoints
• Three-lines-of-defence implications for portfolio governance
• Decision rights using RAPID and responsibility matrices
• Outcome, output, benefit and regulatory commitment distinctions
• PMO maturity assessment for agile banking environments

Workshop: Teams assess a simulated bank PMO and produce a target-state service catalogue with priority capability gaps.

Day 2: Portfolio strategy, prioritisation and planning

• Strategic themes and portfolio investment guardrails
• Outcome-based roadmaps and rolling-wave planning
• Weighted Shortest Job First prioritisation
• Weighted scoring for regulatory and risk-reduction initiatives
• Capacity allocation across run, change and mandatory work
• Quarterly planning cadence and commitment management
• Funding views for product-centric and project-centric portfolios

Workshop: Participants prioritise a digital banking, KYC remediation and core-modernisation portfolio and produce a quarterly investment roadmap.

Day 3: Dependencies, controls and delivery assurance

• Cross-team dependency mapping and critical-path analysis
• Integration dependencies across core banking, APIs and vendors
• RAID logs adapted for agile delivery
• Regulatory traceability from obligation to delivery evidence
• Definition of Ready and Definition of Done control criteria
• Release readiness and operational acceptance gates
• Impediment escalation through portfolio governance forums

Workshop: Teams build a dependency and control-evidence map for a mobile banking release dependent on KYC and core-platform services.

Day 4: Metrics, reporting and executive decisions

• Portfolio flow metrics including throughput, cycle time and work in progress
• Predictability measures for planned versus completed work
• Benefits realisation tracking and outcome hypotheses
• Regulatory milestone confidence and evidence-completeness measures
• Risk exposure heat maps and exception reporting
• Jira Software portfolio data and data-quality controls
• Power BI executive dashboard design principles

Workshop: Participants convert simulated team delivery data into an executive portfolio dashboard and present three required decisions.

Day 5: Implementing and sustaining the Agile PMO

• Agile PMO governance calendar and meeting architecture
• Stakeholder engagement with technology, risk, finance and operations
• Change impact assessment for PMO process redesign
• Training, coaching and adoption measures for delivery teams
• Pilot selection and phased implementation planning
• Control testing, audit preparation and continuous improvement
• Ninety-day Agile PMO implementation roadmap

Workshop: Each participant completes and peer-reviews a 90-day Agile PMO implementation blueprint for a selected banking transformation context.

Tools & standards covered

Jira Software, Microsoft Project, Microsoft Power BI, SAFe 6.0

A typical training day

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

What the fee includes

How you can take this course

Certification

Participants who complete the full five days receive the Skillset Development Certificate of Completion, stating the course title, course code, dates and delivery format — suitable for professional-development records and employer reimbursement.

Frequently asked questions