Specification by Example

5 minutes 5 Questions

Specification by Example (SBE) is an Agile Testing approach that involves defining requirements and acceptance criteria through realistic examples rather than abstract statements. In SBE, developers and testers work closely with product owners and stakeholders to create a shared understanding of th…

Guide on Specification by Example

Specification by Example (SBE) is an agile practice that aims to reduce miscommunication between project stakeholders by using examples to clarify the expected behavior of any system or system part.

Importance of Specification by Example:
SBE helps to close the gap between domain experts and software developers, providing a common language that everybody can understand. It encourages active and consistent collaboration, stimulating regular feedback and improvements. It also allows early testing, reducing the risk of bugs and other issues later in the project.

Understanding Specification by Example:
In SBE, requirements are turned into executable specifications that are written before the software is implemented. These specifications show how the system should behave with concrete examples. This makes it easier to verify that the system is implemented correctly and that it meets users' needs.

How Specification by Example works:
1. Identifying examples: The development team, along with the stakeholders, collaborate to identify real-world examples that describe the desired functionality.
2. Illustrating specifications: These examples then illustrate the specifications of the system.
3. Turning examples into automated tests: The examples are then turned into automated tests.
4. Checking the system behaviour: The tests are used to validate the implemented system or feature against its expected behaviour.

Exam Tips: Answering Questions on Specification by Example
1. Understand the basics: Ground your understanding in the basics of SBE including its purpose, importance and workflow.
2. Use real-world examples: Most exam questions will have scenarios or case studies where you have to apply SBE. Take the time to understand these examples and how they relate to the topics you have studied.
3. Refer to agile principles: As a part of Agile project management, SBE operates under general Agile principles. Understand Agile processes and how they relate to SBE.
4. Practice: Practice multiple choice and essay questions about SBE to get a feel for what may be asked on the exam.

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

Question 1

Your team has completed a project using Specification by Example. What's the best way to maintain and utilize examples for future projects?

Archive all examples separately from the project for safekeeping. Turn the examples into user stories. Treat them as living documentation that can be updated, shared, and referred to by the team. Rely on team members’ memory and personal notes. Use the same examples for other projects without adaptation. Discard the examples as they are only relevant to the completed project.

Correct Answer: Treat them as living documentation that can be updated, shared, and referred to by the team.

Specification by Example is most effective when examples are maintained as living documents that are continuously refined and can be used as a reference for future projects. Discarding or relying on memory makes them less useful and reliable.

Question 2

In a team meeting, stakeholders are having difficulty defining a feature using specification by example. What is the best way to facilitate the conversation?

Ask the team to expand the feature into multiple smaller features. Encourage the team to come up with concrete examples as scenarios. Delegate the task to only one member. Ignore the difficulty and move on to the next feature. Tell the stakeholders to figure it out later. Ask the stakeholders to define the feature in abstract terms.

Correct Answer: Encourage the team to come up with concrete examples as scenarios.

By asking team members to think of concrete examples as scenarios, you're helping them visualize and understand how the feature will work. Abstract definitions or delaying discussion won't provide the desired clarity.

Question 3

As a product owner, you're reviewing specifications written by the team. You come across an example that is unclear and not easily understood. What should you do?

Ask the team to vote on a rewrite. Discuss it with the team members and ask them to revise the example for clarity. Delete the unclear example and move on. Rewrite the example yourself without the team's input Leave the example as it is. Postpone clarification for a later project phase.

Correct Answer: Discuss it with the team members and ask them to revise the example for clarity.

To ensure clear and easily understandable specifications, it's crucial to address unclear examples with the team and ask them to revise it collectively. Ignoring it or making changes without the team's input can cause confusion or inconsistency.

🎓 Unlock Premium Access