Using "Cucumber Without Gherkin" as a Heuristic for Writing User Stories

The Power of Storytelling

Storytelling is a fundamental aspect of human communication. It allows us to share experiences, convey complex ideas, and connect with others on a deeper level. In the context of software development, storytelling can be a powerful tool for bridging the gap between technical and non-technical team members. By framing requirements and goals as stories, we can ensure that everyone involved has a clear and shared understanding of what needs to be achieved.

What is Cucumber?

Cucumber is a tool used in Behavior-Driven Development (BDD) that allows developers to write tests in plain language. These tests are written in a format called Gherkin, which uses a simple syntax to describe the behavior of the application. A typical Gherkin scenario might look like this:

Feature: User login
  Scenario: Successful login
    Given the user is on the login page
    When the user enters valid credentials
    Then the user is redirected to the dashboard

Simplifying with "Cucumber Without Gherkin"

While Gherkin is already quite readable, it can still be too technical for some stakeholders. "Cucumber without Gherkin" strips away the formal syntax and focuses on the core elements of a user story: the context, the action, and the outcome. This approach can be particularly useful for non-technical people who need to convey their vision or requirements without getting bogged down in technical details.

How to Use This Heuristic

1. Identify the Context: Start by describing the situation or context in which the user finds themselves. This sets the stage for the action that will follow.

   • Example: "The user is on the login page."

2. Describe the Action: Next, outline the action that the user will take. This should be a clear and concise description of what the user does.

   • Example: "The user enters their username and password."

3. State the Outcome: Finally, describe the expected outcome of the action. This helps to clarify what should happen as a result of the user's action.

   • Example: "The user is taken to their dashboard."

By breaking down user stories into these three simple components, non-technical people can more easily communicate their ideas and requirements. This approach ensures that everyone on the team has a clear understanding of what needs to be built and why.

Examples of "Cucumber Without Gherkin" User Stories

To illustrate this approach further, here are some examples of user stories using the "Cucumber without Gherkin" method:

Social Media Post

• Context: The user is on their profile page.
• Action: The user writes a new post and clicks "Publish."
• Outcome: The post appears on their timeline.

Email Subscription

• Context: The user is on the website's homepage.
• Action: The user enters their email address in the subscription box and clicks "Subscribe."
• Outcome: The user receives a confirmation email.

Communicating a Sale

Here's how you can use the "Cucumber without Gherkin" approach to communicate different aspects of a sale:

Announcing a Sale

• Context: The user is browsing the homepage of an online store.
• Action: The user sees a banner announcing a 20% off sale on all items.
• Outcome: The user clicks on the banner and is taken to the sale section of the website.

Receiving a Sale Notification

• Context: The user is checking their email.
• Action: The user opens an email announcing a flash sale.
• Outcome: The user clicks the link in the email and is directed to the sale page on the website.

Benefits of This Approach

• Clarity: Simplifying user stories in this way makes them easier to understand for everyone involved, reducing the risk of miscommunication.
• Accessibility: Non-technical stakeholders can contribute more effectively to the development process, ensuring that their vision is accurately captured.
• Efficiency: Clear and concise user stories can speed up the development process by providing developers with a straightforward description of what needs to be done.

Conclusion

Using "Cucumber without Gherkin" as a heuristic for writing user stories can be a game-changer for teams with non-technical members. By focusing on the context, action, and outcome, this approach makes it easier for everyone to understand and contribute to the development process. Whether you're explaining your vision or detailing specific requirements, this method can help ensure that your user stories are clear, concise, and effective.