- Published
- 8 October 2026
- Last reviewed
- 8 October 2026
How to use these FAQs
Understand Scrum accountabilities and use delivery conversations to inspect work and agree useful next steps.
Select a question to expand its answer. The first answer is open initially; each answer can be opened or closed independently. These are original RDE practical explanations. Any example described as fictional is a teaching scenario.
Common questions
Does agile mean using Scrum?
No. Agile approaches are broader than one framework. Scrum provides a particular structure of accountabilities, events and artefacts. A team using a task board or short meetings is not necessarily using Scrum. Describe the approach your team actually follows, and consult the Scrum Guide when you need to understand what the framework specifies.
What are the Scrum accountabilities?
A Scrum Team includes Developers, a Product Owner and a Scrum Master. The Product Owner is accountable for maximising product value; the Scrum Master is accountable for establishing Scrum. Developers are accountable for creating a usable Increment each Sprint. These accountabilities are not a template for every organisation’s job titles or reporting hierarchy.
Is the Daily Scrum a manager status meeting?
The Scrum Guide describes it as an event for Developers to inspect progress towards the Sprint Goal and adapt their plan. It is not defined as a reporting round to a manager. A practical discussion might identify a dependency that needs action today. Use other arrangements for reporting needs rather than replacing the event’s purpose.
What is a useful Sprint Goal?
It gives the Sprint a coherent objective rather than simply listing unrelated tasks. In a fictional booking product, the goal might be enabling a user to confirm an available session reliably. The selected work should support that objective. Keep the goal visible when discussing adjustments so that changing a task does not quietly change the intended outcome.
How are a Sprint Review and Retrospective different?
A Review inspects the Sprint outcome with stakeholders and considers future adaptations. A Retrospective focuses on improving how the Scrum Team works. Showing a feature is not the whole Review, and discussing a process problem does not replace reviewing the product outcome. Use each event to produce an appropriate next decision or improvement.
What should I do when work cannot be finished?
Make the situation visible, discuss its effect on the goal and follow the team’s agreed process. Do not label unfinished work as done to keep a chart looking tidy. Record what remains and why. In Scrum, the quality requirements in the Definition of Done still apply; incomplete work does not become a usable Increment through a status change.
Put one answer into practice
Choose the question closest to your current task. Write one action in your own notes, identify the information or permission you need and set a review point. Use the related resources below to develop the task further. No response is submitted or stored by this page.
Sources and scope
The sources below provide relevant context and terminology. The examples, practical suggestions and wording are original RDE teaching material. Apply your organisation’s policies and the guidance relevant to your situation. Reviewed 8 October 2026. Author: Jefferson Otonbara Imgbi.
Cover image: AI-generated illustrative scene created specifically for this resource.