Project Management for Central Banks Training Course

Participants can prepare a structured business case for a central-bank project proposal.

• Problem statements linked to statutory functions and operational performance gaps
• SMART objectives expressed as measurable project and service outcomes
• Options appraisal using do-nothing, minimum-change and preferred-option comparisons
• Cost categories covering internal effort, suppliers, technology and transition
• Benefits mapping for policy, resilience, efficiency and stakeholder outcomes
• Assumptions, constraints and dependencies documented within the business case

Participants can create a project charter with clear scope boundaries and authority.

• Project charter components under PMBOK and ISO 21502 guidance
• Scope statements separating included deliverables from explicit exclusions
• Acceptance criteria specified for systems, processes, services and controls
• Requirements traceability from sponsor needs through approved deliverables
• Defining tolerances for scope, time, cost, risk and quality
• Authority limits assigned to sponsors, project managers and steering committees

Participants can design governance structures that support timely and accountable project decisions.

• PRINCE2 governance principles applied to central-bank project oversight
• Sponsor responsibilities for direction, resources, decisions and benefit ownership
• RACI matrices clarifying accountability across policy, operations and technology
• Stage gates with evidence requirements, approvals and decision records
• Escalation routes for tolerance breaches, conflicts and unresolved dependencies
• Terms of reference for steering committees and working groups

Participants can decompose a project into manageable deliverables, work packages and control accounts.

• Work breakdown structures organised around approved project deliverables
• Decomposition techniques separating products, work packages and supporting activities
• Product breakdown structures for technology, process and policy outputs
• Work-package owners assigned through accountable delivery commitments
• Control accounts connecting scope, responsibility, budget and performance reporting
• Deliverable dictionaries defining purpose, owner, acceptance and dependencies

Participants can build an integrated schedule that identifies sequencing constraints and critical work.

• Precedence diagrams showing finish-to-start, start-to-start and finish-to-finish relationships
• Estimating durations using analogous, parametric and three-point techniques
• Critical path method identifying activities with zero scheduling float
• Milestone plans aligned with governance gates and operational release dates
• Dependency mapping across legal, procurement, technology and business-readiness workstreams
• Schedule compression choices using fast tracking and crashing analysis

Participants can estimate resource demand and construct a defensible project cost baseline.

• Resource breakdown structures covering staff, specialists, facilities and suppliers
• Capacity planning against business-as-usual duties and peak operational periods
• Bottom-up estimates built from work packages and resource rates
• Cost baselines separating capital expenditure, operating expenditure and contingency
• Contingency reserves calculated from identified risk exposure and assumptions
• Funding profiles aligned with annual budgeting and procurement approval cycles

Participants can identify, assess and respond to project risks affecting central-bank objectives and services.

• ISO 31000 principles applied to project risk governance
• Risk identification using prompt lists, workshops and assumption analysis
• Probability-impact matrices calibrated for service, financial and reputational consequences
• Risk owners, response actions, triggers and residual-risk assessments
• Threat responses using avoid, reduce, transfer, accept and contingency strategies
• Risk appetite statements informing escalation thresholds and approval requirements

Participants can operate practical registers that keep emerging delivery constraints visible and owned.

• Issue logs distinguishing current problems from uncertain future risks
• Assumption registers recording validation dates, owners and consequences
• Dependency registers identifying external commitments and required delivery dates
• Decision logs preserving rationale, authority and resulting actions
• Escalating overdue actions through agreed governance and tolerance rules
• Weekly control reviews linking issues, risks, assumptions and dependencies

Participants can plan stakeholder engagement for projects involving internal and external central-bank interests.

• Stakeholder mapping by power, interest, influence and impact
• Identifying affected functions, market participants, authorities and service providers
• Engagement strategies matched to stakeholder support and resistance levels
• Communication plans defining messages, channels, timing and accountable owners
• Consultation records capturing concerns, commitments and required follow-up actions
• Managing sensitive communications involving market-moving or confidential information

Participants can plan supplier engagement and maintain project control through procurement and delivery stages.

• Procurement strategies matching market capability, risk and delivery urgency
• Statement-of-work specifications defining deliverables, service levels and acceptance criteria
• Evaluation criteria balancing technical quality, price, risk and capability
• Supplier governance through milestones, reporting obligations and review meetings
• Contract change controls protecting scope, cost, schedule and accountability
• Managing vendor dependencies during system integration and operational transition

