Study guide

The CPMAI Methodology: Six Phases and Data-Centric Iteration

PMI Certified Professional in Managing AI PMI-CPMAI

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: PMI-CPMAI Exam Foundations & the CPMAI Methodology

The PMI-CPMAI Exam: Format, Eligibility, Fees & Scoring The CPMAI Methodology: Six Phases and Data-Centric Iteration CPMAI vs Waterfall, Agile, and CRISP-DM

2 Chapter 2: AI and Machine Learning Fundamentals for CPMAI

The Seven Patterns of AI Supervised, Unsupervised & Reinforcement Learning Why AI Projects Fail: Value, Data Readiness & Right-Sizing

3 Chapter 3: Domain I — Support Responsible and Trustworthy AI Efforts (15%)

Oversee the Privacy and Security Plan Manage AI/ML Transparency in Data and Algorithm Selection Conduct Bias Checks on Model, Data, and Algorithm Monitor Regulatory and Policy Compliance Manage Accountability Documentation and the Audit Trail

4 Chapter 4: Domain II — Identify Business Needs and Solutions, Part 1 (26%)

Identify the Problem to Be Solved Evaluate Initial AI Feasibility Conduct Security, Safety, and Ethics Risk Assessments Develop the AI Project Scope Statement Determine Return on Investment

5 Chapter 5: Domain II — Identify Business Needs and Solutions, Part 2

Manage Adoption and Integration Risks Draft the AI Solution Define Success Criteria and KPIs Support Business Case Creation Identify Project Resources: People, Hardware, and Contractors

6 Chapter 6: Domain III — Identify Data Needs, Part 1 (26%)

Define the Required Data Identify Data Subject-Matter Experts Identify Data Sources and Locations Coordinate the AI Workspace and Infrastructure Gather the Required Data

7 Chapter 7: Domain III — Identify Data Needs, Part 2

Check Data Privacy, Compliance, and Access Oversee Data Evaluation Determine If the Data Meets Solution Needs: The Phase 2 Go/No-Go Convey Data Understanding to Leadership

8 Chapter 8: Domain IV — Manage AI Model Development and Evaluation (16%)

Oversee AI/ML Model Technique and Algorithm Selection Oversee Model QA/QC and Configuration Management Manage AI/ML Model Training Manage Data Transformation and Data Preparation Verify Data Quality for the Data Preparation Go/No-Go Verify the Model Is Ready for Operationalization

9 Chapter 9: Domain V — Operationalize AI Solution, Part 1 (17%)

Manage Creation of the AI Solution Deployment Plan Manage the AI Solution Deployment Oversee Model Governance in Production Oversee AI Solution Metrics and Performance Monitoring

10 Chapter 10: Domain V — Operationalize AI Solution, Part 2

Prepare the Final Report and Lessons Learned Manage the AI Solution Transition Plan Oversee the AI Solution Contingency Plan

The CPMAI Methodology: Six Phases and Data-Centric Iteration

Key Takeaways Explain This Topic AI

CPMAI has six phases in order: Business Understanding, Data Understanding, Data Preparation, Model Development, Model Evaluation, and Model Operationalization.

Each CPMAI phase answers one go/no-go question and produces a concrete artifact, such as the scope statement in Phase 1 or the data sufficiency assessment in Phase 2.

Data Understanding and Data Preparation are full phases with their own gates, and data work is roughly 31% of the exam blueprint — all of Domain III at 26% plus the data-centric tasks inside Domain IV.

CPMAI is iterative: evidence from a later phase sends you back to an earlier one rather than forward with a known defect.

Each CPMAI iteration should cover a slice narrow enough to fail cheaply and complete enough to deliver a usable increment through all six phases.

Last updated: August 2026

Learn the Phases as Decisions, Not a Schedule

CPMAI (Cognitive Project Management in AI) is the six-phase methodology PMI-CPMAI is built on, and the ECO states that the exam tests its application. Treat each phase as a decision point rather than a block of calendar time: every phase asks one go/no-go question, produces at least one artifact you can put in front of a sponsor, and hands the next phase something it cannot start without.

Phase 1 — Business Understanding

You establish that a real business problem exists, that AI is an appropriate way to address it, and that the value justifies the spend. The work includes identifying the problem to be solved, assessing initial feasibility, running risk assessments, drafting scope, estimating return on investment (ROI), defining success criteria and key performance indicators (KPIs), and supporting the business case. Artifacts: problem statement, AI project scope statement, success criteria and KPIs, ROI estimate, business case input. Go/No-Go: Is this problem worth solving, and is AI the right approach?

Phase 2 — Data Understanding

