PMP 2026 | 83 | Scenario Lab: Timed Situations, Set One

Put your project judgment to work in six fictional situations covering late scope requests, interface performance risk, approval records, supplier substitutions, benefits, and schedule compression. This first timed practice set invites you to pause, choose an action, and explain…

This listening lab uses original fictional situations, not a full-length examination or a reproduction of official questions. At a safe opportunity, give yourself a practice budget of about sixty to seventy-five seconds for an initial decision, then use the extended discussion to examine the reasoning. That is a training choice, not a required pace for every item on the current exam. Identify the decision, evidence and authority, including any immediate harm or mandatory obligation. Mark uncertainty for later review.

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

Scenario one combines people and process tensions. A very important stakeholder demands a “tiny” user interface tweak just five days before user acceptance testing. The team lead protests, morale is already strained, and the clock is ticking. You may feel the pull to satisfy the stakeholder, but doing so without analysis undermines both governance and team trust. The options illustrate possible mistakes: approve immediately to appease, refer a decision without checking its owner and urgency, or tell the team to absorb extra work without a feasible plan. The artifact to consult is the acceptance criteria linked through the traceability matrix. The professional move is to facilitate alignment, run a quick impact analysis, and route the request through the change path.

For this ordinary scope request, clarify the acceptance criteria and assess the impact with the people doing and accepting the work. Use the established change route for any affected commitment and record the outcome. Do not promise that a tired team will simply absorb additional effort. If the decision exceeds delegated authority, bring the appropriate owner a clear choice promptly. Facilitation supports the decision; it does not require the project manager to keep a sponsor-owned decision away from the sponsor.

Extend the first decision with a fictional ticket-reporting project. The customer requests a filter showing reservations by event date. The delivery lead calls it a new feature, but the approved acceptance example already requires staff to retrieve reservations for a selected date. Testing has demonstrated only an unfiltered list. The question is what the project manager should do next, not whether the customer is being demanding. Pause at a safe opportunity and identify the fact that distinguishes a new request from a possible failure to meet an existing commitment.

The decisive evidence is the agreed acceptance example and what has actually been demonstrated. Review the discrepancy with the delivery and acceptance owners. Do not automatically classify the filter as added scope simply because the user describes it as a request. The existing requirement may already include the needed capability, although the exact implementation is still a technical choice. Equally, do not announce fault or a remedy before establishing that the example is current and applies to this release. The next action is a focused clarification of the commitment and evidence.

Compare two tempting responses. Immediately approving a change request could charge the customer or consume contingency for work already owed. Immediately ordering the developer to add a filter could prescribe a solution without understanding its effect or the relevant authority. A stronger response establishes the requirement, assesses the delivery gap and uses the appropriate route for correction or a genuine change. The distinction is not paperwork versus action. It is choosing the action that addresses the right problem.

Now change the evidence. The approved release explicitly excludes date filtering, and the customer accepts that exclusion but has discovered a new operational need. The request is now a proposed addition rather than a missing agreed capability. Assess its value and effect, then follow the applicable decision route. Notice that almost all the surrounding story can stay the same while one authoritative fact changes the answer. In timed practice, finding that fact is more useful than recognizing a familiar scenario title.

Change the authority instead. Suppose the requested addition is within a documented delegation, affects no external commitment and has already been assessed as feasible. Sending it to a committee that has no decision to make may add delay rather than improve governance. The project manager can act within the actual delegation and record the outcome. If the request crosses a funding, contractual or acceptance boundary, another owner may be needed. The word change does not itself determine who must approve it.

For your debrief, state the decision boundary in plain language. An existing unmet requirement needs an appropriate delivery response; a new requirement needs an authorized scope decision; an unclear record needs clarification. Then identify the evidence that would separate those states. This is not a universal three-step ritual for every problem. It is a way to prevent a quick answer from quietly assuming the most important fact in the question.

A third-party interface may throttle requests, and the planned launch date is approaching. Quality specialists warn that the resulting performance could be unacceptable. Ask what evidence would establish the actual limit, which requirement it affects and who owns the response. Extra working hours do not themselves remove a supplier's technical limit. Technical testing and contractual review may proceed together when both are relevant. Avoid assuming either that the rumor is proven or that only one response can work.

