Hard Difficulty Questions

Project Sponsor

Why it fails: The sponsor provides resources but does not manage daily priority changes.

Development Team

Why it fails: The team implements changes but does not manage priorities.

Steering Committee

Why it fails: Steering committee provides governance but not daily priority decisions.

Norming

Why it fails: Norming follows storming, when conflicts are resolved and cohesion and agreed working norms emerge; active conflict and questioning of authority precede it. Norming would be correct once the team has reconciled differences and accepts the project manager's role.

Performing

Why it fails: Performing is the mature stage with shared goals, autonomy and constructive disagreement; overt conflict and challenges to the project manager's authority indicate storming. Performing would be correct once the team works productively with settled norms and minimal supervision.

Forming

Why it fails: Forming is orientation, where members depend on the leader and avoid conflict; open questioning of authority and interpersonal clashes belong to storming. Forming would fit a newly assembled team still learning roles and objectives, before disagreements surface.

Overhead costs

Why it fails: Overhead costs such as rent, utilities and administrative salaries are indirect: they cannot be attributed to a single project deliverable. Direct costs, like labour billed to the project or dedicated materials, trace to specific work. Overhead is tempting because projects do incur it, but it is shared across the organisation.

Training costs

Why it fails: Training is a recurring operational expense, not a direct project cost tied to a specific deliverable, so it fails the direct-cost criterion. It tempts because training often appears in project budgets, and it would qualify as an indirect or overhead cost when allocated across multiple projects rather than charged to one.

The project is over budget and behind schedule.

Why it fails: CPI of 1.2 means earned value exceeds actual cost, so the project is under budget, not over. The schedule half is correct. It is tempting because SPI below 1.0 does indicate behind schedule, so the accurate second clause lends false credibility to the inverted cost claim.

The project is over budget and ahead of schedule.

Why it fails: CPI of 1.2 means earned value exceeds actual cost, so the project is under budget, not over. The option inverts the cost index. It is tempting when a learner reads any index above 1.0 as unfavourable, but CPI and SPI both measure favourability above 1.0, making this pairing internally inconsistent.

The project is under budget and ahead of schedule.

Why it fails: SPI of 0.9 means earned value lags planned value, so the project is behind schedule, not ahead. The cost half is right, the schedule half is inverted. It is tempting because CPI above 1.0 genuinely signals under budget, so half the statement reads correctly and masks the schedule error.

The control limits need adjustment

Why it fails: Control limits derive from process data and are not recalculated merely because points cluster on one side of the mean; a seven-point run signals an assignable cause. Limits would be revisited only when the process itself changes, such as after a documented improvement or new equipment.

Common cause variation only

Why it fails: Common cause variation describes random dispersion within the limits with no pattern; a seven-point run above the mean is a non-random signal indicating special cause variation. This option would be correct if the points were scattered evenly around the mean without any sustained shift.

The process is out of control

Why it fails: While not out of control in terms of limits, the run indicates special cause variation that needs investigation.

15 days

Why it fails: Fifteen days is the early finish value, not the float; total float is late finish minus early finish (20 − 15 = 5). It is tempting because early finish is a prominent schedule figure and subtracting early start from it gives the activity duration.

20 days

Why it fails: Twenty days equals late finish, not float; total float is late start minus early start (10 − 5 = 5) or late finish minus early finish (20 − 15 = 5). It is tempting because late finish is the largest date in the activity's schedule data.

10 days

Why it fails: Ten days is the late start value, not the float; total float is late start minus early start (10 − 5 = 5). It is tempting because the late dates differ from the early dates by five days, and ten is the first late date encountered.

Ignore

Why it fails: Ignore is not a recognized response strategy.

Enhance

Why it fails: Enhance is for positive risks (opportunities).

Increase the project scope to justify the shorter timeline.

Why it fails: Increasing scope would extend the schedule, not shorten it.

Reduce the quality standards to speed up work.

Why it fails: Reducing quality is not acceptable and may cause rework.

R3 - Technical failure

Why it fails: Though impact is high, probability is low, and it's accepted.

R4 - Scope creep

Why it fails: It is being avoided, which may reduce priority compared to active risks.