Participants can establish quality controls and assurance activities for project outputs and decisions.

• Quality management plans defining standards, reviews and acceptance responsibilities
• Quality criteria translated into measurable deliverable acceptance tests
• Independent assurance roles separated from day-to-day project delivery
• Internal control requirements incorporated into process and system designs
• Audit trails maintained for approvals, changes, testing and acceptance evidence
• Lessons learned captured through structured reviews and closure reports

Participants can evaluate and control changes without losing approved project baselines.

• Baseline management for scope, schedule, cost and approved requirements
• Change requests documenting rationale, urgency, impact and requested decisions
• Impact assessments covering benefits, controls, resources, risks and dependencies
• Change authority matrices defining approval thresholds and decision owners
• Configuration management for controlled documents, specifications and system versions
• Maintaining traceability between requirements, changes, tests and accepted deliverables

Participants can report project performance clearly and forecast corrective action requirements.

• Project dashboards presenting milestones, risks, issues, decisions and budget status
• Traffic-light criteria defined through objective thresholds and supporting evidence
• Earned value management using planned value, earned value and actual cost
• Forecasting estimate at completion from current cost and schedule performance
• Exception reports focused on tolerance breaches, consequences and required decisions
• Executive reports tailored for boards, committees, sponsors and senior management

Participants can prepare implementation plans that protect service continuity and operational control.

• Operational readiness assessments covering people, processes, technology and facilities
• Cutover plans sequencing migration, testing, approvals and contingency actions
• Business continuity requirements integrated into implementation and transition planning
• Training needs analysis for users, operators, administrators and support teams
• Service acceptance criteria agreed before production release decisions
• Hypercare arrangements defining incident handling, support capacity and exit criteria

Participants can incorporate technology, cyber-security and data controls into project planning.

• Technology architecture dependencies identified before solution design commitments
• Cyber-security requirements incorporated into scope, testing and supplier obligations
• Data governance covering ownership, classification, retention and access controls
• Privacy impact assessments planned for personal or sensitive information
• System integration risks assessed across interfaces, data flows and operational handoffs
• Resilience testing requirements defined for critical payment and market infrastructure

Participants can close projects formally and track whether intended benefits are achieved after handover.

• Benefits realisation plans linking outcomes, measures, owners and review dates
• Baseline measures established before change implementation and operational handover
• Post-implementation reviews testing benefits, controls, adoption and service performance
• Closure criteria covering accepted deliverables, contracts, records and outstanding actions
• Knowledge transfer plans assigning ownership for support and future improvements
• Lessons-learned reviews converting delivery experience into reusable institutional guidance

Participants can lead project teams through competing priorities, disagreement and delivery pressure.

• Team charters establishing roles, behaviours, meeting cadence and working agreements
• Facilitation techniques for cross-functional planning and problem-solving meetings
• Conflict resolution using interests, options, criteria and agreed commitments
• Decision-making methods including consultation, consent, delegation and sponsor escalation
• Managing policy, operational and technology perspectives within integrated teams
• Personal action plans addressing project leadership strengths and development needs

Participants can position projects within wider portfolios, programmes and strategic change priorities.

• Portfolio prioritisation criteria linking projects to mandate, risk and strategic objectives
• Programme roadmaps coordinating tranches, interdependencies and shared capability development
• Resource conflicts resolved through prioritisation, sequencing and sponsor decisions
• Portfolio reporting aggregating risk exposure, milestones, costs and expected benefits
• Strategic alignment tests applied before approving new project commitments
• Managing inter-project dependencies across payments, supervision and technology portfolios

Participants can build, review and present a complete central-bank project dossier for sponsor approval.

• Project charter articulating mandate, objectives, scope, exclusions and success criteria
• Integrated plan combining work breakdown, schedule, resources and cost baseline
• Governance model defining sponsor roles, stage gates and escalation routes
• Risk, issue and dependency registers with owned response actions
• Stakeholder engagement plan addressing internal, market and public-sector interests
• Sponsor presentation defending assumptions, priorities, controls and benefit measures