You find out what data actually exists, who owns it, whether you can lawfully use it, and whether it plausibly contains the signal the solution needs. You identify data SMEs and data sources, inspect samples, and report sufficiency to leadership in plain language. Artifacts: data inventory and source catalog, data SME list, data quality and sufficiency assessment, privacy and access review, leadership briefing. Go/No-Go: Does accessible, lawful, sufficient data exist? This is the phase teams skip under schedule pressure, and the one whose omission kills projects late and expensively.

Phase 3 — Data Preparation

The team cleans, labels, transforms, and splits the data into training, validation, and test sets. Your job is oversight and traceability, not writing pipelines: insist on a labeling standard, documented lineage, and a check that the prepared set represents the population the model will serve. Artifacts: prepared dataset, data dictionary, labeling standard, transformation and lineage log. Go/No-Go: Is the data clean, labeled, and representative enough to train on without baking in bias?

Phase 4 — Model Development

The team selects techniques, trains candidate models, and tunes them. Your contribution is discipline: require a baseline (the current manual process or a simple rule), reproducible experiment logging, and a stop rule so tuning does not run indefinitely. Artifacts: trained candidate models, experiment log, model card, baseline comparison. Go/No-Go: Does a candidate beat the baseline by enough to matter?

Phase 5 — Model Evaluation

Candidates are judged against the Phase 1 success criteria and responsible-AI thresholds, not against technical metrics alone. This is where bias checks, explainability review, and error-cost analysis happen — a false negative in claims triage costs something very different from a false positive. Artifacts: evaluation report mapped to the KPIs, bias and fairness results, go/no-go memo. Go/No-Go: Does this meet the business criteria and the responsible-AI requirements, and what does being wrong cost?

Phase 6 — Model Operationalization

You plan and manage deployment, stand up governance and monitoring, transition the solution to an owning team, and close the project out. Artifacts: deployment plan, monitoring and metrics plan, model governance rules and retraining triggers, transition plan and RACI (responsible, accountable, consulted, informed) chart, contingency and rollback plan, final report and lessons learned. Go/No-Go: Can we run, monitor, support, and reverse this, and who owns it on Monday?

Phase-to-Blueprint Map

Phase Key question Main artifact ECO domain(s) tested

1. Business Understanding Is it worth solving, and is AI right for it? Scope statement, success criteria, business case II (26%)

2. Data Understanding Does usable, lawful, sufficient data exist? Data inventory and sufficiency assessment III (26%)

3. Data Preparation Is the data clean, labeled, representative? Prepared dataset, data dictionary, lineage log III, plus IV (data transformation, data-quality go/no-go)

4. Model Development Does a candidate beat the baseline? Experiment log, model card IV (16%)

5. Model Evaluation Does it clear business and responsible-AI criteria? Evaluation report, bias check, go/no-go memo IV, plus I (15%)

6. Model Operationalization Can we run, monitor, and own it? Deployment, monitoring, transition, contingency plans V (17%)

Domain I (Support Responsible and Trustworthy AI Efforts) is deliberately not confined to one row — privacy, transparency, bias, compliance, and audit trail obligations run through every phase.

Two Properties the Exam Hammers

CPMAI is iterative. Phases run in order inside an iteration, but you return to an earlier phase whenever evidence demands it. Data Understanding reveals that failure labels are unreliable, so you go back to Business Understanding and re-scope. Model Evaluation misses the KPI, so you return to Data Preparation for better features rather than tuning forever. Production monitoring detects drift, so you loop back to Data Understanding with fresh data. On the exam, the answer that presses forward with a known defect and "fixes it in a later phase" is almost always wrong.

CPMAI is data-centric. Data Understanding and Data Preparation are first-class phases with their own gates — not a story in a sprint backlog and not a prerequisite someone quietly handles. Domain III is 26% of the blueprint on its own — defining required data, identifying data SMEs and sources, gathering data, checking privacy and access, and evaluating sufficiency. Domain IV then adds two data-centric tasks of its six, managing data transformation and verifying data quality at the Data Preparation go/no-go, which is roughly another 5% . Count them together and data work is about 31% of the blueprint — close to a third of your scored items, before a single question about modeling. Do not inflate that figure by claiming all of Domain IV: the other four Domain IV tasks are technique selection, QA/QC, training, and operationalization readiness, and they are not data work.

Fail Fast in Small Iterations

CPMAI expects small, complete loops rather than one long march. Each iteration should be narrow enough that failure costs weeks instead of quarters, and complete enough that success ships something usable.

Narrow the slice. One claim type, one product line, one region, one asset class — not the whole enterprise portfolio.

Run all six phases on that slice. A slice that stops at Model Evaluation has proved nothing about operations.

Deliver a usable increment. Something a real user or process consumes, so business value is observable and monitoring is real.

Gate it. End the iteration with an explicit go/no-go: expand the scope, iterate again on the same slice, or stop.

Kill cheaply. Discovering in week six that the data cannot support the use case is a successful iteration. It preserves budget that a nine-month single delivery would have burned.