Scrum Masters serve the team, not the backlog. Your job is to remove impediments, facilitate ceremonies, coach agile practices, protect the team from distraction, and help people work together more effectively—all without having direct authority over any of it.
It's a role that generates a lot of documentation: sprint reports, retrospective summaries, impediment logs, stakeholder updates, team health assessments, and the constant stream of communication required to keep a Scrum team aligned and moving.
ChatGPT won't facilitate your retrospectives or build your team culture. But it can handle the writing, structuring, and scaffolding that surrounds your facilitation work. These 35 prompts cover the full Scrum Master workflow: ceremonies, impediment management, stakeholder communication, coaching, and professional development.
Sprint Ceremonies
Prompt 1 — Write a sprint goal
Write a sprint goal for Sprint [X]. Our committed user stories: [list story titles]. The business objective we're supporting: [what the team is working toward]. A good sprint goal should: capture the business outcome in 1-2 sentences, be achievable even if some stories slip, and give the team a north star for decisions during the sprint. Avoid listing features — focus on value delivered.
Prompt 2 — Write sprint planning questions
Write a set of sprint planning facilitation questions for a [X]-person team planning Sprint [X]. Include questions for: confirming team capacity, reviewing the sprint goal before committing, clarifying ambiguous stories before pulling them in, identifying dependencies and risks, and checking for agreement before finalizing the sprint. 10-12 questions total, organized by planning phase.
Prompt 3 — Write daily standup prompts
Our team's standups have become status reports rather than coordination conversations. Write 5 alternative standup question sets (rotate daily) that focus on: collaboration needs, impediment surfacing, sprint goal progress, and cross-team dependencies. Each set should have 3 questions. Avoid "what did you do yesterday" — focus on "what does the team need to know today."
Prompt 4 — Write a retrospective agenda
Design a [60/90]-minute retrospective agenda for a team that [has been together X sprints / just launched a product / is struggling with delivery pace / needs to celebrate a win]. Include: opening activity to create psychological safety, a method to gather data (timeline, sailboat, 4Ls, etc.), a process to identify insights, a way to commit to actionable improvements, and a closing. Include facilitation notes for each section.
Prompt 5 — Write retrospective action items
Our retrospective identified the following themes and experiments to try: [paste what the team agreed on]. Convert these into formal action items with: a clear description of the action, the owner (team / specific role / SM), the success metric (how we'll know it worked), and a review date (next retro or specific sprint). Format as a living action item tracker.
Prompt 6 — Write a sprint review agenda
Design a sprint review agenda for Sprint [X]. Attendees: [list — team, PO, stakeholders]. Key demo items: [list features or stories completed]. Duration: [X minutes]. Include: opening (sprint goal recap), demo sequence (who shows what), stakeholder feedback gathering, product backlog discussion, and close. Include time estimates per section and facilitation tips for keeping demos focused.
Prompt 7 — Write sprint review notes
Write sprint review meeting notes from the following raw notes: [paste notes]. Include: sprint goal outcome (met/partially met/not met), stories demonstrated, stakeholder feedback (organized by theme), decisions made, backlog items added or changed as a result, and open questions. Format for distribution to stakeholders who weren't in the room.
Retrospective Facilitation
Prompt 8 — Design a themed retrospective
Design a themed retrospective for a team that [describe situation — has been struggling with quality / just shipped a major release / is newly formed / is experiencing conflict]. Theme: [suggest a metaphor — weather, sailing, cooking, etc.]. Include: the metaphor frame, 4 questions mapped to the theme (what worked, what didn't, what to try, what to keep), instructions for running it, and estimated time per section.
Prompt 9 — Write a retrospective summary
Write a retrospective summary for Sprint [X]. What went well: [paste team's items]. What didn't go well: [paste items]. Actions we're committing to: [paste agreed actions]. Format for sharing with the team after the session and as a record for the Scrum Master's improvement tracking. Include the sprint number and date for reference.
Prompt 10 — Write retrospective facilitation notes
I'm facilitating a retrospective for a team that has the following dynamics: [describe — e.g., remote, some tension between devs and QA, some members quieter than others]. Create facilitation notes for me covering: how to open with psychological safety, techniques for drawing out quieter voices, how to handle it if the retro starts to become a blame session, and how to close with genuine commitment rather than going through the motions.
Prompt 11 — Write a team health check
Design a team health check assessment for a Scrum team. Include 8-10 dimensions: e.g., sprint goal clarity, retrospective effectiveness, impediment resolution speed, cross-functional collaboration, delivery predictability, technical debt management, team morale, and stakeholder relationships. For each dimension: write a question, a scale (1-5), and anchors that describe what 1, 3, and 5 look like. Format for a quarterly team self-assessment.
Impediment Management
Prompt 12 — Document an impediment
Write an impediment documentation entry for: [describe the impediment]. Include: impediment title, date identified, who raised it, description of the impact on the team, root cause (if known), owner of resolution (SM / specific person / leadership), actions taken so far, target resolution date, and current status. Format for an impediment log that I review weekly.
Prompt 13 — Write an impediment escalation
Write an escalation message for an impediment that has been unresolved for [X days]. The impediment: [describe]. Impact on the team: [describe in concrete terms — stories blocked, sprint goal at risk, team capacity affected]. What I've already tried to resolve it: [list actions]. What I need from leadership: [specific ask]. Audience: [engineering director / product leader / department head]. Factual and action-focused.
Prompt 14 — Write a dependency tracking update
Write a dependency tracking update for our team's external dependencies this sprint. Dependencies: [list — each with the team/person we're depending on, what we need, and when we need it]. Status of each: [list]. Risks: [which dependencies are at risk of not being resolved in time]. Actions: [what I'm doing to accelerate resolution]. Format for the weekly dependencies sync meeting.
Stakeholder Communication
Prompt 15 — Write a sprint report for stakeholders
Write a sprint report for Sprint [X] for non-technical stakeholders. Sprint goal: [description]. Goal outcome: [met / partially met / not met]. Stories completed: [list]. Stories not completed (and why): [if any]. Key metrics: velocity [X], bug count [X], any other relevant metrics. Next sprint focus: [brief description]. Risks or concerns for leadership awareness: [list]. Under 300 words. No Scrum jargon — write for a business audience.
Prompt 16 — Write a team velocity communication
Our team's velocity has [increased/decreased/been inconsistent] over the last [X] sprints. I need to explain this to stakeholders. Velocity trend: [describe with numbers]. Reasons: [list — team changes, tech debt, new work types, interruptions, etc.]. What this means for our roadmap: [impact]. What we're doing about it: [improvements underway]. Frame this as a data-informed explanation, not a defense.
Prompt 17 — Write a PI planning preparation summary
Write a PI (Program Increment) planning preparation summary for our team. Team members: [list with roles]. Capacity for the PI: [total story points or sprint capacity]. Known constraints: [vacations, dependencies, shared resources]. Team objectives for this PI (draft): [list]. Risks we're bringing to PI planning: [list]. Dependencies we need resolved: [list]. Format for the team wall and for sharing with our RTE or program manager.
Prompt 18 — Communicate a missed sprint goal
We missed our sprint goal for Sprint [X]. What was committed: [sprint goal]. What we delivered: [what actually shipped]. Why we missed: [honest explanation — scope underestimation, unexpected complexity, interruption, dependency blocked, etc.]. What we're doing differently next sprint: [specific changes]. Write this as a transparent, factual communication for the product owner and key stakeholders. No excuses, no spin.
Coaching and Team Development
Prompt 19 — Write a coaching conversation guide
I need to have a coaching conversation with a team member who [describe situation — is dominating standups, is resistant to retrospective feedback, is consistently underestimating stories, is not following agreed team norms]. Help me: frame the opening without putting them on the defensive, ask questions that help them reflect rather than telling them what to do, identify what success looks like from this conversation, and plan a follow-up.
Prompt 20 — Write a new team member onboarding guide
Write a Scrum team onboarding guide for a new member joining our team. Cover: our team's working agreements, how our ceremonies work (schedule, format, expectations), how we use our tools [Jira/Linear/Azure DevOps], our definition of done, our norms around communication (async vs. sync, channels), and the 5 most important things to know in the first sprint. Friendly and practical.
Prompt 21 — Create team working agreements
Facilitate the creation of team working agreements by generating a starter set for a [remote / hybrid / co-located] Scrum team of [X] people. Cover: core hours and availability, meeting norms (camera on/off, muting, facilitation), communication channels and expected response times, definition of "ready" and "done," code review turnaround, and how we handle conflict. Present these as a draft the team can adapt, not rules imposed from above.
Prompt 22 — Write a team charter
Write a team charter for [team name]. Team mission: [why this team exists]. Members and roles: [list]. Ways of working: [key agreements]. Success metrics: [how we measure team effectiveness]. Decision-making: [how we make decisions, who has authority over what]. Communication: [internal and external norms]. Review cycle: [when we revisit the charter]. Format as a living document the team owns and updates.
Prompt 23 — Write a conflict resolution facilitation guide
Two team members are in conflict about [describe the disagreement — technical approach, workload, communication style]. Help me prepare to facilitate a resolution conversation. Include: how to frame the conversation to both parties before it starts, questions I can ask to help each person feel heard, techniques to move from positions to interests, how to reach an agreement they'll both honor, and follow-up steps.
Metrics and Reporting
Prompt 24 — Write a velocity trend analysis
Write a velocity trend analysis for the last [X] sprints. Velocity by sprint: [list]. Trends observed: [increasing/decreasing/volatile]. Contributing factors: [list what affected velocity in key sprints]. Forecast for next sprint: [range]. Implications for roadmap: [what PO and stakeholders should know]. Recommended actions: [if any]. Format for the retrospective and for stakeholder communication.
Prompt 25 — Write a sprint metrics summary
Write a sprint metrics summary for Sprint [X]. Include: planned vs. committed vs. completed story points, sprint goal outcome, defects found vs. resolved, carryover stories, team availability vs. actual (if tracked), and cycle time for completed stories (if available). For each metric: the number and a 1-sentence interpretation. Format for the SM's records and for sharing with the product owner.
Prompt 26 — Write a cumulative flow diagram interpretation
Help me interpret our cumulative flow diagram. What I'm seeing: [describe — e.g., "the 'in progress' band is widening," "there's a flat line in the 'done' column," "work is piling up in code review"]. Write a plain-English interpretation of: what this pattern indicates about our workflow, the likely root cause, and what we should do to address it. Audience: the team and product owner.
Agile Coaching and Process Improvement
Prompt 27 — Write a process improvement proposal
Write a process improvement proposal for our team based on the following retrospective findings: [paste recurring themes from retrospectives]. For each improvement: describe the current state, the proposed change, the expected benefit, how we'll measure success, and what we need to commit to making it work. Format as a proposal I can present at our next retrospective.
Prompt 28 — Evaluate our Scrum implementation
Evaluate our team's Scrum implementation based on the following observations: [describe how we run ceremonies, our definition of done, our sprint length, our backlog health, our team composition, and any known pain points]. Identify: where we're following Scrum well, where we've made pragmatic adaptations that work, where we're deviating in ways that are hurting us, and 3 specific recommendations to improve our implementation.
Prompt 29 — Design a Scrum training session
Design a [60/90]-minute Scrum training session for [audience — new team members / stakeholders / leadership]. Topic: [e.g., "what Scrum is and why we use it," "how to write good user stories," "understanding the Scrum events"]. Include: learning objectives, agenda with timing, key concepts to cover, 1-2 interactive exercises, and how to handle common objections or questions from skeptics.
Prompt 30 — Write a scaling Scrum proposal
We need to coordinate Scrum across [X] teams working on the same product. Current state: [describe how teams work today]. Challenges: [list coordination problems]. Proposed approach: [Scrum of Scrums / SAFe / LeSS / Nexus — describe what you're considering]. Expected benefits: [list]. Risks and mitigation: [list]. What we need to get started: [resources, time, commitments]. Format for leadership review.
Professional Development
Prompt 31 — Prepare for a PSM or CSM exam
I'm studying for the [PSM I / CSM / PSM II] certification. Key areas to master: [list — Scrum values, roles, events, artifacts, theory]. Create 15 practice questions across these areas at the difficulty level of the actual exam. Include: scenario-based questions (not just definitions), the correct answer, and an explanation of why each distractor is wrong. Focus on questions that test judgment, not recall.
Prompt 32 — Write a Scrum Master self-assessment
Write a Scrum Master self-assessment for my performance review. My current team context: [describe]. What I've done well this year: [list]. Where I've grown: [list]. Areas I want to develop: [list]. My goal for next year: [describe]. Help me articulate my impact in terms of team outcomes — delivery predictability, impediment resolution speed, retrospective action completion rate — not just activities I facilitated.
Prompt 33 — Design a personal learning plan
Design a 6-month learning plan for a Scrum Master who wants to grow in [area — technical depth / organizational agility / coaching / facilitation / leadership]. Current level: [experience description]. Recommended resources: [books, courses, communities]. Monthly milestones: [what to achieve each month]. How to measure growth: [concrete indicators]. Format as an actionable plan I can review monthly.
Prompt 34 — Write a conference talk abstract
Write a conference talk abstract for [agile conference]. Topic: [describe your talk idea]. Key insights or story: [what you want to share]. What attendees will take away: [3 specific things]. Format: [case study / workshop / keynote / panel]. Keep the abstract under 300 words. Lead with the problem or tension that will hook the audience, not with your credentials.
Prompt 35 — Write a team success story
Write a team success story for [context — internal newsletter / conference talk / portfolio / LinkedIn]. The achievement: [describe what the team accomplished]. What made it hard: [the challenge or obstacle]. How we got there: [key changes or decisions]. My role as Scrum Master: [what I contributed — coaching, facilitation, impediment removal]. Measurable outcomes: [quantify where possible]. Under 400 words. Celebrate the team, not yourself.
Getting the Most From These Prompts
Add team context. These prompts work best when you include your team's specific situation — size, tech stack, organizational dynamics, and current pain points. Generic teams produce generic outputs.
Use for facilitation prep, not facilitation replacement. ChatGPT is excellent for designing agendas, drafting summaries, and structuring communications. Your job is creating the psychological safety, reading the room, and adapting in the moment — that's the irreplaceable part.
Adapt the language to your org. Some organizations use SAFe, LeSS, or Kanban terminology. Adjust prompt language to match your context.
The Complete Scrum Master AI Toolkit
These 35 prompts cover ceremonies, impediment management, stakeholder communication, coaching, and professional development. If you want the full system — advanced ceremony design templates, team health frameworks, stakeholder communication libraries, and a complete agile coaching toolkit — the Scrum Master AI Toolkit has everything organized.
Get the Scrum Master AI Toolkit →
Bookmark this page. Share it with your agile community. Use one prompt before your next retrospective — you'll facilitate with more confidence and less prep time.
Top comments (0)