R2 - Resource shortage

Why it fails: R2 scores 0.30, below R1's 0.48 and R3's 0.36, so it ranks third rather than first. Expected monetary value multiplication is the axis here. Resource shortage monitoring suits staffing plans where labour availability drives the schedule, but this register's probabilities and impacts place it behind higher-scoring risks.

$110,000

Why it fails: $110,000 misapplies the EAC formula by dividing BAC by CPI incorrectly or using a non-continuing assumption. With CPI of 0.8, EAC = BAC ÷ CPI = $100,000 ÷ 0.8 = $125,000. This figure would suit a scenario where remaining work proceeds at the original budgeted rate, using EAC = AC + (BAC − EV).

$75,000

Why it fails: This value resembles a rough estimate combining actual cost with remaining budget, but the continuing-performance EAC is BAC divided by CPI, which equals 125000. The mistake is dividing earned value by budget or otherwise misapplying the formula; 75000 would only arise under a different assumption about future cost performance.

$90,000

Why it fails: This applies the EAC formula BAC divided by CPI, but CPI here is 40000/50000, or 0.8, giving 125000, not 90000. The figure appears plausible because it sits between actual cost and budget, yet it corresponds to no standard earned value formula for a continuing cost performance trend.

Add more developers to critical path tasks to catch up on schedule

Why it fails: Adding more developers (crashing) increases cost, which is problematic given the project is already over budget (CPI 0.71). This is not the best option.

Reduce the project scope to align with the current progress

Why it fails: Reducing scope requires formal change control and may not be acceptable to the sponsor or stakeholders.

Replace senior developers with junior ones to reduce cost

Why it fails: Replacing senior developers with juniors would likely reduce quality and slow progress further, worsening both schedule and cost.

Fast-tracking; increases cost

Why it fails: Fast-tracking overlaps activities instead of adding resources, so it fails the stem's resource-adding description, and its trade-off is rework risk rather than cost. It is tempting because both are compression techniques, but fast-tracking suits schedule reduction when budget is fixed and parallel work is feasible.

Crashing; increases risk

Why it fails: Crashing adds resources to critical path activities, matching the stem, but its primary trade-off is increased cost, not increased risk. It is tempting because risk does rise secondarily, yet the defining consequence of buying duration with additional labour or equipment is the added expenditure.

Fast-tracking; increases risk

Why it fails: Fast-tracking overlaps activities rather than adding resources, so it does not match the stem's resource-adding technique. It is tempting because it is a genuine schedule compression method whose trade-off is increased risk from parallel work, making it the correct choice when duration must shrink without extra budget.

The team member has missing email configuration

Why it fails: Missing email configuration would prevent receiving any emails, not just project emails.

The team member is not listed in the project directory

Why it fails: Being in the project directory ensures portal access, but email groups are separate.

The email server firewall is blocking messages

Why it fails: Firewall blocking would affect all emails, not just project emails.

1 day

Why it fails: Total float for task C is 2 days, not 1 day. This value is calculated using forward/backward pass on the network diagram.

0 days

Why it fails: Task C has total float of 2 days, so it is not on the critical path. Zero float would indicate it is on the critical path, which is not the case here.

3 days

Why it fails: Total float for task C is 2 days, not 3 days. The calculated float is based on the difference between late start and early start.

Team member salaries

Why it fails: Team member salaries belong to HR or finance records, not the communication plan, which specifies what information is shared, with whom, when, and through which channel. It is tempting because personnel data can inform stakeholder analysis, and salary bands would be relevant when building a resourcing or budget plan rather than a communications matrix.

Personal contact information for all stakeholders

Why it fails: A communication plan defines who receives what, when, how and through which channel; individual contact details belong in a stakeholder register. Contact information is appropriate for a directory or escalation list, not the plan's core elements.

Performing quality control inspections

Why it fails: Quality control inspections are performed by the quality team or testers executing the quality management plan; the sponsor approves the plan and accepts deliverables rather than inspecting them. It tempts because sponsors sign off final acceptance, which feels adjacent to inspection, but acceptance follows testing rather than replacing it.

