Study guide

26.4 The PMBOK Five Process Groups

Certified Government Financial Manager CGFM

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Organization, Authority and Structure of Government — Part I

1.1 Levels, Branches, and Separation of Powers 1.2 Components of Government & Public Authorities 1.3 Subnational Governments: General-Purpose vs. Special-Purpose

2 Chapter 2: Organization, Authority and Structure of Government — Part II

2.1 Legal Authority, Charters, and Sovereign Powers 2.2 Tribal Sovereignty & Intergovernmental Relations 2.3 Categorical Grants vs. Block Grants

3 Chapter 3: The Government Financial Management Cycle & Legal Framework — Part I

3.1 The Seven Phases of the Financial Management Cycle 3.2 The Closed-Loop Feedback Architecture 3.3 The Constitutional Basis: The Power of the Purse

4 Chapter 4: The Government Financial Management Cycle & Legal Framework — Part II

4.1 Types of Legislative Appropriations 4.2 The Hierarchy of Budgetary Spending Controls 4.3 Legal Mechanisms Dedicating Public Revenues

5 Chapter 5: Government Revenues, Grants & Debt Financing — Part I

5.1 Public Tax Policy and Tax Structures 5.2 Wealth and Property Taxes 5.3 Intergovernmental Grants & the Uniform Guidance Lifecycle 5.4 The OMB Uniform Guidance Grant Lifecycle (2 CFR 200)

6 Chapter 6: Government Revenues, Grants & Debt Financing — Part II

6.1 User Charges, Cost Recovery, Leases & Public-Private Partnerships 6.2 Public Debt Issuance, Bond Types & Credit Ratings 6.3 Certificates of Participation (COPs) and Lease-Revenue Bonds

7 Chapter 7: Public Accountability, Transparency & Open Government — Part I

7.1 Legislative Frameworks for Accountability: IG Act & CFO Act 7.2 Government Management Reform Act (GMRA) of 1994 7.3 Assessing Fiscal Sustainability, Solvency & SEA Reporting

8 Chapter 8: Public Accountability, Transparency & Open Government — Part II

8.1 Net Pension Liability (NPL) Recognition 8.2 Open Government, DATA Act of 2014 & Citizen-Centric Reporting 8.3 Digital Open Checkbooks

9 Chapter 9: Public Sector Ethics & Digital Government — Part I

9.1 Public Service Ethics Principles & the AGA Code of Ethics 9.2 The Ethical Spectrum: The Ethical Floor vs. The Ethical Ceiling 9.3 Managing Conflicts of Interest, Due Care, Whistleblowing & Nepotism

10 Chapter 10: Public Sector Ethics & Digital Government — Part II

10.1 Post-Employment "Revolving Door" Prohibitions (18 U.S.C. § 207) 10.2 E-Government Services, Public Portals & NIST Cybersecurity Standards 10.3 Personally Identifiable Information (PII)

11 Chapter 11: Governmental Accounting Principles & Cost Allocation — Part I

11.1 Environmental Differences, Standard Setters & GAAP Hierarchies 11.2 Standard-Setting Bodies and Jurisdictional Framework 11.3 State and Local GAAP Hierarchy: GASB Statement No. 76 11.4 Measurement Focus, Basis of Accounting & Nonexchange Transactions

12 Chapter 12: Governmental Accounting Principles & Cost Allocation — Part II

12.1 The Four GASB Statement No. 33 Nonexchange Categories 12.2 Managerial Cost Accounting, SFFAS 4 & Intergovernmental Fee Establishment 12.3 Cost Allocation under OMB Uniform Guidance (2 CFR 200 Subpart E)

13 Chapter 13: Public Budgeting Concepts & Controls — Part I

13.1 Public Budget Formulation, Structures & Budgeting Approaches 13.2 Fund 13.3 Performance-Based Budgeting (PBB) 13.4 Capital Project Financing, Capital Budgets & Revenue/Expenditure Forecasting

14 Chapter 14: Public Budgeting Concepts & Controls — Part II

14.1 Public-Private Partnerships (P3s) 14.2 Budgetary Control Techniques & General Ledger Accounting Operations 14.3 Stock Statements vs. Flow Statements

