PMP 2026 | 84 | Scenario Lab: Timed Situations, Set Two

The second timed situational set adds six more opportunities to practice decisions under competing demands. An urgent Sprint request, weak adoption after delivery, and a disputed supplier interface challenge your ability to separate stakeholder pressure from the conditions that…

This second short practice set combines adaptive work, benefits, supplier decisions, release readiness and cost. It contains six fictional situations rather than a full exam simulation. For each, identify the immediate condition and the role that can make the relevant decision. Records help establish the facts, while action must also fit the actual obligations and authority. A tidy paper trail is not enough if the chosen action leaves the problem unresolved. Explain why the response works in the case before treating it as a useful pattern.

Welcome to Certified, the P M P prepcast. This is episode eighty four of season one. Today we are exploring the second set of timed situational practice.

Artifacts you’ll need in this set include scope and schedule baselines, product backlogs, acceptance criteria, change logs, risk and issue registers, statements of work, interface control documents, and benefits registers. Each scenario will push in different directions, one testing how you protect a sprint, another how you handle benefits leakage, another how you interpret a contract dispute. What matters is that you resist emotional responses and return to the evidence. Exam questions and real sponsors alike reward the project manager who can say, “Here is the artifact, here is the impact, here is the policy path.”

You can use a practice budget of sixty to seventy-five seconds per scenario when you have a safe opportunity to pause. Longer evidence-based items may need more time, so do not treat this drill as a mandatory exam pace. Read or recall the situation, identify what is already known and choose the step that is still needed. Immediate protection or a reporting duty may take priority over a meeting. Review uncertain reasoning afterward instead of relying on a rule that escalation is always late.

The first case is an agile mid-sprint conflict. A vice president tries to insert a “must-have” story, even though the sprint backlog is full and compliance tests are already queued. The team is stretched, but the V P insists urgency trumps process. Artifacts to consult are the sprint backlog, the sprint goal, and the backlog ordering policy. These define capacity, commitments, and rules for new requests. The trap here is to appease either the stakeholder or the team by cutting corners. The professional move is to apply the backlog policy transparently, not to improvise.

In Scrum, involve the Product Owner and Developers in assessing the request against the Sprint Goal and available capacity. The Developers can adapt their plan through discussion with the Product Owner without endangering the goal or reducing quality. There is no rule that equal story-point weight makes a swap acceptable. Deferral may be appropriate, or the Product Owner may cancel a Sprint whose goal is obsolete. Route any affected external commitment through its own decision owner. Explain which condition supports the response in this case.

The second case tests benefits stewardship. A new portal has shipped, but adoption is below target, and feature requests are piling up. Stakeholders want to build more functionality, but metrics show users are struggling with what already exists. The artifact to consult is the benefits register, supported by adoption metrics and training plans. These show the gap between expected and actual outcomes. Adding features without understanding the adoption obstacle can waste effort or worsen confusion. A justified product change may itself help resolve the obstacle, so compare it with training, access and workflow responses. The benefit owner must be engaged here to own the outcome and decide corrective actions.

Investigate the adoption obstacle with users, operations and the benefit owner. Training and job aids may help a capability gap; access, workflow or product changes may be needed for a different problem. Test a justified response and compare the outcome with a meaningful baseline. Update the forecast with the evidence instead of declaring success from delivery alone. More features are not automatically wrong, but they need a reason linked to the outcome. Keep the continuing owner accountable for measuring that outcome.

The third case shifts to vendor management. An interface is late, and the vendor claims the specification was unclear. Penalties loom, and frustration builds. The artifacts to consult are the statement of work and the interface control document. These define the deliverable and its boundaries. The decision log will capture how the dispute is resolved. Penalizing immediately risks alienating a partner still needed. Adding another vendor introduces complexity. Letting the teams “work it out” informally ignores accountability. The project manager must re-anchor the discussion in the agreed artifacts.

Review the statement of work and interface evidence with the supplier, technical leads and authorized contract owner. Determine whether the problem is unclear wording, missed performance or a proposed change to the agreement. Record the facts and use the applicable clarification, notice or modification route. Do not reset a contractual date or waive a right merely to reduce tension. Where a notice deadline or other duty applies, follow it promptly while collaboration continues. Fairness and accountability can operate together.

Explore the supplier case through an original fictional equipment-booking service. The buyer's interface document requires a booking identifier and an event date. A later workshop slide also shows a location code, but nobody recorded whether that slide amended the agreed interface. The supplier delivers the two documented fields. The integration team expects three and cannot complete its test. A senior manager calls the supplier late and asks the project manager to impose a penalty immediately. Before responding, identify the uncertainty that matters: which interface was actually agreed, through what authority, and for which delivery?

