10 AI prompts every Scrum Master should steal

Stop asking AI "help me with Scrum"

Most Scrum Masters try AI once, type something vague, get a generic answer and give up. The difference is in the prompt. A good prompt gives the AI a role, the real context and a clear output.

Here are 10 prompts you can copy into ChatGPT, Claude or Gemini today. Replace the parts in [brackets] with your own details.

Refinement

1. Split a story that is too big

Act as an experienced Scrum Master. Split this user story into 3 to 5 smaller stories.
Each one must deliver user value on its own (vertical slices, not technical layers)
and fit in a few days of work. For each, write a title and one line on the value.
Story: [paste the story]

2. Write acceptance criteria

Write acceptance criteria for this user story in Given / When / Then format.
Include the happy path, at least 3 edge cases and one error case.
Story: [paste the story]

3. Find the gaps before Refinement

Review this backlog item as if you were a developer seeing it for the first time.
List the questions you would ask the Product Owner before you could start.
Group them into: unclear scope, missing data, dependencies, and risks.
Item: [paste the item]

Sprint Planning

4. Draft a Sprint Goal

Here are the items the team selected for the next Sprint: [list].
Suggest 3 possible Sprint Goals. Each must be one sentence, describe an outcome
for users or the business, and not just list the items.

5. Check if the Sprint is overloaded

Our Sprint is [10] working days. Team availability: [name: days available, ...].
Selected work totals [X] story points. Our average velocity is [Y].
Tell me if we are overcommitted, by how much, and which items to move out first
based on this priority order: [list].

Daily Scrum

6. Turn messy notes into a blocker list

Here are notes from today's Daily Scrum: [paste notes].
Extract only the blockers. For each one: who is blocked, what is blocking them,
who can help, and whether it threatens the Sprint Goal. Keep it under 10 lines.

Retrospective

7. Group feedback into themes

Here is anonymous Retrospective feedback from the team: [paste].
Group it into 3 to 5 themes. For each theme, give a short name, how many comments
belong to it, and one concrete action the team could try next Sprint.
Do not add opinions that are not in the feedback.

8. Get a fresh Retro format

Suggest a 45-minute Retrospective format for a team of [7] that feels
[tired after a hard release]. Include the steps, timing for each step,
and the exact questions to ask. Avoid Start/Stop/Continue.

Stakeholders and risk

9. Write a stakeholder update

Turn this Sprint report into a short update for non-technical managers: [paste].
Use plain language, no jargon. Cover what was delivered, what slipped and why,
and what we need from them. Maximum 150 words.

10. Spot risks in the backlog

Review these upcoming backlog items: [paste].
Identify dependencies between items, dependencies on other teams,
and items that look risky or underestimated. Explain each in one line.

Two rules before you paste anything

• Don't paste confidential data. Remove client names, credentials and personal information, or use your company's approved AI tool.
• AI drafts, the team decides. Use the output to start a conversation in Refinement or the Retro, not to replace it. The Sprint Goal and the commitment still belong to the team.

Your turn

Which of these will you try first? And what's the one prompt you use every Sprint? Share it so other Scrum Masters can steal it too.

Where LazyScrum fits

Prompts help with the thinking. The planning work itself still takes hours: collecting availability, sizing, checking capacity. With LazyScrum, you can see and follow all the activity from one place. LazyScrum runs live Sprint Planning on top of Jira, with Estimation, real capacity and a 30-minute timeline, plus start and end of sprint reports. Team members join planning free, so the whole team plans together.

LazyScrum offers a 7-day free trial. Try it here.