How well did we meet the sprint goal?
Not at all / Partly / Mostly / Fully
A rating the team can track from one sprint to the next, provided the wording stays the same.
Sprint retrospective: collect input before the meeting
A sprint retrospective survey collects the team's view of the sprint before the meeting, so that quieter people can contribute and the discussion starts from patterns rather than memory. Ask about the sprint and its process, not about individuals, and keep the same questions each time so the answers can be compared. The meeting then turns the themes into one or two actions with owners.
What people search
Sprint retrospective: 1,000 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Question bank
Questions about the sprint, not the people in it
What went well that we should keep doing?
Open text, up to three items
Protects the practices the team depends on, which otherwise get changed without anyone deciding to change them.
What slowed the sprint down?
Open text, up to three items
Names the friction. Ask about the work, the handoffs and the process, so the answers describe the system rather than a person.
How clear were the priorities during the sprint?
Very unclear / Unclear / Mixed / Clear / Very clear
Shows whether unfinished work came from the plan or from the execution of it.
What is one change to try next sprint?
Open text, one change
A single change can be tested in the next sprint. Several changes at once cannot show which one helped.
Field blueprint
A form to send a day before the meeting
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Sprint name or numberFor example: Sprint 14 | Short text | Required | Ties the answers to one sprint so that trends can be read later. |
How well did we meet the sprint goal?Not at allPartlyMostlyFully | Single choice | Required | The same rating every sprint, so the team can see movement over time. |
What went well? | Long text | Optional | Things to keep. Asking for what worked first gives the team something to build on before the harder answers. |
What slowed the sprint down? | Long text | Required | The friction the team wants to address. Ask about the work and the process, not about a named person. |
How clear were the priorities?Very unclearUnclearMixedClearVery clear | Single choice | Required | Separates a planning problem from an execution problem before the meeting starts. |
One change to try next sprint | Long text | Required | A single change is testable. Several changes at once cannot show which one helped. |
Anything you would rather raise privately | Long text | Optional | A place for points that are hard to raise in a group. Read it before the meeting, and speak to the writer first if they gave a name. |
Your name (optional) | Short text | Optional | Lets the facilitator follow up on a point. Leave it blank if you want fewer identifying details, knowing that a small team can still recognize a writer by wording. |
Try it
Fill it in as a team member would
Read the results
Turn the answers into one or two actions
Group the answers before the meeting
Read the answers and sort them into a few themes. Put the themes on the agenda, so the group discusses the pattern rather than reading every answer aloud.
Count how many people raised each theme
A theme raised by one person can still matter, but a theme raised by most of the team is the one to discuss first. Count the mentions rather than weighing the loudest voice.
Choose one or two actions, each with an owner
Pick actions the team can finish in the next sprint, name one owner for each, and check them at the start of the next retrospective.
Compare the same questions over several sprints
Because the questions repeat, you can see whether the goal rating or the priority rating is moving across sprints. One sprint on its own tells you very little.
Mistakes to avoid
Ways a retrospective survey loses the team
Asking who caused the problem
Who missed the deadline turns a retrospective into a performance review, and people stop writing honest answers. Ask about the work, the handoffs and the process.
Sending the form when the meeting has already started
Notifications follow the hourly processing run in production. Send the form a day before, so the facilitator has read the answers when the meeting begins.
Asking more than the team will read
A long form with several open boxes can get thinner answers and a slower read. Keep it to the questions you will work through before the meeting.
Promising anonymity you cannot keep
A name field can be left blank, but a team of six can still tell who wrote a sentence. Say who will read the answers, and do not call the form anonymous.
Ending without a visible action
A retrospective that produces a list but no action can teach the team to stop answering. Record the chosen actions where the team tracks its work, and report what happened to last sprint's actions first.
Frequently asked questions
What should a sprint retrospective survey ask?
Ask how well the sprint goal was met, what went well, what slowed the work down, how clear the priorities were, and what one change to try next. Keep the same questions each sprint, so the answers can be compared over time.
Do I need special software to run a sprint retrospective?
No. A retrospective needs a short set of questions, a meeting, and an owner for each action. This form collects the input before the meeting. Attain OS builds it as a link the team answers on a web page, and it does not replace the discussion.
Should the sprint retrospective be anonymous?
The name field is optional, so you do not have to collect names. A team small enough to run a retrospective can still recognize a writer from the wording, so do not call the form anonymous. Tell the team who will read the answers before the meeting, and keep that promise.
How far ahead should the retrospective form go out?
Send it at least a day before the meeting. The form's creator hears about each response only after the hourly processing run in production, so a reply sent minutes before the meeting may arrive too late to read.
Browse by category
More surveys in Product & Engineering
Surveys
Third-Party Vendor Evaluation
Surveys
Product Feedback
Applications
User Research Screener
Requests
API Access Request
Requests
Architecture Review Request
Applications
Beta Tester Signup
How to build it
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.