A focused investigation can test the throttling concern and compare feasible responses. Caching is one possible candidate when data freshness, privacy and consistency requirements permit it, but the technical owners should evaluate the design. Record the risk, owner, assumptions and remaining uncertainty. Assess schedule effects and seek any required change decision. A short experiment can reduce uncertainty; it cannot prove that no future failure will occur. Keep that distinction in the explanation you would give the sponsor.

A more demanding variation supplies the evidence that the earlier interface case lacked. In this fictional test, requests arrive steadily at one hundred twenty per minute while the supplier accepts only one hundred per minute. Assume no batching, retries, rejection or other processing path, and an empty queue at the start. Twenty requests accumulate each minute, so after ten minutes the queue contains two hundred waiting requests. This simple model demonstrates sustained overload under its assumptions. It does not establish what happens in every real interface, where arrival patterns and error handling may differ.

The technical owners have already verified that a permitted batching option can meet the requirement, and the authorized contract owner has confirmed that it fits the agreement. The tested option also remains within the team's existing implementation authority. The question now asks what should happen next. Ordering another generic risk-identification workshop would repeat work without addressing the current decision. Implementing the authorized response with the required verification and monitoring is more appropriate than indefinitely collecting evidence that the case says is already sufficient.

Change one fact: the batching option delays a time-sensitive update beyond the accepted limit. It is no longer an acceptable response merely because it reduces the queue. The owners must compare another feasible option, seek an authorized change to a changeable commitment or recommend the appropriate release decision. Do not silently relax the freshness requirement to make the technical model pass. The same queue calculation can support different decisions depending on the service conditions.

For your timed explanation, name both the evidence state and the authority state. The original case needed investigation because the limit and response were uncertain. The first variation supports action because the relevant assessment and authorization are complete. The second variation has a failed requirement that still needs resolution. This exercise tests whether you recognize progress through a decision rather than restarting at the first step every time a question mentions risk. Good judgment includes knowing when to stop analyzing and carry out a valid decision.

In the third fictional case, the organization's release procedure requires an identifiable authorized approval. An auditor asks for the last release records, and the team has found only informal messages whose meaning is unclear. Determine whether an approval actually occurred and whether authentic supporting evidence exists. Do not assume that a screenshot is always sufficient or always invalid. Check the authority, content and applicable record requirements. A missing formal log and a missing decision are related but different problems.

Reconcile the available authentic records with the deployed changes and report any unresolved gap honestly. If the approval occurred, link the genuine evidence without altering its date or meaning. If it did not, do not manufacture it after the fact. Assess the affected work and use the corrective-action and release process required by the organization. A new action record does not automatically permit the next release. The authorized owner must decide using the actual conditions, including whether a hold is required.

Extend the approval-evidence case with a fictional inventory application. The deployment completed at midday. A record entered in the afternoon says that approval was granted earlier, but the named approver was absent and no other evidence has yet been located. A manager asks the project team to accept the note because the release appears to work. The question is whether apparent technical success establishes authorization. Pause and separate the two conclusions before choosing an action.

The note is a claim about an earlier decision, not proof by itself that the required authorization existed. Preserve it as received and seek authentic evidence through the appropriate owners. Check whether a delegated approver was authorized at the time, whether the record identifies the actual deployed change and whether the stated policy accepts the evidence offered. Do not change the timestamp or create a new signature that appears contemporaneous. The review must preserve what is known and what cannot be established.

There are two important branches. If a valid delegate did authorize the exact change before deployment and an authentic record is recovered, the issue may be incomplete filing. If no valid approval occurred, the issue is an unauthorized change requiring the organization's applicable assessment and response. A current decision about keeping or altering the deployed system is possible, but it should be recorded as current. These branches can lead to different corrective actions even when users observed the same apparently successful release.

Avoid assuming that a missing record always requires an immediate blind rollback. The technical and operating owners need to assess current exposure and the consequences of reversal. If there is immediate harm, use the applicable protective route promptly. If the system is stable and no urgent condition is established, an evidence review and authorized disposition may be appropriate. The scenario must supply the facts that justify urgency. Neither automatic reversal nor automatic acceptance follows from the missing link alone.

A second distractor is to open a corrective-action ticket and then declare the next release cleared. The ticket assigns work; it does not complete the work or supply missing authority. Ask what condition must be satisfied, who evaluates it and what evidence would demonstrate completion. The release owner needs that result before applying the actual release policy. This is a common reasoning distinction across many domains: a plan to correct a problem is not evidence that the problem has already been corrected.

