about 3.3% of the exam content - about 90 minutes - 14 practice questions
0:00 / --:--
Reading
Continuous improvement means the project gets better while it is running, not just in a
report written after everyone has moved on. PMI's position is blunt: if your team finishes the same way
it started, you wasted the information the work gave you. On the exam, the correct answer is almost
always the one where the team examines how it works, changes something small, and measures whether the
change helped.
Retrospectives and lessons learned
A retrospective is a recurring, timeboxed team meeting to inspect how the work is
going and decide on improvements. Adaptive teams hold one at the end of every iteration. Predictive and
hybrid teams hold the same conversation at phase gates and major milestones; the name changes, the
behavior should not.
A healthy retrospective often follows five moves (a common facilitation pattern): set the stage, gather data, generate insight, decide what to
do, and close. The output is one or two concrete, owned, dated action items, not a
long list of complaints. If a retrospective produces no action, or produces the same action three times
in a row, the retrospective itself is broken and that is what the team should fix first.
Two related but distinct artifacts:
Lessons learned register: created early and updated throughout the
project. It is a living project document, so this project can benefit from its own learning.
Lessons learned repository: the organization-wide store where lessons go at
closeout so future projects benefit. That repository is an organizational process asset
(OPA).
Exam trap
"We will capture lessons learned at the end of the project" is a wrong answer. Lessons are captured
continuously in the register during execution and transferred to the repository at closure. Waiting
until closure means this project never got to use what it learned.
Kaizen, PDCA, and the Deming cycle
Kaizen is Japanese for "change for the better", a philosophy of many small,
frequent, team-generated improvements rather than rare, expensive overhauls. Its opposite pattern,
kaikaku, is the occasional breakthrough change. Kaizen is the everyday habit; breakthrough is
the exception.
The engine of kaizen is PDCA, the Plan-Do-Check-Act cycle popularized by W. Edwards
Deming (and often called the Deming or Shewhart cycle):
Stage
What happens
GCHS example
Plan
Identify the problem, find the root cause, design a change and how you will measure it
Punch lists average 22 items per home; team suspects unclear finish standards
Do
Run the change small: a pilot, one crew, one house
Try a one-page photo standard on the next three rehabs only
Check
Study the result against the measure; did it actually work?
Punch items drop to 9 per home on the pilot houses
Act
Adopt and standardize it, adjust it, or abandon it, then start the cycle again
Add the photo standard to the GCHS field manual for all crews
Note that Check is the step teams skip. Changing something and never measuring
whether it helped is not improvement; it is churn.
Lean and the eight wastes
Lean thinking asks one question about every activity: does the customer (for GCHS, the homeowner and
the funder) value this? If not, it is waste (Japanese: muda) and should be
reduced or removed. The eight wastes are commonly remembered with the acronym DOWNTIME.
Waste
Meaning
On a GCHS rehab
Defects
Work that must be redone
Grab bar anchored into drywall instead of blocking; ripped out and redone
Overproduction
Producing more or sooner than needed
Cutting trim for six houses when only one is ready to receive it
Waiting
Idle time between steps
Crew standing by three days for an inspection slot
Non-utilized talent
Not using people's skills and ideas
A 20-year carpenter never asked how to sequence the work
Transportation
Unnecessary movement of materials
Hauling the same lumber between three staging yards
Inventory
Stock sitting unused, tying up cash and spoiling
Pallets of flooring stored six months in a humid warehouse
Motion
Unnecessary movement of people
Tools stored in the truck instead of at the work station
Extra processing
Doing more than the requirement demands
Three coats of paint in a closet where the spec calls for two
Value stream mapping is the Lean tool that makes waste visible: you map every step
from request to delivered home, mark which steps add value and which do not, and attack the biggest
non-value-adding blocks first.
Six Sigma and the improvement toolkit
Six Sigma is a data-driven method aimed at reducing variation and defects.
Where Lean chases waste and speed, Six Sigma chases consistency, and most organizations blend the two
as Lean Six Sigma. Its improvement cycle is DMAIC: Define, Measure, Analyze, Improve,
Control. Notice that Analyze (root cause) comes before Improve. PMI tests that order constantly:
understand the cause before you install the fix.
5 Whys: ask why repeatedly to walk from symptom to root cause.
Fishbone (Ishikawa / cause-and-effect) diagram: organizes possible causes into
categories so the team looks past the first obvious answer.
Pareto chart: ranks defect categories by frequency; as a rule of thumb, about 80% of the problems come from about 20% of the causes, so you fix the tall bars first.
Control charts: plot a process over time against control limits to tell normal
variation from a real signal that the process has shifted.
Histograms, scatter diagrams, flowcharts, and check sheets: the rest of the basic
quality toolkit.
Related quality vocabulary that shows up in improvement questions: cost of quality
splits into cost of conformance (prevention and appraisal: training, inspections) and cost of
nonconformance (internal and external failure: rework, warranty callbacks, a homeowner complaint to
the funder). Prevention is usually cheaper than failure, which is why improvement spending pays for
itself.
Audits, benchmarking, and maturity
Quality audit: a structured, usually independent review of whether the project
is following organizational policies and processes. It looks at the process, identifies good
practices worth sharing, and produces improvement recommendations. Contrast with quality
control, which inspects the deliverable to see whether it meets specification.
Benchmarking: comparing your practices or results against other projects,
organizations, or industry standards to set improvement targets. GCHS comparing its cost per
accessibility modification to peer nonprofits is benchmarking.
Maturity models (such as OPM3 or CMMI-style models): assess how consistently and
repeatably an organization performs project work, on a scale from ad hoc and heroic to measured and
optimizing. They tell leadership where the organization sits and what the next capability step is.
Process improvement plan: a subsidiary plan describing how processes will be
analyzed and improved: process boundaries, configuration, metrics, and targets.
Improving in adaptive and hybrid environments
Agile bakes improvement into the rhythm rather than scheduling it separately.
Inspect and adapt: every review and retrospective is a formal inspection point;
what is learned changes the next iteration immediately.
Experiments and spikes: improvement ideas are treated as hypotheses run in a
timebox. "We think a two-person pre-walk cuts punch items in half; let us try it for two sprints and
measure."
Retrospective actions on the backlog: improvement work is put in the backlog and
prioritized with feature work, so it competes fairly and actually gets done.
Team-owned metrics: cycle time, throughput, escaped defects, and rework
percentage give the team evidence instead of opinion. Metrics are for the team to improve with, not
for management to rank people with.
Psychological safety: people only report the truth in a retrospective if it is
safe to do so. Blameless framing is a prerequisite for improvement, not a nicety.
Key points
Improvement follows a fixed logic on the exam: measure the current state, find the root cause, make a
small change, verify the result, then standardize it and share it as an organizational process asset.
Any answer that installs a solution before understanding the cause, or that improves something without
measuring the effect, is the wrong answer.
Two 2026 themes belong here as well. AI can accelerate improvement by mining project
history for patterns humans miss (recurring defect types, estimate bias by crew, seasonal cycle-time
shifts), but the team still owns the decision and must validate the data. And
sustainability is now an improvement dimension in its own right: reducing material
waste, cutting fuel used hauling between sites, and raising energy performance are genuine
continuous-improvement targets, not side projects.
Practice Questions
1. What is the primary purpose of a retrospective?
To inspect how the team works and agree on improvements for the next period
To evaluate individual team member performance and report it to functional managers
To formally approve changes to the scope baseline
To document the final status of deliverables for the sponsor
Answer: a. A retrospective is a team inspection of its own process, producing concrete improvement actions for the near future. Evaluating individuals is explicitly not its purpose: performance appraisal in a retrospective destroys the psychological safety the meeting depends on.
2. A project manager plans to hold a single lessons learned session at project closeout. What is the MOST significant weakness of this approach?
The information cannot be stored in the organizational repository until the sponsor approves it
Closeout sessions require sponsor attendance, which is hard to schedule
The current project gains nothing from its own learning
Lessons learned are only valid for adaptive projects
Answer: c. Lessons must be captured continuously in the lessons learned register so the project can correct itself while it is still running. A single closeout session may help future projects but does nothing for the one that paid for the learning.
3. Which statement correctly distinguishes the lessons learned register from the lessons learned repository?
The register is an organizational asset owned by the PMO; the repository is a project document kept by the team
The register is updated throughout the project; the repository is the organization-wide store
They are two names for the same artifact
The register is used in predictive projects and the repository in adaptive projects, by convention
Answer: b. The register is a living project document updated throughout execution. At closure its content is transferred to the organization-wide lessons learned repository, which is an organizational process asset available to future projects. The answer reversing the two is the common trap.
4. Kaizen is BEST described as:
A one-time breakthrough redesign of a major process
A philosophy of frequent, small, team-generated improvements
A statistical method for reducing defects to 3.4 per million
An audit performed by an independent quality group
Answer: b. Kaizen means change for the better and refers to continuous small improvements generated by the people doing the work. A one-time breakthrough redesign is the contrasting concept (kaikaku), and the 3.4-defects-per-million figure belongs to Six Sigma.
5. Place the PDCA cycle in the correct order.
Plan, Deliver, Control, Assess
Prepare, Design, Construct, Approve
Plan, Check, Do, Act
Plan, Do, Check, Act
Answer: d. PDCA is Plan (design the change and its measure), Do (pilot it small), Check (study the results against the measure), Act (standardize, adjust, or abandon). Putting Check before Do would mean measuring a change that has not been run yet.
6. A GCHS crew introduces a new pre-drywall photo checklist and immediately rolls it out to every crew without collecting punch-list data. Which PDCA stage was skipped?
Do
Check
Act
Plan
Answer: b. Check is the step where results are compared against the intended measure to confirm the change actually helped. Skipping it means the organization standardizes a practice with no evidence; this is churn, not improvement.
7. A GCHS crew stands idle for three days waiting on an inspection slot before framing can continue. Which Lean waste (DOWNTIME) does this represent?
Motion
Overproduction
Defects
Waiting
Answer: d. Idle time between steps, with the crew unable to proceed until the inspection happens, is exactly the Waiting waste. Motion refers to unnecessary movement of people, not idle time.
8. A quality audit at GCHS primarily assesses:
Whether the project follows organizational policies and processes, and what to improve
Individual crew member performance ratings for use in the next round of reviews
The dollar cost of nonconformance on the current rehab, split by internal and external failure
Whether an installed grab bar meets the ADA blocking specification
Answer: a. A quality audit is a structured review of whether the project follows its policies and processes, surfacing good practices and improvement recommendations. Checking whether the grab bar itself meets spec is quality control, which inspects the deliverable rather than the process.
9. In the DMAIC improvement cycle, which stage finds the root cause and must be completed before Improve installs a fix?
The order does not matter as long as a fix is applied
Control
Define, and no other stage matters
Analyze
Answer: d. DMAIC runs Define, Measure, Analyze, Improve, Control, and Analyze (finding the root cause) must happen before Improve installs a fix. Installing a fix before analyzing the cause is the same trap PMI tests across every root-cause topic.
10. GCHS pays for moisture-testing training so crews catch problems before drywall goes up. This spending is best classified as:
Cost of conformance, prevention
Cost of nonconformance, internal failure
Cost of nonconformance, external failure
Cost of conformance, appraisal
Answer: a. Training that stops a defect from ever occurring is prevention spending under cost of conformance. Appraisal is also conformance spending, but it means inspecting for defects after the fact, such as a moisture reading itself, not training crews to avoid the defect.
11. GCHS compares its cost per accessibility modification against peer nonprofits to set an improvement target. This is:
A quality audit
Root cause analysis
Value stream mapping
Benchmarking
Answer: d. Comparing practices or results against other organizations to set improvement targets is benchmarking. A quality audit reviews adherence to the organization's own processes rather than comparing against outside peers.
12. A maturity model such as OPM3 is used at GCHS to:
Calculate the expected monetary value of identified project risks and size the contingency reserve
Approve individual scope change requests
Assess how consistently the organization performs project work and name its next capability step
Replace the lessons learned repository
Answer: c. A maturity model rates an organization from ad hoc to measured and optimizing, showing leadership where it sits and what capability to build next. It is a diagnostic and planning tool, not a change control or risk technique.
13. Why is psychological safety described as a prerequisite for improvement rather than a nicety?
People only report the truth in a retrospective if it feels safe to do so
It removes the need for a facilitator to run the meeting
It replaces the need for measurable metrics
It guarantees management will approve every retrospective action
Answer: a. Honest input is the raw material a retrospective needs, and people only give it when blameless framing makes it safe to speak up. Without that safety, problems get hidden and the team measures nothing real.
14. A GCHS team believes a two-person pre-drywall walk-through will cut punch items in half. They run it for two sprints and measure the result before deciding whether to adopt it. This is BEST described as:
A quality audit
Benchmarking against peer organizations
An experiment that treats the idea as a hypothesis tested in a timebox
A kaikaku breakthrough redesign
Answer: c. Running a proposed improvement as a timeboxed test with a measured result before committing is the agile experiment pattern, closely related to a spike. Kaikaku describes a rare, large breakthrough change, not a small measured trial.
Glossary
Retrospective
A recurring, timeboxed team meeting to inspect how the work is going and decide on concrete improvements.
Kaizen
A philosophy of frequent, small, team-generated improvements, as opposed to rare breakthrough change (kaikaku).
PDCA (Deming cycle)
Plan-Do-Check-Act, the cycle of designing a change, piloting it small, measuring the result, and standardizing, adjusting, or abandoning it.
DMAIC
Define, Measure, Analyze, Improve, Control; the Six Sigma improvement cycle in which root cause is found before a fix is installed.
Value stream mapping
A Lean tool that maps every step from request to delivery to identify which steps add value and which are waste.
Cost of quality
The total spent on conformance (prevention and appraisal) and nonconformance (internal and external failure).
Quality audit
A structured, usually independent review of whether a project follows organizational policies and processes.
Benchmarking
Comparing an organization's practices or results against other projects or industry standards to set improvement targets.