The Ultimate AI Scrum Master Prompt Library

By Sanjay Saini | Published: | Updated: | 13 Prompts
AI Scrum Master Prompts: A digital illustration showing a Scrum Master integrating AI technology into Agile workflows

Why Use AI in Scrum Mastery?

Welcome to the ultimate resource for modern Agile practitioners. As a Scrum Master, your core accountability is fostering team effectiveness, removing impediments, and aligning stakeholders. But what happens when you hit a wall? What happens when retrospectives become stale, or when stakeholders consistently bypass the Product Owner?

Artificial Intelligence isn't here to replace human coaching—it's here to amplify it. The carefully engineered prompts below are designed to act as your digital thinking partner. They help you leverage Large Language Models (LLMs) like ChatGPT, Gemini, or Claude to brainstorm workshop structures, draft empathetic coaching scripts, and prepare for difficult conversations before they happen.

New in this update: We've added three powerful Claude prompts (#11, #12, #13) for Product Owners and Scrum Masters who want to write better user stories instantly — covering INVEST-compliant story generation, edge case hunting, and vertical story splitting.

How to use this library: Simply click on any card below to reveal the prompt, copy it to your clipboard, and paste it directly into your preferred AI tool.

1. Coaching POs on Sprint Goals

Generate an empathetic coaching script to help a PO move from a disconnected list of tickets to an outcome-focused goal.
You are an experienced Scrum Master mentoring a newly appointed Product Owner. The PO has brought a list of disconnected Jira tickets to Sprint Planning and is entirely focused on output (ticket completion) rather than outcomes (customer value). Write a script for a 10-minute coaching conversation where you empathetically guide them to discover the true, value-driven Sprint Goal for the upcoming sprint. Include specific questions I should ask them.
2. Break the Daily Scrum Slump

Design a quick brainstorming activity to surface hidden impediments when your Daily Scrum becomes vague.
Context: I am a Scrum Master. We are midway through our Sprint and progress is slowing down. Developers are impeded but aren't raising issues clearly—our Daily Scrums have become vague and repetitive. Our Sprint Goal is currently at risk. Reason: I need to design a 30-minute activity for my team to brainstorm how we can incorporate AI directly into our current problem-solving session to still achieve the Sprint Goal. Audience: The Scrum Team who are technically skilled but currently struggling with open communication. Format: Provide 3-5 creative ways to use an AI agent as a silent or active participant in an emergency brainstorming session. Topic Scope: Focus only on ways to integrate AI into the brainstorm to surface hidden impediments and refocus the team. Do not provide a general sprint planning guide. Source: Ground the suggestions in Scrum principles of transparency and self-management. Soul!: The tone should be urgent yet supportive and authentic. We need to cut through the 'vagueness' and get to the truth of what is stopping us, without making the team feel blamed.
3. High-Level Stakeholder Roadmap

Generate a clean, strategic 3-month roadmap structure specifically designed for Sprint Reviews.
Context: I am a Scrum Master. Our previous Sprint Reviews have been chaotic, leaving stakeholders confused about our priorities. The Product Owner and I want to present a simple, forward-looking roadmap to reset expectations. Reason: Create a high-level visual roadmap for the next Sprint Review to align stakeholders on where the product is heading and clearly answer 'What’s next?' Audience: External and internal stakeholders who need a 'big picture' view without getting lost in technical details or specific Jira ticket IDs. Format: Generate a 3-month high-level roadmap structure. Include a summary of the current sprint's value and a prioritized list of upcoming themes for the next three sprints. Topic Scope: Focus strictly on product vision, high-level themes, and strategic direction. Do not include specific technical tasks or sub-tasks. Source: Align with the Professional Scrum Master and Product Owner accountabilities for fostering transparency and managing stakeholder expectations. Soul!: The tone should be professional, transparent, and confidence-building. Show that we have a clear grip on the product's future while remaining agile enough to pivot based on feedback.
4. Cure Retrospective Fatigue