When you review your answer, identify the conclusion each record can support. A deployment log can identify the implementation event. A test result can support a defined quality conclusion. An authorization record can support a decision within the signer's authority. The project needs the relevant relationship among those records, not a pile of individually reassuring labels. Your explanation should show that relationship without inventing a legal requirement or technical failure the case did not state.

Before the next scenario, review the reason for your choices rather than just the time spent. Did you identify a missing fact, an authority boundary or a release condition? Did you import a rule that the case did not give you? The next three situations turn to a supplier request, benefits and schedule pressure. Keep using the evidence appropriate to each decision. If you are listening while driving or doing another task, save the timed exercise for a safe opportunity.

For the fourth fictional scenario, a supplier asks to replace a specified component with a cheaper model. The proposed substitute appears to perform the same basic function, but its support period is shorter and the interface evidence is incomplete. The supplier says the saving means no change approval is necessary. Identify what must be reviewed before the project accepts that claim. The purchase price is only one part of the decision. Consider the requirements, lifecycle support, test evidence and the contract's change route.

Have the technical, operating and contract owners compare the proposed substitute with the actual requirements and agreement. Ask for missing interface and support evidence, and assess the remaining cost and risk. The authorized owner can then decide whether a modification is acceptable. Do not approve solely because the component is cheaper, and do not reject a useful option without evaluation. Update the relevant records after the decision. A supplier's no-impact description is a claim to assess, not an approval.

The fifth scenario concerns an internal service portal. Delivery is complete, but the benefit owner reports that eligible staff rarely finish the process through the portal. A sponsor proposes buying more features immediately. Usage logs show that many users abandon the process at a step requiring access they do not have. What evidence and ownership should guide the next move? Do not confuse a delivered feature count with the business outcome the portal was intended to support.

Work with the operating and benefit owners to verify the access problem, understand the affected users and compare feasible remedies. An access correction and a measured trial may be more useful than extra features, but confirm that the permitted access arrangement is appropriate. Establish a baseline for completed eligible transactions and observe the result after the authorized change. Update the benefit forecast honestly. The former project team should support this work only under the agreed transition or a new assignment; ownership does not disappear after handover.

The portal case can also test whether you use the right denominator. In a fictional service trial, two hundred fifty employees are eligible to complete a required transaction during the month. Two hundred activate an account, one hundred fifty finish the transaction and fifty of those completions require staff assistance. The sponsor reports eighty-percent adoption because two hundred of two hundred fifty activated. That is an accurate activation rate, but it is not the self-service completion outcome the trial was intended to measure.

The completed-transaction rate among eligible employees is sixty percent. Unassisted completions total one hundred, producing a forty-percent self-service completion rate among the eligible group. These are straightforward calculations, but the decision depends on their meaning. A report can use a mathematically correct percentage and still misrepresent the promised benefit. The next action is to align the reported measure with the agreed outcome and investigate the gap with the accountable owners, not to celebrate or condemn the service from one number alone.

Suppose the abandoned transactions cluster at an access check. The project manager should not direct administrators to bypass the check merely to improve adoption. Establish whether the intended users should have access, whether the approved access process is working and which owner can authorize a correction. A compliant remedy might improve completion, but the result must be measured. If access is intentionally restricted for a valid reason, the service design or target population may need reconsideration rather than a blanket access grant.

Now suppose access is working and users abandon because the process takes longer than the existing alternative. Training might help if users misunderstand a shortcut, but it may also fail to address an inconvenient design. Observation and user feedback can reveal whether the service is solving the intended problem. The benefit owner should compare feasible improvements and their likely effect before authorizing new features. A feature purchase is not automatically a benefit response just because it is visible and easy to announce.

A further variation changes the reporting period. Some employees became eligible only in the final two days of the month and could not reasonably complete the process within that window. The definition of the reporting population and completion window now matters. The responsible owners should establish a fair, consistent method rather than exclude inconvenient cases after seeing the result. Keep the original and revised definitions visible if the method changes. That prevents a better-looking percentage from masquerading as an improved service.

For the timed answer, focus on the immediate decision: establish a truthful outcome measure and investigate the observed barrier with the proper owner. For the debrief, explain what evidence would support an access correction, training, workflow redesign or a revised benefit forecast. Those are different interventions, not interchangeable positive-sounding options. A sound response keeps the organization accountable for the outcome without pretending that one experiment will guarantee adoption.

