5 exercises — sprint, backlog, velocity, retrospective, epic, and more terms your whole team uses every day.
0 / 10 completed
1 / 10
In Scrum, a sprint is best described as:
A sprint is a time-boxed iteration — typically 1 to 4 weeks — during which the Scrum team works on a set of selected backlog items and produces a working, potentially shippable increment.
2 / 10
Complete the sentence: "The team couldn't complete all the stories — they had too much work in the _____, so items were pushed to the next sprint."
The sprint backlog contains the work selected for the current sprint. If items are not completed, they return to the product backlog for re-prioritisation.
3 / 10
Which term means "the measure of work a team can complete in a single sprint"?
Velocity is the average number of story points a team completes per sprint, used to forecast future work capacity. A burndown chart shows daily progress within a sprint.
4 / 10
A retrospective is a Scrum ceremony where the team:
The sprint retrospective (retro) is focused on the team's process, not the product. The team discusses what went well, what didn't, and what to change. It's different from the sprint review (demo to stakeholders).
5 / 10
"We need to break this epic into smaller stories." In Agile, an epic is:
An epic is a large feature or requirement that is too big to complete in a single sprint. It is decomposed into smaller user stories (or simply stories) that can be estimated and completed within a sprint.
6 / 10
During a code review of Sarah's pull request for the new user authentication module, Mark comments: 'This implementation doesn't handle edge cases related to expired tokens. We should add error handling and logging to improve robustness.' What does Mark suggest the team *immediately* focus on?
Mark is advocating for a pragmatic response within the Agile framework – immediate action based on a clear impediment. He's not suggesting fundamental architectural changes (option A) or delaying until planning (option C). While testing (option D) is valuable, Mark specifically requests error handling and logging, directly addressing the identified vulnerability to improve robustness; this aligns with iterative improvement principles.
7 / 10
In a Slack channel dedicated to the 'Phoenix' project, David writes: 'Just finished implementing the new API endpoint for retrieving user profiles. Response time is averaging around 300ms – we need to investigate and aim for under 150ms in production.' What does David primarily focus on when discussing performance?
David's message centers on *response time*, specifically latency. While server costs (option A) and user concurrency (option D) are factors influencing performance, they aren't the direct focus of his immediate concern. Accuracy (option B) is a separate quality consideration. The core issue is the 300ms response, indicating a need to optimize the code execution itself – this aligns with Agile's emphasis on iterative improvement.
8 / 10
The API response for a user profile request returns JSON data like: `{"user_id": 123, "username": "john.doe", "email": "john@example.com"}`. What is the primary meaning of this response in the context of Scrum velocity and sprint goals?
The API response delivers *functional* data – in this case, confirming the backend service is returning user profile details. This information feeds into velocity calculations and helps teams understand their throughput. While related to sprint goals (option A), the API response itself doesn't inherently represent a completed story or directly estimate capacity; these are derived from analyzing the data.
9 / 10
During a daily standup meeting, Liam says: 'Yesterday, I worked on implementing the user authentication flow. I ran into some issues with OAuth2 integration and spent most of my time debugging.' What does Liam primarily communicate during this update?
Standup updates are meant to be brief and focused on *progress* and impediments. Liam's statement highlights what he worked on (authentication flow) and the challenges (OAuth2 debugging). This aligns with Agile's emphasis on transparency and identifying issues that might impact the sprint – a concise update of tasks is key.
10 / 10
In an Agile project, a large user story describing all features related to 'customer onboarding' is often referred to as an ______. The team will then break this down into smaller, manageable stories for individual sprints.
An 'epic' is a large user story that's too complex to be completed in a single sprint. It represents an initial scope and needs to be broken down into smaller, more manageable stories – this aligns with Agile's iterative approach to development and prioritization. A release candidate (option A) is a tested build, technical debt (option B) refers to the implied cost of rework required due to hasty coding; an MVP (option C) is a version with just enough features to satisfy early customers, and a 'minimum viable product' is a product containing only the features necessary for the initial release.
What does the "Agile & Scrum Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to agile & scrum vocabulary through 10 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.