Practice sprint demo feedback vocabulary: stakeholder acceptance, conditional approval, PO rejection, new requirements triggered by demos, and capturing feedback in Jira.
0 / 14 completed
1 / 14
A stakeholder says 'I like the feature but I want to change the label on the export button'. How should the team handle this?
When a story meets its acceptance criteria, it can be accepted. Minor feedback like a label change is captured as a new backlog item — this keeps the sprint review focused and avoids scope creep mid-demo. The PO decides priority for the follow-up item.
2 / 14
A PO says 'accepted with one condition: the error message must be updated before release'. What is the correct team response?
'Accepted with one condition' means the story is done but has a minor outstanding item that must be resolved before going to production. The team logs this as a task or bug, not a full story rejection, and addresses it before the release gate.
3 / 14
During a demo a stakeholder says 'this is great — but seeing it makes me realise we also need X'. What vocabulary describes this?
Demos frequently surface new requirements because stakeholders can react to working software in ways they couldn't to a written spec. These demo-triggered requirements are valuable — they're captured in the backlog, not added to the current sprint.
4 / 14
The PO says 'I'm rejecting this story — the flow doesn't match the agreed acceptance criteria'. What should happen next?
If a story doesn't meet its acceptance criteria, the PO can reject it. The story goes back to the backlog with clear notes explaining why it was rejected and what needs to change. It will be re-estimated and scheduled in a future sprint.
5 / 14
A team says 'the demo feedback is captured in Jira'. What does this mean practically?
Capturing demo feedback in Jira means any new requirements, change requests, conditional acceptances, or follow-up tasks raised during the demo are immediately logged as tickets. This ensures feedback doesn't get lost and is visible to the whole team in the backlog.
6 / 14
Sarah (the QA engineer) comments on a PR: 'The automated tests are failing consistently after this change. It seems like there's an issue with the data validation.' What does Sarah likely mean when she says 'data validation'?
Sarah's comment refers to 'data validation,' which means the system isn't properly checking if the data being processed meets predefined rules – for example, ensuring a number falls within an acceptable range or that a string matches a specific format. The misconception is often thinking of it as performance issues, debugging, or database problems; data validation specifically focuses on input integrity.
7 / 14
During a Slack conversation about the new user onboarding flow, David says: 'This is fantastic! But I'm struggling to understand how to add my company logo. The UI isn't intuitive.' What does David *really* mean?
David's comment highlights a usability issue – his statement about 'intuitive UI' indicates that the user interface isn't easy for users to understand and navigate. He's not necessarily criticizing the code itself but rather the design choices impacting the user experience. Options A, C, and D are related to technical problems, not usability.
8 / 14
The development team is preparing a PR description for a feature update. Maria suggests: 'We've incorporated the new API endpoint and added basic error handling.' What vocabulary best describes this situation?
Maria's phrasing – 'minimal functional solution' – indicates that the team delivered a basic version of the feature meeting the essential requirements but without extensive optimization or redesign. This is common in early sprints and PR descriptions, acknowledging that further refinement can come later. The other options represent more significant changes.
9 / 14
The team uses Jira to track sprint tasks and bug reports. A stakeholder asks: 'Can you update me on the progress of this feature?' What does the team *really* mean when they say 'update you' in this context?
When the team says 'update you,' they mean providing information about the feature's status *within Jira*. This involves sharing the relevant ticket – showing its progress (e.g., 'In Progress', 'Resolved'), assigned tasks, and any outstanding issues tracked in the system. The other options represent different forms of communication beyond the standard Jira update.
10 / 14
Mark says during the sprint demo: 'The integration with the third-party service is working perfectly. However, I'm noticing a slight delay – around 3 seconds – when retrieving user data. It's impacting the overall responsiveness.' What does Mark *most* likely mean when he mentions 'a slight delay'?
Mark is highlighting a performance issue – latency. A 'delay' in this context refers to an unacceptable amount of time taken to retrieve data, negatively affecting the user experience. The options incorrectly suggest approval or security reasons; Mark's focus is on responsiveness.
11 / 14
During a Slack discussion about a newly deployed feature, Emily types: 'Just ran the smoke tests – all green! Looks good for now.' What does Emily *primarily* mean when she says 'all green'?
'All green' in this context refers to passing automated tests. It's a shorthand for indicating that the initial smoke or sanity tests have passed without raising any immediate concerns – it doesn't guarantee complete functionality or absence of future issues.
12 / 14
The development team writes in a PR description: 'This change refactors the authentication module for improved maintainability and adds support for OAuth 2.0.' What does the phrase 'refactors the authentication module' mean?
'Refactoring' means improving existing code without changing its external behavior. In this case, it describes restructuring the authentication module – likely simplifying or cleaning up the code – to make it easier to maintain and update in the future. The other options misinterpret the term.
13 / 14
During a standup meeting, John says: 'I'm blocked on getting feedback from the design team regarding the new UI elements. They haven't provided their input yet.' What does John *really* mean when he says he is 'blocked'?
To be 'blocked' means that John's progress is halted due to an external dependency or lack of information. He cannot proceed until he receives feedback from the design team; this represents a critical impediment to his workflow.
14 / 14
A stakeholder emails: 'This feature looks great on mobile, but I'm concerned about how it will appear on larger screens. Can you please prioritize testing on different resolutions?' What does the stakeholder *primarily* need from the development team?
The stakeholder's concern focuses on responsiveness – how the feature adapts across different screen sizes. 'Prioritize testing on different resolutions' directly requests that the team conduct usability tests to validate the feature's appearance and functionality on various devices.
What will I learn from the "Sprint Demo Feedback Vocabulary" exercise?
Practice sprint demo feedback vocabulary: stakeholder acceptance, conditional approval, PO rejection, new requirements triggered by demos, and capturing feedback in Jira.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 14 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Sprint Demo & Releases exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss sprint demo & releases topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 14 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Sprint Demo & Releases exercises?
See the full Sprint Demo & Releases exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.