Study guide
Supervised, Unsupervised & Reinforcement Learning
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
Supervised, Unsupervised & Reinforcement Learning
Key Takeaways Explain This Topic AI
Supervised learning needs labeled examples, and the labels — not the algorithm — are usually the schedule and budget risk; classification predicts a category, regression predicts a number.
Unsupervised learning has no ground truth, so its output must be validated by a domain SME against a business use rather than scored against a held-out answer key.
Reinforcement learning learns from a reward signal by trial and error and normally needs a simulation environment; it powers the Goal-Driven Systems and Autonomous Systems patterns.
Generative AI shifts work from training a model to grounding, prompting and evaluating a pre-trained one; evaluation becomes rubric-based human review on a fixed prompt set, not a single accuracy number.
The strongest signal for machine learning is a task whose patterns are too complex or too changeable to write as fixed rules; if the logic is known, stable and enumerable, deterministic rules are cheaper, auditable and instantly changeable.
Last updated: August 2026
Three Ways a Model Learns
Machine learning is not one thing. Which of the three learning approaches your team proposes decides whether you must buy or create labeled data, how long Phase 3 Data Preparation and Phase 4 Model Development will run, and — the part project managers most often miss — whether the result can be evaluated objectively at all. You do not need to write the code. You do need to know which approach is on the table before you agree to a schedule.
Supervised Learning
The team gives the algorithm examples that already carry the right answer — a label — and the model learns to reproduce it on new cases. It takes two shapes. Classification predicts a category: fraud or not fraud, which of eleven claim types, which diagnosis code. Regression predicts a number: next month's demand, days until this pump fails, expected claim cost.
Supervised learning is the workhorse of enterprise AI, and it is also where projects quietly bleed schedule, because the labels are the deliverable nobody budgeted. Ask three questions during Phase 2 Data Understanding:
Do labels exist at all? "We have ten years of claims" is not the same as "we have ten years of claims each marked as fraudulent or clean."
Who will create them, and at what cost? Labeling 20,000 images or 5,000 clinical notes is a staffed workstream with its own schedule, quality process and budget line — not a task.
Are the labels trustworthy? Two annotators disagreeing on the same record is a measurable problem you can quantify and fix with a coding guide. Worse is a label that encodes past behavior: your "fraud" flag only marks the fraud investigators happened to catch, and a "successful hire" label reproduces whoever the company used to hire.
What you get in return for that cost is objectivity. A supervised model can be scored on data it has never seen, so Phase 5 Model Evaluation has a defensible, numeric answer.
Unsupervised Learning
No labels. The algorithm finds structure on its own. Clustering groups similar records — customer segments, equipment behaving alike, documents about the same topic. Dimensionality reduction compresses many variables into a few that carry most of the signal. It is often the cheapest thing to run because you skip labeling entirely, and it is genuinely useful during Phase 2 for seeing what is actually in the data before you commit to a solution.
The catch is evaluation. With no ground truth there is no held-out answer key, so "is this segmentation good?" is a judgment made by a domain expert, not a score. Plan for that: put a subject matter expert in the loop, schedule review sessions, and write acceptance in business terms before the work begins — for example, "the segments are distinguishable enough that marketing can write a different offer for each." Never let an unsupervised deliverable be signed off on the strength of a colorful chart.
Reinforcement Learning
The system learns by acting, receiving a reward signal , and adjusting — trial and error against an objective rather than imitation of labeled examples. It needs a simulation environment or another safe place to explore, because early attempts are bad by design and you cannot let a learning agent practice on live pricing or live equipment. Reinforcement learning is what typically sits behind the Goal-Driven Systems and Autonomous Systems patterns.
Three implications for you. The simulator is frequently a larger build than the model itself, and it belongs in the estimate. Specifying the reward is a business decision with real consequences, because an agent rewarded only for margin will find margin at the expense of churn. And validation runs in shadow mode — the agent proposes, humans decide — before it is allowed to act on anything.
Generative AI and Large Language Models
Generative AI is a distinct case with different economics, evaluation and risks. Instead of training a model on your labeled data, you usually take a large language model (LLM) somebody else pre-trained and adapt it — through prompting, retrieval from your own approved content, or fine-tuning on a modest set of examples. That inverts the usual project shape: Phase 3 gets lighter on labeling and heavier on curating trustworthy, current, permissioned source content, while Phase 5 Model Evaluation gets considerably harder.
There is no single accuracy number for "write a good claim summary." Evaluation becomes rubric-based and human-judged: a fixed set of representative prompts, defined quality criteria, and trained reviewers — all of which you must schedule and staff. The risk properties differ too. Output can be fluent and wrong. The same prompt can produce different answers on two runs. Sensitive data can leave the organization through a third-party service. And a vendor can change the model version underneath you, shifting behavior with no change on your side. Treat version pinning, a regression prompt set, and a data-handling agreement as Phase 1 scope items.
Choosing Between Approaches
Approach What the data must look like Typical evaluation Project-management implication
Supervised — classification Historical records each carrying the correct category Precision, recall and a confusion matrix on held-out data Labeling is a staffed workstream; objective sign-off is achievable
Supervised — regression Historical records with the numeric outcome recorded Average size of the error against actuals on held-out data Needs long, clean history; plan for relationships that shift
Unsupervised Records with useful attributes; no labels required Judgment of a domain SME against a stated business use Cheap to run, expensive to agree on; define acceptance in business terms up front
Reinforcement A defined reward, explicit constraints, and a simulator or safe sandbox Objective attained under constraints in simulation, then shadow mode The simulator can exceed the model in cost; reward design is a business decision
Generative / LLM Curated, current, permissioned content to ground answers on Rubric scoring by trained human reviewers on a fixed prompt set Staff the evaluation, pin model versions, control what data leaves the organization
The Trap: Machine Learning Where Rules Would Do
The exam punishes reaching for machine learning by default. Deterministic rules are cheaper to build, instantly changeable, auditable line by line, and they never drift. If the logic is known, stable and enumerable — "flag any invoice over 10,000 dollars without a purchase order," "route Spanish-language calls to the Madrid queue" — write the rule. Adding a model there buys you cost, latency, an explainability problem and a permanent monitoring obligation in exchange for nothing.
The strongest signal for machine learning is the opposite condition: the task depends on patterns in data that are too complex to express as fixed rules, or that keep changing , and enough historical data exists to learn them. Fraud qualifies, because adversaries adapt faster than any rule committee. Forecasting demand across thousands of items qualifies. Reading handwriting qualifies. Approving an expense against a fixed policy does not. When you review a proposed solution in Phase 1, ask the team to state the rule out loud. If they can state it, you do not need a model.