- Published
- 8 October 2026
- Last reviewed
- 8 October 2026
How to use these FAQs
Clarify a need, define scope and make acceptance conditions observable before agreeing a change.
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
Is a requested feature already a requirement?
A feature request is a useful starting point, but it may describe a preferred solution rather than the underlying need. Ask what the person is trying to achieve and what happens today. A fictional request for a dashboard might reflect missed urgent enquiries. Record the need separately so that the team can compare possible ways to address it.
How do I make scope clear?
Describe what the proposed work includes, what it excludes and which users or situations it covers. Record important dependencies and assumptions. For a fictional form update, the work might include validation messages but exclude a new payment service. Ask the relevant decision maker to resolve unclear boundaries before effort is committed, and keep the agreed version available.
What makes an acceptance criterion useful?
It states a condition that someone can check. Replace “the form is easy” with a specific expected behaviour for a defined situation, such as showing an explanation when a required field is empty. Include relevant failure and access needs as well as the normal route. The criterion should help a reviewer decide what evidence to gather.
Are acceptance criteria the same as a Definition of Done?
They serve different purposes. Acceptance criteria describe conditions for a particular item. In Scrum, the Definition of Done describes the quality state required for an Increment. An item-specific condition does not remove wider quality requirements. Check how your team uses these terms and avoid treating a local approval checklist as the official Scrum definition.
What should happen when a requirement changes?
Record the proposed change, why it is needed and its effect on related work. Discuss effort, dependencies and any agreed delivery boundary with the appropriate people. Keep the decision and the current version traceable. Do not silently edit the only copy and expect everyone to know that a previously agreed condition has changed.
Who decides whether the work is acceptable?
The decision depends on the organisation and delivery arrangement. Identify who can approve the relevant outcome and who provides evidence or advice. A tester may report results without holding commercial acceptance authority. Record responsibilities early so that a completed test, stakeholder preference and formal approval are not confused with one another.
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.
- IIBA: Understanding requirements and designs
- GOV.UK: Writing user stories
- Scrum Guides: Definition of Done
Cover image: AI-generated illustrative scene created specifically for this resource.