10 AI Prompts to Simulate Stakeholder Conflicts (PSM II Prep)

Practice makes perfect. The difference between a Junior Scrum Master and a Senior "AI Orchestrator" is often the ability to navigate conflict. The Scrum Guide gives you the rules, but it doesn't tell you what to say when a VP demands a fixed scope by Friday.

This guide acts as a training tool. It treats Generative AI (ChatGPT, Claude, Gemini) as a "Practice Partner" to help you simulate tough stakeholder conversations, building the "soft skills" required for senior roles and aceing behavioral interview questions.

← Back to the 2026 Scrum Master Roadmap

How to Use These Prompts

Do not just read these prompts—run them.

• Copy the prompt into your AI tool of choice.
• Roleplay the scenario for at least 5 exchanges.
• Ask for Feedback using the critique prompt at the end.

Category 1: The Product Owner Conflict

1. The "Feature Factory" PO

Scenario: The PO wants to skip the Retrospective to build more features.

Prompt: "Act as a Product Owner who is under immense pressure from sales. You want to cancel the Sprint Retrospective because 'we have too much work to do.' I am the Scrum Master. I will try to convince you of the value of the event. Be stubborn but logical. Only agree if I can prove how the Retrospective helps shipping speed in the long run."

2. The "Absentee" PO

Scenario: The PO defines the "what" but refuses to attend Sprint Events.

Prompt: "Act as a busy Product Owner who says, 'I wrote the user stories, I don't need to be at the Sprint Review.' Roleplay with me. Challenge me to explain why my presence matters for the feedback loop, not just for 'checking boxes'."

Category 2: The Team Dynamics

3. The "Hero" Developer

Scenario: A senior dev refuses to pair program or document work, creating a silo.

Prompt: "Act as a '10x Developer' who thinks Scrum slows them down. You refuse to update the ticket status or attend the Daily Scrum because 'you are coding.' I am the Scrum Master. Coach me on the value of transparency without making me feel micromanaged."

4. The "Zombie Scrum" Team

Scenario: The team attends events but is disengaged and silent.

Prompt: "Simulate a Daily Scrum where the entire team gives generic updates like 'worked on ticket 123, no blockers.' I am the Scrum Master trying to spark genuine collaboration. React to my questions with apathy until I ask something that actually triggers engagement."

Category 3: The Organization & Management

5. The "Deadline-Driven" Manager

Scenario: A manager demands a fixed delivery date for a complex feature.

Prompt: "Act as a Middle Manager who demands a specific release date for a complex, uncertain feature. I will try to explain 'Empirical Process Control' and 'Cone of Uncertainty' to you. Push back by saying 'the business needs certainty, not agile jargon'."

6. The "Scope Creep" Stakeholder

Scenario: A stakeholder tries to add items directly to the Sprint Backlog mid-Sprint.

Prompt: "Act as a Sales Director who just promised a client a new feature and wants it added to the *current* Sprint. I am the Scrum Master protecting the Sprint Goal. Roleplay this conflict. Be aggressive about the 'business urgency'."

The "Feedback" Prompt

After you finish a simulation, paste this to get coaching:

Prompt: "Analyze my responses in the previous roleplay. Did I uphold the Scrum Values of Respect and Openness? Did I sound defensive or coaching-oriented? Give me 3 specific tips to improve my conflict resolution skills."