15 Chapter 15: State & Local Fund Accounting & Budgetary Accounting — Part I

15.1 The Eleven State & Local Fund Types & Accounting Bases 15.2 Capital Projects Funds (CPF) 15.3 Custodial Funds 15.4 Modified Accrual Accounting: Revenues, Expenditures & Financing Sources

16 Chapter 16: State & Local Fund Accounting & Budgetary Accounting — Part II

16.1 Other Financing Sources (OFS) and Other Financing Uses (OFU) 16.2 Budgetary Integration, Encumbrance Entries & GASB 54 Fund Balance Classifications 16.3 Nonspendable Fund Balance

17 Chapter 17: State & Local Financial Reporting & Statements — Part I

17.1 Defining the State & Local Reporting Entity & Component Units 17.2 Pathway 3: Misleading to Exclude & Affiliated Organizations (GASB 39 & 90) 17.3 Joint Ventures 17.4 The Annual Comprehensive Financial Report (ACFR) Structure & RSI

18 Chapter 18: State & Local Financial Reporting & Statements — Part II

18.1 Required Supplementary Information (RSI Other than MD&A) 18.2 Government-Wide Financial Statements, Interfund Eliminations & Reconciliation 18.3 Internal Balances (Due To / Due From)

19 Chapter 19: Federal Budgetary Accounting & the USSGL — Part I

19.1 Federal Accounting Governance: FASAB, OMB, Treasury & GAO 19.2 Comparative Analysis: The Quadripartite Leadership 19.3 Federal Budgetary Terminology, the Budgetary Equation & Fund Types

20 Chapter 20: Federal Budgetary Accounting & the USSGL — Part II

20.1 General Fund of the United States Government 20.2 The U.S. Standard General Ledger (USSGL) & Dual-Track Budgetary Accounting 20.3 Milestone 2: OMB Apportionment (Form SF 132)

21 Chapter 21: Federal Proprietary Accounting & Financial Reporting — Part I

21.1 Federal Proprietary Accounting & Fund Balance with Treasury (FBWT) 21.2 Non-FBWT Budgetary Authority (Offsets) 21.3 Stewardship PP&E: Heritage Assets and Stewardship Land (SFFAS 29) 21.4 Federal Credit Reform Act (FCRA): Direct Loans, Loan Guarantees & Subsidy Accounting

22 Chapter 22: Federal Proprietary Accounting & Financial Reporting — Part II

22.1 The Liquidating Account (Budgetary - Pre-1992) 22.2 Federal Financial Reporting: AFR, PAR, Basic Financial Statements & the U.S. Consolidated Report 22.3 The Statement of Changes in Net Position (SCNP)

23 Chapter 23: Cash, Investment & Debt Operations — Part I

23.1 Government Cash Management, Collections, Lockboxes & Banking Controls 23.2 Fees vs. Compensating Balances: Strategic Analysis 23.3 Public Investment Policies, Safety-Liquidity-Yield, Prudent Person Rule & Risk Disclosures 23.4 Authorized Public Investment Instruments: Comparative Analysis

24 Chapter 24: Cash, Investment & Debt Operations — Part II

24.1 GASB Statement No. 40: Deposit and Investment Risk Disclosures 24.2 Electronic Payments, EFT, P-Cards & Disbursement Controls 24.3 Public Benefit Disbursements: EBT and Reloadable Debit Cards

25 Chapter 25: Procurement, Asset Stewardship & Operational Systems — Part I

25.1 Public Procurement Standards, Fair Competition & Contract Administration 25.2 Contract Types and Cost Risk Allocation 25.3 Capital Asset Stewardship, Property Disposal, Inventory & OM&S Controls 25.4 Environmental Compliance and Electronic Data Sanitization

26 Chapter 26: Procurement, Asset Stewardship & Operational Systems — Part II

26.1 Financial Management Information Systems (FMIS), ERP, Cloud Hosting & Automation 26.2 Development Methodologies: Waterfall vs. Agile 26.3 Shared Services Delivery & Public Sector Project Management 26.4 The PMBOK Five Process Groups

27 Chapter 27: Financial, Managerial & Forensic Analysis — Part I

