A Scrum Master's job is to remove friction, not create documentation. But Agile frameworks still generate significant writing work: retrospective formats, sprint planning facilitation guides, stakeholder status emails, team health summaries, and the coaching scripts you need when a team isn't clicking.
ChatGPT doesn't run your ceremonies. It won't sense team morale or decide when to push back on a stakeholder. But it eliminates the preparation overhead that stacks up before every sprint, every retro, and every difficult conversation you need to have.
These 35 prompts are fill-in-the-bracket templates. Drop in your team's specifics and get a working first draft in under 60 seconds.
1. Sprint Planning and Backlog Refinement
Good sprint planning starts before the meeting. These prompts help you prepare materials, frame goals, and structure conversations that result in realistic commitments.
Prompt 1 — Sprint goal options from a backlog:
You are an experienced Scrum Master. Based on the following backlog items selected for our upcoming sprint, write 3 candidate sprint goal statements:
Backlog items: [LIST STORIES/TASKS]
Product area: [DESCRIBE]
Team size: [NUMBER]
Sprint length: [1 WEEK / 2 WEEKS]
Each sprint goal should: be outcome-oriented (not a task list), be achievable in one sprint, give the team a shared focus, and pass the "if we only accomplish one thing" test. Rank your 3 options and explain your reasoning.
Prompt 2 — Story refinement facilitation questions:
Write 5 facilitation questions to use during backlog refinement for the following user story: "[USER STORY TEXT]". Questions should surface: missing acceptance criteria, technical uncertainty, dependencies on other teams or systems, definition of "done" gaps, and edge cases the team might have missed. Questions should be open-ended and promote discussion rather than yes/no answers.
Prompt 3 — Sprint planning agenda:
Create a sprint planning agenda for a [2-WEEK] sprint with a team of [NUMBER] developers. Total ceremony budget: [TIME — e.g., 4 hours]. The team typically struggles with: [CHALLENGE — e.g., overcommitting, not surfacing blockers, vague acceptance criteria]. Include: time blocks for each agenda item, the goal of each section, and a facilitation note for the section where this team most often loses focus.
Prompt 4 — Definition of Done review:
Our team's current Definition of Done is: [LIST CURRENT DOD ITEMS]. We're a [TEAM TYPE — e.g., mobile app team, data engineering team, SaaS product team]. We've been delivering work that [DESCRIBE QUALITY ISSUE — e.g., needs rework after deployment, has gaps in test coverage, breaks accessibility standards]. Suggest 5 additions or modifications to our DoD that would address these issues. For each suggestion, include: what it requires, who's responsible, and how to verify it.
Prompt 5 — Capacity planning worksheet:
Create a sprint capacity planning worksheet for a team of [NUMBER] people for a [LENGTH] sprint. Team members: [LIST NAMES OR ROLES]. Include: available days per person (minus PTO, holidays, meetings), assumed focus factor [%], total team capacity in story points or ideal hours, and a notes column for context (on-call rotation, new hire ramp-up, etc.). Add a section to document assumptions and risks.
2. Daily Standups and Team Facilitation
Standups should take 15 minutes. They rarely do. These prompts help you structure better facilitation and address the patterns that derail them.
Prompt 6 — Standup format alternatives:
Our daily standup has become a status update monologue instead of a team synchronization. The current format is the traditional 3-question standup. Suggest 3 alternative standup formats that might better serve a team that: [DESCRIBE TEAM SITUATION — e.g., has all remote members, has dependencies between sub-teams, has been running the same sprint for 6 months]. For each format: the structure, what problem it solves, and potential downsides.
Prompt 7 — Standup impediment triage framework:
Create a quick decision framework I can use during standup when someone raises an impediment. The framework should help me decide in under 30 seconds whether to: resolve it immediately (how), park it for after standup (how), escalate it outside the team (to whom), or add it to the sprint backlog as a task. Include the 3 questions I should ask to route any impediment correctly.
Prompt 8 — Async standup template:
Create an async standup template for a distributed team in [NUMBER] time zones. The template should capture: what was done yesterday, what's planned today, any blockers, and any need for synchronous collaboration today. Keep it under 5 minutes to complete. Include: instructions for where to post it, the deadline for posting, and a note on how I'll review and respond as Scrum Master.
Prompt 9 — Addressing "always the same person is blocked" pattern:
Write a facilitation plan for addressing a recurring pattern in our standups: the same 2 team members are consistently blocked by [TYPE OF DEPENDENCY — e.g., another team's API, a specific external stakeholder, a shared infrastructure bottleneck]. The blockers are real but the team has stopped treating them as urgent. Include: how to surface this pattern without blame, a root cause discussion framework, and a concrete proposal for what to do differently this sprint.
Prompt 10 — Team working agreement:
Facilitate the creation of a team working agreement for a Scrum team of [NUMBER] people working [REMOTE/IN-PERSON/HYBRID]. The team has been together for [DURATION] and is experiencing friction around: [LIST 2–3 TENSION AREAS — e.g., response time expectations, code review latency, deployment frequency disagreements]. Create a facilitation plan with: discussion prompts for each tension area, a voting method for finalizing agreements, and a template for documenting the final working agreement.
3. Retrospectives and Continuous Improvement
The retrospective is your highest-leverage ceremony. These prompts create formats that go beyond "what went well / what didn't."
Prompt 11 — Retrospective format for a team in conflict:
Design a retrospective format for a team that has significant interpersonal tension between [DESCRIBE DYNAMIC — e.g., developers and QA, two senior engineers with competing visions, a team member who dominates discussions]. The format should: create psychological safety, allow all voices to be heard, surface process issues without making it personal, and result in 1–2 concrete action items. Avoid formats that allow blame or put individuals in the spotlight.
Prompt 12 — Retrospective format variety list:
Give me 5 unique retrospective formats I haven't used before, designed for a team that has been running standard Start/Stop/Continue retros for the past [TIME PERIOD] and is experiencing retro fatigue. For each format: name, structure, time required, best use case, and facilitation tips. Formats should range from low-energy to high-energy so I can match team mood.
Prompt 13 — Action item follow-through system:
Our retrospectives produce good action items but they rarely get completed before the next retro. Write a system for tracking and following through on retrospective action items. Include: where to document them (format/template), how to review them at the start of the next retro, accountability structure, and what to do when an item keeps getting deferred. The system should add less than 10 minutes to each retro.
Prompt 14 — Facilitation script for a difficult retro topic:
Write a facilitation script for raising [DIFFICULT TOPIC — e.g., the team missed sprint goals 3 sprints in a row / a recently released feature had critical bugs / team members aren't peer-reviewing code] at a retrospective. The script should: frame the topic as a system/process problem (not a blame session), use a specific data point or artifact as the anchor, create space for diverse perspectives, and end with a commitment to one concrete change. Under 5 minutes to deliver.
Prompt 15 — Retrospective outcomes report for leadership:
Write a retrospective outcomes summary for leadership/management for [SPRINT NUMBER]. Audience: engineering manager and product director who want to know if the team is improving without micromanaging. Include: sprint goal outcome (achieved/partially/not), top 2 process improvements discussed, action items committed to (with owners), and any systemic impediments that require management input or action. Under 300 words.
4. Stakeholder Communication and Reporting
Scrum Masters bridge the team and the organization. These prompts handle the external communication layer.
Prompt 16 — Sprint review summary for stakeholders:
Write a sprint review summary email for stakeholders who couldn't attend the sprint review. Sprint [NUMBER], [DATES]. Goals: [LIST SPRINT GOALS]. What was completed: [LIST DONE ITEMS]. What was not completed (and why): [LIST]. Key demo highlights: [DESCRIBE]. Decisions made by stakeholders at the review: [LIST]. Next sprint starts: [DATE]. Keep it factual and brief — under 200 words. No Scrum jargon.
Prompt 17 — Escalating an impediment to management:
Write an escalation email to [MANAGER/DIRECTOR] about an impediment that has been blocking the team for [TIME PERIOD]. The impediment: [DESCRIBE — e.g., waiting for security review approval, dependency on Team X's API that keeps slipping, unclear product decision]. What we've tried: [LIST]. What we need from them: [SPECIFIC ASK]. Impact on delivery: [DESCRIBE]. Keep it factual and specific, not emotional.
Prompt 18 — Velocity and burndown explanation for non-technical stakeholders:
Write a plain-language explanation of our team's recent velocity and burndown data for a stakeholder who doesn't understand Scrum metrics. Data: [DESCRIBE — e.g., velocity has dropped from 42 to 28 story points over 3 sprints; burndown consistently flat until day 8 then steep dropoff]. Explain: what these numbers mean, what's causing the pattern, what the team is doing about it, and what the stakeholder should/shouldn't infer from this data.
Prompt 19 — Release readiness communication:
Write a release readiness summary for stakeholders ahead of the [RELEASE NAME/DATE] release. Include: features included, features deferred (with rationale), known issues/risks, deployment plan summary, rollback capability (yes/no), monitoring plan, and who to contact if issues arise post-release. Audience: non-technical stakeholders including [CUSTOMER SUCCESS / SALES / EXECUTIVE TEAM].
Prompt 20 — Quarterly Agile health report:
Write a quarterly Agile program health report for [QUARTER/YEAR]. Audience: program leadership and Agile Coaches. Include: team velocity trend, sprint goal achievement rate [X of Y goals met], retrospective action completion rate, key impediments and resolution status, team health pulse summary [DESCRIBE IF DATA EXISTS], and 3 focus areas for next quarter with rationale.
5. Removing Blockers and Conflict Resolution
A Scrum Master earns trust by solving problems. These prompts help you prepare for hard conversations and structural fixes.
Prompt 21 — Difficult conversation preparation:
Help me prepare for a difficult conversation with [ROLE — e.g., a developer who is resistant to pairing, a product owner who keeps adding scope mid-sprint, a stakeholder who bypasses the team and assigns tasks directly]. The specific issue: [DESCRIBE]. My goal for the conversation: [OUTCOME I WANT]. Write: an opening that doesn't put them on the defensive, 3 questions to understand their perspective, the key point I need to make clearly, and a proposed agreement to close the conversation.
Prompt 22 — Dependency mapping workshop:
Design a 60-minute workshop to map and address team dependencies. Attending: [LIST TEAMS OR ROLES]. Known dependencies: [LIST WHAT YOU KNOW]. Goal: identify all inter-team dependencies for the next [TIME PERIOD], assign owners, and agree on communication protocols. Include: workshop agenda, materials needed, facilitation notes for the sections where dependency discussions typically break down, and a template for the dependency log output.
Prompt 23 — Cross-team impediment coordination email:
Write a coordination email to the Scrum Master of [OTHER TEAM] about a cross-team dependency that is blocking our team. Our team: [TEAM NAME]. Their team: [TEAM NAME]. The dependency: [DESCRIBE]. Impact on our sprint: [DESCRIBE]. Requested action: [SPECIFIC — e.g., API endpoint available by sprint day 5, confirmation on data schema by Wednesday]. Propose a synchronization touchpoint. Professional, collaborative tone.
Prompt 24 — Handling scope creep mid-sprint:
Write a response to our Product Owner who has asked the team to add [NEW ITEM] to the current sprint, which is already at full capacity. The new item is [PRIORITY LEVEL]. Include: acknowledgment of the business need, explanation of the sprint commitment and what adding this item would displace, 3 options with trade-offs (add and drop something, defer to next sprint, spike now and deliver next sprint), and a request for a clear decision by [DEADLINE]. Professional, not pushback-y.
Prompt 25 — Team conflict observation and coaching:
I observed [DESCRIBE CONFLICT — e.g., two developers arguing about code architecture in standup, a team member dismissing another's estimates repeatedly, passive-aggressive comments in code reviews]. Write: a coaching approach for addressing this (which framework to use), specific questions to ask each party separately, how to bring this to a team-level conversation if needed, and warning signs that this needs HR involvement rather than Scrum Master coaching.
6. Team Onboarding and Agile Coaching
Building Agile capability in a team is a long game. These prompts support training, onboarding, and coaching work.
Prompt 26 — New team member Scrum orientation:
Write a 30-minute Scrum orientation guide for a new team member joining [TEAM NAME]. They have [NO SCRUM EXPERIENCE / SOME SCRUM EXPERIENCE / COME FROM KANBAN BACKGROUND]. Cover: our specific Scrum implementation (sprint length, ceremony schedule, key roles), team working agreements, how to participate in ceremonies, where to find information (backlog, wiki, etc.), and "unwritten rules" of how this team actually works. Friendly, direct, practical.
Prompt 27 — Agile training workshop outline:
Design a half-day Agile fundamentals workshop for [AUDIENCE — e.g., new team members, executive stakeholders, a team transitioning from Waterfall]. Key concepts to cover: [LIST — e.g., Agile values and principles, Scrum framework overview, role of the Scrum Master, working in sprints]. Include: learning objectives, agenda with time blocks, 2 interactive exercises (not lectures), and a Q&A buffer. Audience has no Agile background.
Prompt 28 — Coaching plan for a struggling team:
Create a 6-sprint coaching plan for a Scrum team that is struggling with [SPECIFIC ISSUE — e.g., consistently missing sprint goals, low trust in the team, poor backlog quality, no real retrospective improvement]. For each sprint, define: the focus area, the coaching intervention (ceremony changes, one-on-one coaching, workshops, etc.), observable success indicator, and risks to watch for. Include a check-in mechanism at sprint 3.
Prompt 29 — Agile maturity assessment:
Create a simple Agile maturity self-assessment for a Scrum team. 20 questions covering: backlog quality, sprint planning realism, ceremony quality and participation, team collaboration, product owner engagement, continuous improvement cadence, and technical practices. Each question should be a 1–5 scale with descriptors for each level. Include instructions for how to score it and what score ranges suggest about maturity level.
Prompt 30 — Feedback script for a Product Owner who isn't available:
Write a coaching conversation script for giving feedback to a Product Owner who is consistently unavailable during sprints — they miss refinement sessions, don't respond to questions for 2+ days, and send a proxy to sprint reviews. The conversation should: describe the behavior and its impact with specific examples, ask for their perspective before jumping to solutions, propose specific availability agreements, and agree on how to handle situations when they genuinely can't be reached.
7. Metrics, Velocity, and Team Health
Data tells part of the story. These prompts help you communicate what the numbers mean and what to do about them.
Prompt 31 — Sprint metrics summary:
Write a sprint metrics summary for Sprint [NUMBER]. Data:
- Sprint goal achieved: [YES/PARTIALLY/NO]
- Committed story points: [X], Completed: [Y]
- Carry-over: [Z points, explain why]
- Bugs reported this sprint: [NUMBER]
- Team satisfaction: [IF SURVEYED — average score]
Write: a brief narrative (3 sentences), the top contributing factor to the sprint result, one metric trend to watch, and one team conversation to have next sprint.
Prompt 32 — Team health survey design:
Design a 10-question anonymous team health survey for a Scrum team. Cover: psychological safety, clarity of sprint goals, quality of collaboration, confidence in processes, and satisfaction with the team's direction. Each question should be a 1–5 scale. Include: the survey instructions, how to explain the purpose to the team, how to report results without identifying individuals, and 3 discussion prompts for reviewing the results at a team health retrospective.
Prompt 33 — Velocity trend analysis narrative:
Write a velocity trend analysis for the past 6 sprints. Velocities: [SPRINT 1: X, SPRINT 2: X, SPRINT 3: X, SPRINT 4: X, SPRINT 5: X, SPRINT 6: X]. Context: [LIST RELEVANT EVENTS — e.g., new team member joined sprint 3, major bug fix sprint 4, two people on PTO sprint 5]. Write: the trend story, what's driving it (your best analysis), whether the current velocity is a reliable forecast baseline, and what I'd recommend for the next sprint's planning assumptions.
Prompt 34 — Flow efficiency assessment:
Assess our team's flow efficiency based on the following cycle time data from the past sprint:
- Average time in "In Progress": [HOURS/DAYS]
- Average time in "In Review": [HOURS/DAYS]
- Average time in "Blocked": [HOURS/DAYS]
- Average time in "Waiting for Deploy": [HOURS/DAYS]
Calculate approximate flow efficiency percentage. Identify which state is the biggest waste contributor. Suggest 2 process changes to reduce wait time in the highest-waste state.
Prompt 35 — End-of-quarter team accomplishment summary:
Write an end-of-quarter team accomplishment summary for [TEAM NAME] for Q[QUARTER] [YEAR]. Audience: the team itself (for morale and reflection) and their engineering/product leadership. Include: sprints completed, sprint goals achieved vs. total, major features or capabilities shipped, key process improvements made, and one challenge the team navigated well. End with a forward-looking statement about Q[NEXT QUARTER]. Affirming but honest tone. Under 400 words.
Get 35 More Prompts — Organized by Agile Scaling and Advanced Scenarios
These 35 prompts cover core Scrum Master workflows. The full pack adds 35 more for advanced scenarios: SAFe and LeSS coordination, PI planning, distributed team facilitation, and Agile transformation coaching.
Get the full 70-prompt Scrum Master ChatGPT Pack →
Use LAUNCH30 for 30% off — limited uses remaining.
Every prompt is editable. Works with ChatGPT-4, Claude, and Gemini.
Top comments (0)