1. On a hybrid learning-platform project, an analytics module enables a campaign in six weeks and a grading module supports an accreditation pilot in eight. Both have measurable benefits and deferral risks, but dependencies allow only one this sprint. Shared weights for value, urgency, risk and dependencies are not set. What should the project manager do BEST?

1. Collect comparable value and deferral data, ask the sponsor to choose, then reorder the backlog.
2. Facilitate agreement on weights for value, urgency, risk and dependencies. The Product Owner then orders the backlog and makes the deferral visible.
3. Define the thinnest slice of both modules, split sprint capacity, then decide after the review which to finish.
4. Score both modules against release objectives, recommend the resulting order to the Product Owner, and document the rationale.

2. Mid-sprint, a compliance specialist shares a draft regulation due in six weeks. One traceability requirement may affect the architecture in development, but noncompliance is unconfirmed; the remaining requirements do not affect the Sprint Goal. What should the Product Owner do FIRST?

1. Add the requirements to the Product Backlog, analyze them at the next refinement, and leave the Sprint Backlog unchanged until then.
2. Document the possible governance impact, obtain approval to analyze the scope change, then add and triage the requirements.
3. After a quick estimate, add the architectural requirement to the Sprint Backlog, swap out a lower-risk item, and defer the rest.
4. Rapidly triage impact, urgency and risk with the specialist and team. Add the requirements to the backlog and renegotiate the sprint only if needed.

3. A logistics platform is built by 14 teams across three regulatory clusters with uneven maturity and critical cross-cluster dependencies. Executives want fewer integration delays but do not require a named framework. What should the program manager recommend next?

1. Define minimum dependency and governance interfaces, test them on a representative flow across two clusters, then evaluate before wider rollout.
2. Define minimum interfaces, test them in the most mature team, then expand after its local flow metrics improve.
3. Define minimum interfaces, deploy them to all teams, then tailor cluster mismatches after the first release.
4. Set governance requirements per cluster, let each choose its interfaces, and measure effectiveness at quarterly shared-release integration.

4. In an international construction project, design decisions are moving to private chats even though team rules require meetings. New subcontractor representatives did not create the rules, experienced members find them slow, and conflicting interpretations caused rework. Another decision is due tomorrow. What should the project manager do FIRST?

1. Record the decision visibly, then involve the full team, including new members, in tailoring decision channels, records and escalation rules.
2. Record the decision, restate the current rules at the next meeting, and tailor them jointly after the current phase.
3. Record the decision, have experienced members and the PMO draft faster rules, then ask the full team to ratify them.
4. Record the decision, begin measuring decision time and rework, then realign the rules after gathering data.

5. Six weeks before a medical-records launch, physicians fear patient-safety effects, nursing managers lack training coverage, and the union requires notice of schedule changes. The sponsor proposes an immediate campaign for all staff. What should the project manager do BEST?

1. Update role-specific messages and launch the benefits campaign before the training schedule is final.
2. Ask HR and the clinical director to finalize one training and staffing plan, then communicate the approved solution.
3. Assess readiness and impact by group, co-design communications, training and safeguards with representatives, and add adoption actions and measures to the plan.
4. Pilot with physician and nurse champions, refine deployment and communications, then involve the remaining groups.

6. A predictive network project is asked to automate three more warehouses. Full expansion adds 25% cost and six weeks, exceeding CCB thresholds. Phasing, scope swaps and extra funding preserve different benefits, but their impact data are not comparable. What should the project manager do before recommending an option to the CCB?

1. Develop phasing with the benefits owner, confirm cost and timing, then recommend it to the CCB.
2. Compare available data with the director, select a compromise, reserve resources, and send it to the CCB.
3. Compare expansion, phasing and a scope swap with the director, choose one, and record non-comparable benefits as a risk.
4. Standardize each option's value, risk, cost and schedule effects with the benefits owner, compare them with the director, then send the agreed recommendation.

7. Before an investment review, implementation cost is up 35%, forecast savings are down, and positive NPV requires adoption above 80%. Readiness is 55%, but the benefits owner believes an adoption program could raise it. What should the project manager do FIRST?

1. Update costs and savings, recommend a timeboxed adoption pilot, and defer scope and phasing analysis until results arrive.
2. Use 55% as the base case and recommend termination unless the benefits owner guarantees adoption above 80%.
3. Validate adoption assumptions, update the business case with scenarios plus feasible scope, phasing and adoption options, then recommend with risks.
4. Agree a scope-reduction and phasing option with the sponsor, seek committee approval, then complete the business case.

8. An agile clinical platform has many confirmed criteria for traceability, unintended outcomes and human review; several still need legal interpretation. Three increments have partial evidence not mapped to the criteria, and release time is limited. What should the project manager do FIRST?

1. Map evidence to confirmed criteria, prioritize remediation by risk and add a release gate, but leave the Definition of Done unchanged.
2. Separate confirmed and open criteria, assess the gap by risk, update acceptance criteria and the Definition of Done, then prioritize remediation and legal decisions.
3. Assign a specialist subgroup recurring sprint capacity for evidence mapping and remediation, then pass approved results to the delivery team.
4. Run a timeboxed spike for open interpretations, prepare remediation options, then update acceptance criteria and the Definition of Done together.

9. Cycle time has risen for three iterations. Data show excess WIP and irregular flow reviews. The team accepts both ideas but distrusts another top-down change after a failed rollout. What should the leader do BEST?

1. Select a WIP-limit test, then jointly set its value, timebox, flow measures and retention criterion.
2. Jointly deploy a WIP limit and more frequent reviews across the stream, then evaluate combined results after a timebox.
3. Facilitate a workshop, choose one practice by vote, set flow measures, then let the majority decide whether to keep it.
4. Analyze the data together, form a hypothesis, test one practice within a timebox, and decide from the measured results.

10. Three stable teams build one digital product. Outcomes are reviewed quarterly, feature scope changes with feedback, and finance requires a spending limit, escalation thresholds and a stop option. Which funding model BEST supports adaptation with control?

1. Use a rolling product budget with quarterly forecasts and thresholds, while accounting by work package each quarter.
2. Fund team capacity quarterly within limits and outcome measures, but reapprove the full business case and allocation each review.
3. Fund the stable value stream within limits and thresholds; review outcomes quarterly and reallocate by value, risk and learning.
4. Keep a base product budget and monthly limits, funding feedback-driven work from reserve after set criteria are met.

11. During a CRM retrospective, a developer again interrupts an analyst, warning that her assumption may block integration. The team agreed not to interrupt; she falls silent and others withdraw from discussion. Fifteen minutes remain. What should the facilitator do FIRST?

1. Call a break, discuss the interruption privately, then restate the rule, return the floor and address the risk later.
2. Stop the exchange, restate the rule, return the floor, visibly record the risk for immediate follow-up, and speak privately with the developer later.
3. Restate the rule but give the developer 60 seconds for the risk, then return the floor and address the behavior later.
4. Summarize both topics, move them to the parking lot, continue the agenda, then speak separately with both people.

12. Training follows production configuration plus a two-day refresh and anonymization of the training environment. That work has an owner, uses resources and produces approved evidence, but the schedule models it only as a two-day FS lag. How should the schedule be improved?

1. Keep the two-day FS lag, describe the infrastructure work in a dependency note, and control it outside the network diagram.
2. Add an environment-readiness milestone two days after configuration, link it FS to training, and track milestone approval.
3. Add a separate two-day refresh and anonymization activity with resources, link it FS to configuration and training, and track its deliverable.
4. Add the two-day activity with resources, sequencing it with training through resource leveling without a logical link.