27.1 Mathematical and Financial Foundations of Time Value of Money (TVM) 27.2 Internal Rate of Return (IRR) 27.3 Financial Statement Trend and Comparative Analysis

28 Chapter 28: Financial, Managerial & Forensic Analysis — Part II

28.1 Earned Value Management (EVM) for Capital Project Oversight 28.2 Public Sector Data Sources and Reliability Verification 28.3 Common Red Flags and Public Sector Fraud Schemes

29 Chapter 29: Internal Control Frameworks & Enterprise Risk Management — Part I

29.1 COSO Internal Control Integrated Framework & the GAO Green Book 29.2 Component 2: Risk Assessment 29.3 Internal Control Deficiencies, Corrective Action Plans & Management Reporting

30 Chapter 30: Internal Control Frameworks & Enterprise Risk Management — Part II

30.1 FMFIA Reporting Sections 30.2 Enterprise Risk Management (ERM) & OMB Circular A-123 Implementation 30.3 Core Elements of a Federal Risk Profile

31 Chapter 31: Performance Measurement, Government Auditing & the Single Audit — Part I

31.1 Performance Measurement, SEA Reporting, GPRA & Public Accountability 31.2 Baselines, Targets, Benchmarking, and Stakeholder Engagement 31.3 Government Auditing Standards: The Yellow Book & Auditor Independence 31.4 Quality Management and External Peer Review

32 Chapter 32: Performance Measurement, Government Auditing & the Single Audit — Part II

32.1 Performance Audit Fieldwork, Reporting & Auditee Responsibilities 32.2 Cause ("Why It Happened") 32.3 The Single Audit Act & Uniform Guidance (2 CFR 200 Subpart F) 32.4 Internal Control over Compliance Testing

26.4 The PMBOK Five Process Groups

Key Takeaways Explain This Topic AI

Public sector project management governs financial modernizations across the five PMBOK process groups (Initiation, Planning, Execution, Monitoring/Controlling, Closing), balancing the Triple Constraint (Scope, Time, Cost) under strict statutory appropriation and anti-deficiency constraints.

Shared services consolidate common administrative support functions—such as payroll, financial systems hosting, travel management, procurement, and HR—across multiple agencies or jurisdictions into a dedicated, customer-focused service organization.

Successful shared service partnerships depend upon structured governance instruments: comprehensive business cases, legally binding Service Level Agreements (SLAs) with measurable Key Performance Indicators (KPIs), Memoranda of Understanding (MOUs), and full cost-recovery fee models.

Last updated: September 2026

The PMBOK Five Process Groups

Public sector financial modernizations must progress through five structured process groups: +---------------------------------------------------------------------------------------------------+

  • | THE FIVE PMBOK PROJECT MANAGEMENT PROCESS GROUPS |
  • +---------------------------------------------------------------------------------------------------+
  • | 1. INITIATION: |
  • | • Define project business need and strategic alignment with civic mission |
  • | • Issue formal Project Charter signed by Executive Sponsor; appoint Project Manager |
  • | • Identify key stakeholders (oversight committees, department heads, unions, citizens) |
  • | ----------------------------------------------------------------------------------------------- |
  • | 2. PLANNING: |
  • | • Develop Project Management Plan: Scope Baseline, Schedule Baseline, and Cost Budget |
  • | • Construct Work Breakdown Structure (WBS) down to manageable work package level |
  • | • Establish Risk Management Register, Quality Plan, and Stakeholder Communication Matrix |
  • | ----------------------------------------------------------------------------------------------- |
  • | 3. EXECUTION: |
  • | • Direct and manage project execution; coordinate cross-functional agency teams |
  • | • Execute software configuration, data cleansing, and interface development |
  • | • Implement quality assurance protocols and stakeholder engagement sessions |
  • | ----------------------------------------------------------------------------------------------- |
  • | 4. MONITORING AND CONTROLLING: |
  • | • Track performance against baselines using Earned Value Management (EVM: CV, SV, CPI, SPI) |
  • | • Manage Risk Register triggers and execute mitigation strategies |
  • | • Enforce strict Change Control Management via the Change Control Board (CCB) |
  • | ----------------------------------------------------------------------------------------------- |
  • | 5. CLOSING: |
  • | • Obtain formal user acceptance sign-offs and execute administrative contract closeout |
  • | • Transition system to operational maintenance teams; release project resources |
  • | • Conduct post-project review and document organizational "Lessons Learned" |
  • +---------------------------------------------------------------------------------------------------+
  • The Public Sector "Triple Constraint"