Design a highly interactive, themed retrospective to re-engage a tired or demoralized team.
My Scrum Team is experiencing 'Retrospective fatigue' and disengaging during our session. Let's think step-by-step: First, analyze why a highly technical software development team might find the standard 'what went well/what didn't go well' event boring. Second, based on those reasons, suggest psychological or structural changes to the session to boost engagement. Finally, provide a detailed facilitation guide for a 60-minute Sprint Retrospective using a 'Movie Critic' (or similar creative) theme. Include a 10-minute icebreaker, a 30-minute data-gathering phase, and a 20-minute action-item generation phase. Provide the exact questions I should ask the team to prompt discussion and identify at least one actionable process improvement.
5. Vision Alignment Workshop

Facilitate a 2-hour workshop to connect a disconnected technical team back to the overarching product purpose.
Context: I am a Scrum Master. My team has recently lost focus on our long-term goals and is struggling to see how their daily tasks connect to the 'bigger picture'. Reason: Design a focused and engaging workshop that gives the entire Scrum Team absolute clarity on the product vision, purpose, and direction. We want to move away from 'Zombie Scrum'. Audience: A cross-functional Scrum Team who are technically skilled but currently feel disconnected from the product's impact on our customers. Format: Generate a detailed 2-hour workshop agenda including: - A timed breakdown of activities. - Specific facilitation formats and interactive techniques (e.g., Liberating Structures). - Ideas for using AI tools as 'thinking partners' during the session. Topic Scope: Strictly limited to identifying and aligning on the product vision and future direction. Avoid deep-dives into technical debt or specific backlog item refinement. Source: Ground the design in Scrum.org principles, fostering self-management and team effectiveness. Soul!: Collaborative, inspiring, and transparent. It must feel human-led and authentic, ensuring the final vision is driven by the team’s collective wisdom and empathy.
6. The Agile Story Slicer

Help developers break down massive, monolithic technical tasks into thin, value-delivering vertical slices.
Act as an Agile Technical Coach. My team is struggling to break down a massive User Story/EPIC: [Insert Story/EPIC description]. Currently, they want to split it horizontally by technical layer (e.g., DB task, API task, UI task), which violates the INVEST principle. Provide 3 different ways to *vertically* slice this story based on value (e.g., slice by workflow step, slice by business rule, slice by user persona). For each slice, write the new User Story and briefly explain how it delivers independent value so I can present this to the team during Backlog Refinement.
7. Difficult Conversation Simulator

Practice navigating team conflicts or pushy stakeholders in a safe, AI-simulated environment.
Act as a defensive, highly technical Senior Developer who is frustrated with our QA process and is starting to cause friction in the team. I am the Scrum Master, and I need to coach you on collaborating better with the testers. Let's roleplay this conversation one response at a time. I will start. You must evaluate my responses for empathy and alignment with Scrum values (Openness, Respect), and push back realistically. Let's begin: "Hey [Name], I noticed there was some tension in the Daily Scrum today regarding the testing bottlenecks. Do you have a few minutes to chat about it?"
8. Value-Metrics Translator

Generate a script to help redirect management's obsession with "Velocity" toward true Agile metrics.
I am a Scrum Master preparing for a 1-on-1 meeting with a senior stakeholder. They are obsessed with increasing our team's 'Velocity' and keep comparing our Story Points to other teams to measure our "performance." Write a professional, diplomatic 3-minute talking script that explains why comparing velocity is a dangerous anti-pattern. Then, help me pivot the conversation to 3 specific value-based metrics we should track instead (e.g., Cycle Time, Work Item Age, Customer Satisfaction). Keep the tone collaborative and educational, not preachy.
9. Mid-Sprint Interrupt Shield

Draft empathetic but firm responses to stakeholders who bypass the PO and push urgent work.
A key stakeholder just sent a direct message to my Developers asking them to "squeeze in" an urgent feature. Doing this jeopardizes our current Sprint Goal. As the Scrum Master, I need to intervene to protect the team's focus and promote self-management. Draft a polite, firm, and empathetic email to this stakeholder. The email should acknowledge their urgency, visually explain the impact of context-switching on our active Sprint Goal, and gently redirect them to the Product Owner to discuss prioritizing this for the *next* sprint.
10. Definition of Done Expander