Begin with the controlling agreement and its incorporated documents, not with whichever file was edited most recently. A later date does not automatically make a slide authoritative. Compare the supplier's acknowledged version, the acceptance criteria, the workshop record and the change history. Involve the contract owner and the technical owners who can interpret the evidence. This is a focused investigation of a specific disputed obligation, not a reason to reopen every procurement decision. Record the unresolved difference so schedule reporting does not disguise it as ordinary progress.

Keep two workstreams distinct while the evidence is checked. The integration team can assess a permitted temporary test adapter and the impact on dependent work. The contract owner can protect any applicable notice or response requirements. In this fictional agreement, disputed delivery notices must be sent within five business days, and the contract owner is the authorized sender. A collaborative meeting does not suspend that requirement. Inform the owner promptly rather than allowing the team to spend the entire window discussing technical solutions. Maintaining a relationship and preserving contractual rights are not mutually exclusive.

Suppose the signed change record confirms that the location code was added, and the supplier acknowledged the revised date. The problem is now an unmet existing obligation, not a new buyer request. Work through the agreed remedy and decision process while assessing recovery options. Suppose instead that the workshop merely explored a future enhancement and no commitment was made. The extra field is a proposed addition whose cost, schedule and acceptance effects need an authorized decision. The same failed test can sit behind two materially different commercial situations.

A third branch is genuinely inconclusive evidence. The project manager should not invent agreement simply to produce a confident status report. State what the records establish, what remains disputed, who is resolving it and when the next decision is needed. A temporary technical workaround may reduce delay, but its approval must specify what it does and does not settle. For example, accepting test data through an adapter need not mean accepting the final contractual deliverable. That distinction should be explicit rather than assumed after the work is complete.

When debriefing this case, explain why each shortcut is weak. Immediate blame assumes the obligation has already been established. Quietly adding the field may concede a disputed change without authority. Waiting for perfect certainty while a notice deadline expires can sacrifice an available option. The stronger response combines targeted evidence gathering, competent authority and timely protection of the project's position. It does not promise that every dispute can be resolved informally or that every disagreement should become a formal claim.

At the midpoint, note which fact determined your response in each case. In the adaptive example, it was the goal and decision rights; in the adoption example, it was the obstacle to the outcome; in the supplier example, it was the agreement and evidence. The remaining cases concern a severe test defect, a changed obligation and incentive fees. Keep the practice pace flexible enough to understand the evidence. Speed is useful only when you are answering the actual question.

The fourth situation is a severe defect found during user acceptance testing shortly before a planned launch. Determine the defect's effect on acceptance and release conditions with the appropriate owners. A close launch date does not automatically justify an emergency change route. The next step depends on whether there is current harm, an unmet release condition or an approved correction that is ready to execute.

Assess the severity and the release criteria with the technical and operating owners. A defect found in user acceptance testing shortly before launch does not automatically qualify for an emergency production-change procedure. Use that procedure only if its defined trigger and authority apply. Otherwise use the established defect and release path, including a hold if the acceptance conditions are not met. A rollback plan reduces some exposure but does not prove a fix is safe. Obtain and record the required decision, validate the result and communicate promptly.

Extend the release case with a fictional room-reservation application that is still in acceptance testing. The launch announcement is scheduled for tomorrow, but a test reveals that one recurring reservation can overwrite another customer's booking. The defect affects a required acceptance condition. No live customer data has yet been exposed. The communications deadline creates pressure, but it does not turn the test failure into an operational emergency by itself. Identify the acceptance and release authorities before selecting the next action.

The immediate decision is whether the current build meets the release conditions. Confirm the defect, its affected scope and the reliability of the test evidence with the relevant owners. If the mandatory condition is unmet, do not represent the release as ready. Consider a repair and retest, an authorized narrower release that genuinely excludes the affected capability, or a delay. A narrower release is not a label placed on the same unsafe function. Dependencies, user access and the ability to reach the excluded function must all be considered.

Now change one fact: the defect is discovered after deployment and is actively overwriting real bookings. The priority shifts to the applicable incident and protective response. The operational owner may have delegated authority to suspend the affected function while the project team supplies technical evidence. A normal committee timetable should not delay a required protective action. Nevertheless, the response must still follow the actual emergency authority and record what happened. An urgent situation does not give every participant unlimited permission to alter production.