In classical project management, the Triple Constraint (or Project Management Triangle ) dictates that every project is bounded by three interrelated variables: Scope , Time (Schedule) , and Cost (Budget) , bounded by Quality .

If an agency expands project scope (e.g., adding unexpected modules), it must inevitably increase budget or extend the schedule, or quality will fail.

The Unique Public Sector Dynamic : In private commercial projects, a project manager faced with scope expansion can often secure additional venture capital or corporate contingency funds. In the public sector, however, the financial manager is strictly constrained by enacted legislative appropriations and statutory anti-deficiency prohibitions. Exceeding the authorized capital appropriation is illegal. Furthermore, schedules are frequently tied to rigid statutory deadlines (such as a legally mandated fiscal year change or tax policy enactment date). Consequently, uncontrolled scope expansion is the primary driver of public project collapse . +---------------------------------------------------------------------------------------------------+

  • | THE PUBLIC SECTOR TRIPLE CONSTRAINT REALITY |
  • +---------------------------------------------------------------------------------------------------+
  • | |
  • | SCOPE |
  • | ^ |
  • | / \ |
  • | / \ |
  • | / \ |
  • | /QUALITY\ |
  • | / \ |
  • | / \ |
  • | COST <-------------+-------------+-------------> TIME |
  • | (Strictly Capped by (Rigid Statutory / |
  • | Legislative Appropriation) Fiscal Year Deadlines) |
  • | |
  • | CRITICAL PUBLIC MANDATE: Because Cost and Time are legally rigid, Scope MUST be strictly |
  • | policed via formal Change Control to prevent project failure and statutory violations! |
  • +---------------------------------------------------------------------------------------------------+
  • Work Breakdown Structure (WBS)

The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish project objectives and create required deliverables:

The 100% Rule : The WBS must encompass 100% of the work defined by the project scope and capture all deliverables (internal, external, and interim). Anything not in the WBS is out of scope.

Work Packages : The lowest level of the WBS consists of Work Packages —discrete units of work that can be reliably estimated for cost, assigned to a specific accountable manager, scheduled, and monitored.

Risk Management and the Risk Register

Public sector IT modernizations face immense operational, organizational, and technical risks. Disciplined risk management requires maintaining an active Risk Register throughout the project lifecycle:

Risk Identification : Systematically identifying threats (e.g., legacy vendor data corruption, key staff turnover, interface integration failures, resistance to change by operating agencies).

Risk Scoring : Evaluating each risk based on Probability (1 to 5) and Impact (1 to 5) to calculate a combined Risk Severity Score.

Risk Response Strategies :

Avoidance : Altering the project plan to eliminate the threat (e.g., eliminating custom code development to avoid maintenance failure);

Mitigation : Implementing actions to reduce probability or impact (e.g., conducting exhaustive data cleansing sprints to minimize migration errors);

Transfer : Shifting financial consequence to a third party (e.g., requiring performance bonds, fixed-price vendor contracts, or commercial warranties); and

Acceptance : Acknowledging low-level risks and establishing contingency reserves to absorb impacts.

Stakeholder Communication and Change Management

Modernizing financial systems is fundamentally an exercise in organizational change management:

Stakeholder Communication Plan : Defines formal communication channels, frequencies, and messages tailored to diverse civic constituencies (legislators, executive sponsors, department directors, union representatives, end-users, and the public).

Organizational Change Management (OCM) : Applying proven change frameworks (such as Prosci's ADKAR model or Kotter's 8-Step Change Model). Projects succeed only when end-users are prepared for workflow changes through comprehensive hands-on training, active executive sponsorship, and continuous engagement that addresses cultural anxiety.

Change Control Governance: The Change Control Board (CCB)

Uncontrolled scope expansion—commonly known as "Scope Creep" —occurs when project scope is incrementally expanded through informal requests without adjusting time, budget, or resources. To prevent scope creep, public financial initiatives must establish a formal Change Control Board (CCB) :