The final fictional scenario has two parallel paths joining at a release milestone. One takes twenty days and the other takes eighteen. The sponsor asks whether shortening the first path by four days will finish the release four days earlier. Assume for this exercise that the paths have no shared resource constraint and all other dependencies remain unchanged. Pause and calculate the new finish. Then explain which path controls the result and what additional fact could change your conclusion.

The first path becomes sixteen days, but the second still takes eighteen. The release therefore finishes in eighteen days, a gain of two days rather than four. The second path is now controlling. To pursue further acceleration, examine that path, the feasible activity changes, their costs and any resulting risks. A shared specialist or another constraint would require a revised model. The key is to recompute the whole network rather than subtract an activity saving directly from the project finish.

Extend the schedule case by adding a common two-day verification activity after the two parallel paths. With paths of twenty and eighteen days, the original finish is now twenty-two days. Shortening the first path to sixteen leaves the eighteen-day path controlling, followed by the same two-day verification. The new finish is twenty days, still only two days earlier. The common activity changes the absolute finish but not the saving from this particular compression. State that dependency explicitly before calculating.

Suppose a different proposal shortens the common verification activity by one day. It would reduce the finish by one day if the revised duration is genuinely feasible and all other conditions remain unchanged. But a promised reduction achieved by omitting required checks is not a valid schedule option. The technical and acceptance owners must establish whether the shorter duration reflects efficiency, added qualified capacity or an unacceptable loss of evidence. A number on a schedule does not settle that question.

Resource sharing creates another variation. If the same specialist must perform overlapping work on both branches, their apparent parallel durations may not be achievable. The model must account for the actual assignments and calendar. Do not add an imagined resource conflict to the original exercise, which explicitly excluded one, but recognize that the changed exercise requires reconsideration. Reading the stated assumptions is part of the calculation. Solving a more complicated problem than the one given can be just as wrong as ignoring a stated constraint.

A practical time-budget exercise can help you notice this tendency. For an optional ten-scenario practice block, allow thirteen minutes of active answering and two minutes of review, for fifteen minutes total. Thirteen minutes is seven hundred eighty seconds, averaging seventy-eight seconds per scenario. That average is a training design, not a prescribed official-exam pace. A short item can take less and an evidence-heavy one more. During later review, compare time spent with reasoning quality rather than trying to make every answer fit the same stopwatch interval.

If the first six practice scenarios consume eight minutes, five minutes of active answering time remain for the last four before the planned review. That is an average of seventy-five seconds per remaining scenario. The calculation helps you recognize the state of your practice block without panicking. It does not justify skipping the decisive condition or selecting an answer solely because it is short. Use the remaining time to reduce unnecessary rereading, not to abandon evidence-based judgment.

Finally, separate your initial choice from your explanation after hearing the debrief. Record what you actually thought, the fact you missed and what would help you notice it next time. Otherwise, the correct explanation may feel obvious in hindsight and hide the learning gap. The purpose of timing is to expose how reasoning changes under pressure. It is not to create an unofficial passing score or to turn these original teaching scenarios into a claim about the difficulty of the real examination.

You have considered six core decisions and their extended variations. Review any answer chosen only because it contained familiar words such as analyze, approve or escalate. Ask what the action would accomplish and which stated fact supports it. Revisit the relevant record, calculation or authority boundary when your reasoning was uncertain. A brief explanation of the decisive fact is more useful than memorizing a label or an answer letter.

The useful pattern across this set is conditional judgment. An ordinary scope request needs a supported commitment decision. A technical risk needs investigation and a feasible response. Missing authorization evidence needs an honest review. Procurement needs requirements and contract authority, benefits need a measured outcome and an owner, and schedule acceleration needs a valid model. Those are distinct reasons. Treating them as one automatic first step would miss the point of the practice.

For further practice, connect this lesson with the project-records lab in episode one hundred six. Write one sentence explaining the decisive fact in each scenario and another explaining when a different response would be justified. Use your notes to choose the chapter that needs review. This exercise strengthens reasoning across topics while preserving the limits of the evidence. It is a study tool, not a prediction of your official exam result.

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 | 83 | Scenario Lab: Timed Situations, Set One
Broadcast by