Facilitate a discussion to upgrade a weak DoD into a robust standard ensuring true increment readiness.
Our Scrum Team's current Definition of Done is too basic (e.g., "Code written, tests passed, merged"). We are dealing with technical debt and need to mature our engineering practices. Generate a 'Definition of Done Maturity Matrix' with three columns: Basic, Intermediate, and Advanced. Include criteria across categories like Code Quality, Security, Automation, and Documentation. Finally, provide 3 powerful coaching questions I can ask the team during our Retrospective to help them collaboratively decide which *one* new criteria they want to adopt for the upcoming sprint.
11. INVEST User Story Generator

Convert a rough feature idea into a refinement-ready user story that follows INVEST criteria, with Given-When-Then acceptance criteria.
Act as a senior Product Owner with 10+ years of experience writing high-quality backlog items for cross-functional Agile teams. I will paste a rough feature idea or stakeholder request below. Convert it into a well-formed user story that strictly follows the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). Your response must include: 1. A user story written in the standard format: "As a [persona], I want [goal], so that [benefit]." 2. A clear, outcome-focused description (2-3 sentences) explaining the user value. 3. 4-6 acceptance criteria written strictly in Given-When-Then (Gherkin) format. 4. A short "Notes for Refinement" section listing assumptions made and 2-3 questions the team should clarify during backlog refinement. Here is the rough feature idea: [PASTE YOUR IDEA HERE]
12. Edge Case & Failure Scenario Hunter

Stress-test a user story by surfacing every edge case, failure mode, and missing acceptance criterion before it reaches the developers.
Act as a seasoned QA engineer and senior developer reviewing a user story before Sprint Planning. Your job is to find every gap, ambiguity, and risk that could cause this story to fail in production or be rejected during the Sprint Review. Review the user story I paste below and produce a structured analysis with these sections: 1. **Edge Cases** — List 8-10 edge cases the current story does not address (empty inputs, boundary values, concurrency, network failures, permissions, etc.). 2. **Failure Scenarios** — Describe 5 realistic ways this feature could fail in production and what the system should do in each case. 3. **Missing Acceptance Criteria** — List 5-7 acceptance criteria that should be added before the story is ready for development. 4. **Non-Functional Concerns** — Flag any gaps around performance, security, accessibility, observability, or data privacy. 5. **Clarifying Questions for the Product Owner** — 3-5 sharp questions the team should ask before estimating this story. User Story to review: [PASTE YOUR USER STORY HERE]
13. Vertical Story Splitter

Break a story that's too large for one sprint into 3 smaller, independently deliverable slices — each delivering real user value.
Act as an experienced Agile coach who specializes in story slicing and incremental delivery. The user story I paste below is too large to be completed in a single sprint. Split it into 3 smaller, independently deliverable user stories using vertical slicing — meaning each smaller story must: - Deliver real, observable value to a user or stakeholder (no purely technical or "back-end only" slices). - Be deployable on its own without depending on the other slices. - Be small enough to fit comfortably within a single sprint. For each of the 3 split stories, provide: 1. The full user story in "As a / I want / So that" format. 2. 3-4 acceptance criteria in Given-When-Then format. 3. A short rationale (1-2 sentences) explaining the user value delivered by this slice. 4. A suggested delivery order, with reasoning (which slice should ship first and why). Also explicitly flag any shared assumptions, dependencies, or technical considerations the team should discuss during refinement. Original large user story: [PASTE YOUR USER STORY HERE]

Next Steps in Your Agile Journey

Prompt engineering is an evolving skill. By tailoring these templates to match your specific organizational context, team culture, and industry, you transform generic AI outputs into highly personalized coaching assets. Remember, the goal of using these tools is to free up your mental bandwidth so you can focus on what truly matters: human connection, observing team dynamics, and driving continuous improvement.

Ready to Elevate Your Scrum Mastery?

Go beyond copying prompts. Learn how to securely integrate AI to facilitate better events, coach teams through complex impediments, and master Agile leadership in our exclusive hands-on workshop.

AI Essentials for Scrum Masters Training Badge