Mandatory Change Proposal Process : Any proposed change to project scope, schedule, budget baselines, or software requirements must be submitted via a formal written Change Request .

Impact Assessment : The project team evaluates the exact impact of the proposed change on cost, delivery milestones, staffing, interface risks, and contract terms.

CCB Adjudication : The CCB—comprising the executive project sponsor, finance director, lead technical architect, and procurement officer—reviews the request and formally approves, rejects, or defers the change. No work on any proposed change may commence without formal CCB authorization and an executed bilateral contract modification.

Practical Public Finance Scenario: Multi-Agency Financial System Consolidation and Shared Services Transition

Scenario : The State of Westland currently operates five separate, outdated financial management systems across its four largest cabinet agencies (Transportation, Human Services, Corrections, and Education). The Governor signs executive legislation establishing a centralized "State Financial Shared Services Organization" (SFSSO) hosted within the Department of Administration to consolidate all core accounting, payroll, and procurement onto a single cloud-hosted ERP platform over a three-year period.

During the initial planning and execution phases, the project leadership encounters severe operational challenges:

The Department of Transportation (DOT) refuses to adopt the standardized Chart of Accounts (COA), insisting on maintaining its own unique 36-digit accounting code structure, threatening to boycott the transition.

The preliminary project schedule was developed without a Work Breakdown Structure (WBS); milestones are arbitrarily set to match legislative election dates rather than realistic technical durations.

Agency operational managers complain that the proposed Service Level Agreement (SLA) drafted by the SFSSO contains only vague promises to "process invoices as quickly as possible," with no quantitative metrics, escalation paths, or financial accountability for processing delays.

Six months into execution, the Human Services department submits 45 separate informal "functional enhancement requests" directly to the software integration contractor's programming team, bypassing the project office and adding $2,400,000 in unbudgeted contractor billing claims.

Professional Project Management & Shared Services Corrective Plan

Establish Multi-Agency Shared Services Governance and Enforce Standard COA :

Action : Form a formal Shared Services Executive Governance Board comprised of cabinet secretaries from all participating agencies, chaired by the State Comptroller.

Resolution : The Board rules that maintaining fragmented, agency-specific Chart of Accounts structures subverts enterprise financial reporting and auditability. The SFSSO data team works with DOT to map its legacy accounting segments into the state's standardized multi-segment COA, utilizing sub-account and project coding fields to capture DOT's unique federal reporting requirements without altering the master COA.

Develop Deliverable-Oriented Work Breakdown Structure (WBS) :

Action : Halt schedule development based on political calendar dates. Convene cross-functional technical teams to construct a comprehensive, deliverable-oriented WBS down to discrete work packages (e.g., Data Cleansing, Banking Interface Development, SIT, UAT, End-User Training).

Resolution : Use the WBS to establish realistic, resource-loaded schedule baselines using the Critical Path Method (CPM), providing defensible, auditable timeline milestones to the legislature.

Restructure the Service Level Agreement (SLA) with Quantitative Metrics :

Action : Overhaul the deficient SLA draft. Replace vague qualitative language with rigorous, measurable Key Performance Indicators (KPIs):

Minimum system availability guarantee of 99.95% during core operating hours;

Mandatory requirement that 98% of clean vendor invoices be vouchered and disbursed within 5 business days to capture prompt payment discounts;

99.9% payroll direct deposit accuracy rate;

Formal escalation protocols with dedicated executive ombudsmen for unresolved inter-agency operational disputes;

Establishment of customer fee credits if the SFSSO fails to meet quarterly performance baselines.

Implement Formal Change Control Management and Halt Scope Creep :

Action : Immediately issue a formal directive to the software integration contractor instructing them to freeze work on all unauthorized functional enhancement requests.

Resolution : Enforce strict change control governance. Establish a formal Change Control Board (CCB) . All 45 enhancement requests submitted by Human Services must be documented as formal Change Requests with comprehensive cost-schedule impact assessments. The CCB approves only mission-critical statutory changes, defers non-essential requests to post-implementation software updates, and issues a formal warning regarding unauthorized commitments.

Loading diagram... Shared Services Implementation Lifecycle and PMBOK Project Governance Framework