Attending daily stand-up meetings

Why it fails: Daily stand-ups are the delivery team's coordination ceremony; the sponsor's primary duties are securing funding, resources and executive backing, and removing organisational blockers. Attending stand-ups would be correct only if the question asked who tracks daily progress against the sprint backlog.

Creating the project schedule

Why it fails: Schedule creation belongs to the project manager, who sequences activities, estimates durations and assigns resources. The sponsor authorises the charter and approves funding, so this task sits outside their remit. It tempts because sponsors often chair steering meetings and may hold scheduling authority in small organisations lacking a dedicated project manager.

$200,000

Why it fails: $200,000 simply restates the budget at completion, ignoring the cost performance index entirely. It is tempting as a baseline figure, but EAC must be recalculated when the project continues at its current CPI; with CPI of 0.833, the correct value is $240,000.

$220,000

Why it fails: $220,000 adds the $20,000 cost variance to BAC, which estimates a one-off overrun rather than continued performance at the current CPI. It is tempting because AC exceeds EV, but the stated assumption requires BAC ÷ CPI, giving $240,000.

$260,000

Why it fails: $260,000 misapplies the formula, perhaps dividing BAC by CPI differently or using PV. With CPI of 0.833, EAC is BAC ÷ CPI = $240,000. The figure is tempting because it resembles a plausible overspend projection, but it does not follow the stated current-CPI assumption.

Vendor performance

Why it fails: Vendor performance measures supplier delivery against contracts, not how a stakeholder prefers to receive project information. It is tempting because procurement reporting genuinely belongs in communications planning when external suppliers are stakeholders, yet the stem asks for per-stakeholder factors such as influence, interest, and preferred channel.

Budget constraints

Why it fails: Budget constraints are a project-level consideration, not a per-stakeholder factor; the communication plan addresses each stakeholder's information needs, influence and preferred method and frequency. It is tempting because cost shapes overall communication channels, and would be correct when selecting enterprise-wide tools rather than planning individual engagement.

Risk tolerance

Why it fails: Risk tolerance describes how much uncertainty an organisation or individual accepts, governing contingency and escalation thresholds rather than communication needs. It is tempting because risk appetite is recorded in stakeholder registers, but the communication plan requires each stakeholder's interest, influence, and preferred format, channel, and frequency.

Six Sigma

Why it fails: Six Sigma reduces process variation in stable, repeatable operations; it offers no cadence for delivering value under shifting requirements. It is tempting because its cost-saving reputation addresses the sponsor's overrun concern, but DMAIC assumes a defined process, not emergent scope.

PRINCE2

Why it fails: PRINCE2 is a stage-gated governance method with defined products and stage boundaries, so it accommodates change through formal exception and change control rather than frequent incremental delivery. It is tempting for its cost tolerance controls, but iterative adaptive delivery needs an agile approach.

Waterfall

Why it fails: Waterfall fixes scope and schedule up front, so it cannot absorb rapidly changing requirements without costly re-baselining at each phase gate. It suits projects with stable, well-understood requirements and regulatory stage approvals, where sequential delivery is acceptable.

Proceed with execution and define criteria later during closure

Why it fails: Deferring criteria to closure leaves execution without a measurable definition of done, so work cannot be verified or accepted progressively. Acceptance criteria are defined during planning, before or early in execution. Postponing them invites rework and disputed sign-off. Defining them later is only viable if the deliverable itself is genuinely deferred.

Define the acceptance criteria based on the project manager's experience

Why it fails: Acceptance criteria must be agreed with the customer and stakeholders who will accept the deliverable, not invented unilaterally. The project manager's experience cannot substitute for that agreement, and self-authored criteria create scope and sign-off disputes. Personal judgement is useful for facilitating workshops, not for setting acceptance thresholds.

Ask the project sponsor to define the acceptance criteria immediately

Why it fails: Acceptance criteria belong to the requirements and quality planning processes, where the project manager facilitates their definition with the customer and stakeholders. Delegating solely to the sponsor bypasses that ownership and may not reflect customer expectations. Sponsors typically approve scope and funding, not author deliverable acceptance criteria.