Reversal also requires judgment. Reinstalling the previous application might stop new corruption but leave altered records in place. It might also be incompatible with a database conversion already completed. Ask what state will be restored, what records need reconciliation and who can verify the result. A tested recovery procedure with clear ownership is stronger than the phrase roll back. Where the safe response is not yet known, restrict exposure through the authorized route while qualified people evaluate options.

For a timed answer, name the decision-changing condition first. Before launch, the issue concerns demonstrated acceptance and an authorized release decision. During active harm, the applicable protective response becomes urgent. After containment, reconciliation, communication and corrective learning remain necessary. These are connected responsibilities, but the question's timing determines which belongs first. A good explanation should make clear why the selected action fits the present state instead of merely repeating that quality matters.

The fifth scenario is a regulatory shift. Just before release, a new privacy rule is announced that changes data retention obligations. To complicate matters, a vendor manages part of the storage pipeline. This situation blends compliance, contracts, and cadence. The artifacts to consult are the compliance register, the contract terms, and the training plan. Record the announcement and obtain a qualified assessment of its applicability and effective date. Review the supplier agreement and any operating or training changes that follow from that assessment. If a confirmed obligation applies before renewal, a renewal date does not postpone the duty. Verify readiness rather than treating a training plan as proof of understanding.

Have the qualified legal and compliance owners establish applicability, effective timing and affected work before treating the announcement as a release condition. If it applies, compare the feasible implementation and supplier responses through the authorized owners. A smaller release may work if it meets all relevant conditions; a pause may be necessary if it does not. Modify the agreement only through the applicable authority. A deadline does not make a noncompliant slice acceptable, and a contract amendment alone does not prove the operating process meets the requirement.

The sixth situation concerns rising costs under a cost-plus-incentive-fee contract. Consult the actual agreement, current cost evidence and the responsible commercial owners before deciding how the incentive and any other conditions apply. Do not assume that the contract label alone determines a fee, a remedy or a right to terminate. The managerial response should address the cause, remaining forecast and available authorized options.

Apply the incentive calculation that the actual agreement specifies, including any minimum, maximum or other relevant condition, with the authorized procurement and finance owners. Analyze the cause of the overrun and compare a feasible corrective response. Update the cost forecast honestly. Do not increase the approved baseline solely to erase the variance; a change to that commitment requires the proper decision. A fee adjustment under an existing clause also differs from negotiating a new contract term. Keep those distinctions visible in the report.

Work the incentive question using an original fictional cost-plus-incentive-fee arrangement. Assume a target allowable cost of two hundred thousand dollars, a target fee of twenty thousand dollars, and a seller share of twenty percent of the difference between target and actual allowable cost. The fee cannot fall below ten thousand dollars or rise above thirty thousand dollars. All figures here are teaching assumptions, not terms that can be presumed in another contract. Funding limits, cost allowability and any other applicable clauses still have to be checked.

First suppose actual allowable cost is two hundred thirty thousand dollars. That is thirty thousand above target. Twenty percent of the overrun is six thousand, so the fee falls from twenty thousand to fourteen thousand dollars. Fourteen thousand is inside the agreed fee range. Adding it to the assumed allowable cost gives a calculated total of two hundred forty-four thousand dollars. The calculation describes the stated incentive mechanism; it does not authorize additional spending or establish that an invoice has satisfied every payment condition.

Next suppose actual allowable cost is one hundred fifty thousand dollars. The saving against target is fifty thousand. The seller's twenty percent share adds ten thousand to the target fee, reaching the thirty thousand dollar maximum. The calculated cost-plus-fee total is therefore one hundred eighty thousand dollars. A learner who subtracts the saving from the fee has reversed the incentive. A learner who pays the entire saving as additional fee has ignored the agreed sharing proportion.

Now test the lower limit. At an actual allowable cost of two hundred sixty thousand dollars, the overrun is sixty thousand. Twenty percent is twelve thousand, which would reduce the twenty thousand dollar target fee to eight thousand before applying the limit. The minimum fee changes that result to ten thousand, producing a calculated total of two hundred seventy thousand dollars under these assumptions. The minimum applies to the fee, not to a guarantee that every claimed cost is reimbursable. Keep those concepts separate when interpreting a scenario.

This example also distinguishes a fee ceiling from a fixed total-price ceiling. A maximum fee of thirty thousand dollars does not mean the buyer's total exposure is thirty thousand. Nor does the formula imply unlimited permission to incur costs. A contract can contain other funding, notification, approval and payment conditions that must be applied alongside the fee calculation. The project manager should work with the authorized commercial and financial owners to understand the actual arrangement rather than substituting a remembered label for its terms.

