Five short situations. For each, a recommended next action and why — not a timed paper, not a score, and not a promise about any exam. Use them to test the habit: domain, constraint, tried-already, next verb.
Scenario 1 — The date is locked, the backlog is not
A sponsor has committed a launch date to the market. The product team works in two-week increments and is still discovering scope. A PMO lead wants the team to produce a full predictive schedule 'so we can be sure.' The contract with a hardware vendor is already fixed. Engineering says a complete task list would be fiction.
Recommended next action: tailor on purpose. Treat the date and the vendor interface as predictive constraints. Order the product backlog by value so the thinnest viable offer can hit the date. Take the scope-versus-date trade-off to the sponsor in one page. Do not invent a detailed schedule you already know is false, and do not pretend the date is flexible because the team likes Scrum.
Rationale: this is hybrid delivery and tailoring, not a tribal vote. Honesty about uncertainty is Process. Protecting a public date is Business Environment. Forcing a fake Gantt trains everyone to ignore the plan. A designed seam is the professional move.
Scenario 2 — Good news, if we omit the defect
Two days before a steerco, testing finds a security defect in a feature the sponsor has already previewed to a customer. A senior stakeholder asks you to keep the pack green and 'handle it quietly after.' The team lead agrees it is real. A vendor who bid on the last contract also mentioned they have tickets to an industry event if the relationship 'stays smooth.'
Recommended next action: refuse the omission. Report the defect, the impact, and options (delay the demo'd feature, mitigate, or accept residual risk with an accountable owner). Decline the tickets and declare the conflict if it exists. Do not wait until after the customer conversation to become honest.
Rationale: honesty and responsibility veto the comfortable pack. Fairness vetoes the gift. People-domain courage, Business Environment risk, and a Process change to the release contents. Managing the stakeholder by joining the fiction is how incidents get keynote slots.
Scenario 3 — Two architects, one silent stand-up
Two senior architects disagree on the integration pattern. The daily coordination meeting has become a status mumble. The schedule is starting to slip. A delivery manager suggests you pick one architect and reassign the other 'to send a message.' Neither architect has been asked to a facilitated decision session. The sponsor is unaware.
Recommended next action: facilitate a structured decision with criteria (risk, time, reversibility, compliance), record the outcome, and only then update the plan. Do not start with a reassignment. Do not escalate past a conversation you have not run. If they still deadlock, escalate the decision, not the personalities.
Rationale: this is a People-domain conflict task first. The nuclear option is a later move and a poor first one. Process updates follow the decision. Skipping to HR theatre would look decisive and waste two specialists you still need.
Scenario 4 — The rule moved at noon
A regulator publishes guidance that affects your data-retention design. The team is mid-increment. The product owner wants to 'park it on the backlog' so velocity does not dip. Operations will inherit the system in six weeks. Nobody from compliance is in the review.
Recommended next action: pause the affected slice long enough to assess compliance impact with the compliance owner. Re-plan scope, evidence, and the handover. Inform the sponsor of benefit and date impact. Do not bury a legal change under story-point hygiene.
Rationale: Business Environment — compliance and organisational change — outranks a local flow metric. Story points are not the transformation, and they are not the exam of whether you understood the domain. Parking a regulator is how you schedule a finding.
Scenario 5 — The pet project and the full guild
A well-liked executive wants a new initiative started 'this quarter.' Your portfolio already has the only integration guild at 130% load. The initiative's benefit story is a slogan. A program already in flight will miss its benefit date if the guild is split. Someone suggests you 'just be Agile and parallelise.'
Recommended next action: show the capacity fact, the benefit comparison, and a recommendation to defer or to stop something else. Do not start the pet work on charm. If leadership still wants it, label it an explicit exception and name what will slip. Write the decision down.
Rationale: portfolio selection and strategic alignment. Parallelising a scarce specialist is not agility. It is a wish. Funding without a stop is how transformations and portfolios both become theatre. The next action is a decision, not a kick-off.
Course complete — what's next
In each case the pattern held: name the domain on fire, honour the hard constraint, refuse the ethical shortcut, and take the next verb — facilitate, disclose, assess, or decide — rather than the theatrical one. Hybrid was a seam, not a slogan. Tailoring was a written choice. Benefits and capacity outranked charm.
This was a reasoning drill, not a replica paper and not a score. There is no pass promise attached to finishing it. Take one live dilemma this week and write the next action and the rationale in four lines. If you can do that without decorating the RAG, you are practising the craft these courses were for.