September 7, 2026 · 8 min read
TL;DR: Options that route something to the change control board appear 39 times in this bank. They are keyed 7 times. The filter that resolves most of them is a single question: does this project have an approved baseline that the change would move?
The change control board is a favourite distractor for a reason. It sounds like process discipline, and process discipline is usually what the exam rewards. But the board exists to protect something specific, and when that something is not present or not affected, sending the problem there is not discipline. It is misrouting.
We counted every answer option in this bank's 2,141 questions naming the change control board or the CCB.
| Context | Keyed | Distractor |
|---|---|---|
| Predictive or baseline-governed scenarios | 6 | 28 |
| Agile or adaptive scenarios | 1 | 4 |
| All appearances | 7 | 32 |
The adaptive row is the more useful of the two despite its small numbers, because it is absolute in practice. In the adaptive scenarios this bank keys backlog reprioritization, backlog refinement, and the team's own cadence. The board is offered every time and taken none of them.
An approved baseline, and nothing else. Read the keyed cases and every one of them has a committed scope, cost, or schedule that moved:
The through-line is that a decision belonging to the baseline's owner is being returned to them, with the analysis already done. That last part matters: the keyed change requests present quantified impact or named options. They do not ask the board to work out what is wrong.
Common trap: "It is a change, so it goes to the change control board." Change is not the test. A baseline that the change would move is the test. This bank's CCB distractors repeatedly offer the board for things that are not baseline changes: an issue that needs a plan, a compliance update that needs formalizing, a stakeholder's request that needs a conversation. One question even offers referring three items to the board without further review, which skips the impact analysis the board depends on.
Because there is no baseline to protect. On an adaptive project the mechanism that decides what gets built next is the backlog, and the person who orders it is the product owner. Two bank questions make this explicit:
A significant scope change emerges halfway through an agile project after the team realizes the product will not deliver its promised benefits. Contingency and management reserves are both available. Three of the four options are process-correct in a predictive world: take it to the board, use the contingency reserve, review the change management plan. The keyed answer reprioritizes the backlog and starts the highest-priority item.
At a sprint review on a hybrid project, the product owner returns with a long list of changes after a successful sprint. Keyed: the product owner takes them into backlog refinement, because a batch of changes has to be weighed against everything else waiting before any of it is built. Following the change control process and implementing once the board approves is the distractor, and the explanation is blunt about why: a change control board has no part in the sprint cycle.
There is one further scenario worth knowing, where the board is not wrong so much as beside the point. A pharmaceutical project under heavy uncertainty has the project manager meeting the board constantly, and that churn has pushed the project behind schedule. The question asks what could have prevented it. Relaxing the board's rules is a distractor. The keyed answer adopts an adaptive approach suited to the uncertainty. Constant change control is a symptom of the wrong delivery approach, not a governance failure to be tuned away.
The change management plan, not the scope management plan.
One bank question is precise about this and easy to get wrong. A senior user identifies a major scope change during user acceptance testing, you may lack the money or resources, and you need approval. The keyed answer reviews the change management plan for the change control process and the approvers on the board, not the scope management plan.
The distinction is worth holding. The scope management plan answers whether a change to scope is permitted and how scope changes are processed. The change management plan answers how approval is obtained and who grants it, including the board's composition, what it can approve, and what has to go higher. When a question asks who decides, it is the change management plan.
Getting a wrong answer explained rather than just marked wrong is what makes this one stick, because the CCB distractors are rarely absurd. They are usually the right answer to a slightly different question.
When is the change control board the right answer? When an approved baseline is affected and the decision belongs to whoever owns that baseline. Across this bank the CCB is keyed 7 times, and every keyed case involves a committed scope, cost, or schedule that has moved or is about to move on a project running to baselines.
Does the change control board apply on an agile project? No. In this bank's adaptive scenarios the CCB is never the keyed answer. One question puts a significant mid-project scope change in front of an agile team with reserves available, and taking it to the change control board is a distractor. The keyed answer reprioritizes the backlog. Another has a product owner return from a sprint review with a list of changes, and the keyed answer is backlog refinement, not the board.
What is the most common CCB distractor? Sending something to the board that is not a change to a baseline. This bank offers referring all items to the board without review, submitting an issue to the board to approve a plan for it, and asking the board to re-approve work it already approved. All three treat the board as a general-purpose decision body rather than the authority over a baseline.
Does having schedule float exempt a change from change control? No. One bank question has a delivery slip two weeks on an activity that is not on the critical path, with the contractor offering to cover the cost. Doing nothing is a distractor. The keyed answer raises a change request and takes it to the board, because a committed date moved and money changed hands.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained, not just marked wrong. Start the free 20-question sample - no card, no signup required to try it.
When is the change control board the right answer?
When an approved baseline is affected and the decision belongs to whoever owns that baseline. Across this bank the CCB is keyed 7 times, and every keyed case involves a committed scope, cost, or schedule that has moved or is about to move on a project running to baselines.
Does the change control board apply on an agile project?
No. In this bank's adaptive scenarios the CCB is never the keyed answer. One question puts a significant mid-project scope change in front of an agile team with reserves available, and taking it to the change control board is a distractor. The keyed answer reprioritizes the backlog. Another has a product owner return from a sprint review with a list of changes, and the keyed answer is backlog refinement, not the board.
What is the most common CCB distractor?
Sending something to the board that is not a change to a baseline. This bank offers referring all items to the board without review, submitting an issue to the board to approve a plan for it, and asking the board to re-approve work it already approved. All three treat the board as a general-purpose decision body rather than the authority over a baseline.
Does having schedule float exempt a change from change control?
No. One bank question has a delivery slip two weeks on an activity that is not on the critical path, with the contractor offering to cover the cost. Doing nothing is a distractor. The keyed answer raises a change request and takes it to the board, because a committed date moved and money changed hands.