The management decision goes beyond arithmetic. Ask why costs have changed, whether the estimate includes all remaining work, whether the output still supports the business case and what response is within current authority. Applying an existing incentive clause is different from negotiating a new target or changing the sharing ratio. The former follows the agreement; the latter requires the appropriate contractual action. Updating a forecast to reflect likely cost is also different from revising an approved baseline to hide an unfavorable variance.

For a final decision branch, assume the calculated fee is correct but the supplier's claimed cost includes an unsupported charge. The arithmetic does not resolve the evidence gap. Route the charge through the applicable review, preserve the undisputed calculations and avoid asserting a final payable amount prematurely. Your answer should separate mathematical correctness, contractual entitlement, spending authority and the management response. These distinctions make the exercise useful beyond a single formula question.

These three cases depend on different triggers. A severe test defect requires a valid release decision and may or may not meet an emergency procedure's trigger. A newly announced obligation needs an applicability assessment before its effect is planned. An incentive-fee question needs the actual agreement and arithmetic rather than a guessed formula. Each calls for an honest forecast of the consequences. Do not choose a familiar process name before checking that the situation meets its conditions.

Across the six cases, ask whether the response uses authority that exists, evidence that is reliable and assumptions that are stated. An equal-weight backlog swap, a training session, a contract meeting or an action log can all look reasonable. None is sufficient by its label alone. Explain what obstacle it resolves and what remains to be verified. That is how a worked scenario becomes a reusable lesson rather than a memorized phrase.

Use confidence to guide review, not to replace correctness. A sound answer chosen with uncertainty identifies material worth revisiting. A confident but unsupported answer deserves particular attention because it may reveal a habitual assumption. Tag the issue by the concept involved and return to the relevant explanation. Review the reason after practice, then try a different scenario. The goal is more reliable judgment rather than a confidence score alone.

Short timed practice can help you notice when pressure makes you skip a condition. Vary the time allowed with the complexity of the evidence and leave detailed review for afterward. A brief professional response should identify the condition, the decision needed and the responsible owner. It should not claim that a register itself orders a particular release. Useful composure comes from a clear understanding of the situation, not from repeating a process phrase quickly.

Compare the alternatives in these fictional situations by the assumptions each one requires. A response that assigns fault without establishing the obligation, accepts a release without meeting its conditions or calculates a fee without applying its limits is missing a decisive step. That does not mean analysis must continue indefinitely. When the facts and authority are established, choose the supported action and carry it through.

Finish this practice set by comparing your explanation with the evidence actually supplied. For the supplier case, underline the document and authority that establish the obligation. For the release case, identify whether the system is in testing or is causing current harm. For the incentive case, state the sharing rule and both fee limits before calculating. These are different forms of disciplined reading, not one universal checklist that replaces judgment.

During a second attempt, change only one decisive fact in each case and answer again. Make the interface requirement formally approved, move the defect from testing into live operation, or change the allowable cost enough to reach a fee limit. Explain why your response changes or remains the same. The objective is not to deliver the same rehearsed sentence more quickly. It is to detect the boundary that separates two plausible actions and select the one supported by the revised facts.

A final variation concerns the time available for a decision. Suppose the supplier's notice deadline is today but the technical analysis will take two days. The owner can send an accurate notice describing the confirmed issue and the pending investigation, provided that approach satisfies the applicable agreement. There is no need to pretend the investigation is complete. Conversely, the project manager should not send a binding concession merely because the owner is busy. Timing pressure changes the coordination need, not the identity of the authorized decision maker.

In your debrief, distinguish an interim communication from a final disposition. The first can preserve visibility and explain what is being investigated; the second may settle rights, cost or acceptance. Record which kind the scenario asks for. Confusing them can make a sensible notification seem premature or make an unauthorized commitment seem like harmless housekeeping.

Return to the chapters that explain any decision you could not justify. Chapter twenty-five supports supplier reasoning, chapter thirty-four supports release and transition decisions, and chapter forty-three supports responses to external change. Use episode one hundred two for deeper adoption work. These practice situations are invented teaching tools, and their pace and distribution are not an official exam specification. Carry forward the habit of explaining the decisive fact and the limit of your authority.

For more certification study resources, books, and podcasts, visit Bare Metal Cyber dot com. Thank you for listening to Certified, the P M P prepcast.

PMP 2026 | 84 | Scenario Lab: Timed Situations, Set Two
Broadcast by