Practical Cucumber: Stakeholders

This post is part of our Practical Cucumber series.

A common criticism of Cucumber is that clients and stakeholders never actually write the scenarios, and making developers write them is a waste of time.

The stakeholders might not care

The pipe dream of agile development is that stakeholders and developers will harmoniously unite and write perfectly crafted acceptance criteria. But it is very unlikely that clients or stakeholders will write—let alone care about—cucumber scenarios.

We have had a few clients that have tried writing cucumber scenarios, and they did a horrible job. However, a horribly written cucumber scenario is infinitely better than a one-line description of a feature. The client’s attempt to describe the feature in a strict language forces them to think more deeply about the feature, and in the process answer questions that a developer would likely be asking when implementing the feature.

Why developers should still write them

Even if the stakeholder doesn’t participate in writing cucumber scenarios, there’s still value in having developers write them. Thinking about features from the end-user’s perspective forces us to think first about the experience of using our software, and second about implementation. It brings issues to the surface that we might not have otherwise thought about, and helps us write the least amount of code possible to meet the requirements.

This post is part of our Practical Cucumber series.

brandon@opensoul.org

Comments

Add a Comment

Hmm...that didn't work.

Something went wrong while adding your comment. If you don't mind, please try submitting it again.

Comment Added!

Your comment has been added to this post. Please refresh this page to view it.

Optional. If added, we will display a link to the website in your comment.
Optional. Never shared or displayed in your comment.
  1. May 21, 2011 at 6:56 AM

    I’ve always thought of Cucumber features as something that clients can READ, not write. You, the developer, talk to the client, try to understand the requirement, and then you write a cucumber feature, show it to the client, asking - have I understood this correctly? Then implement. 

    Having clients write them just seems stupid. I’m still looking for a tool that nicely visualizes the cucumber features of a project, any tips?

  2. May 21, 2011 at 9:11 AM

    Yep. While it would be great if clients wrote them too, we haven’t seen that happen yet. 

    We show them to the clients, and even then not all the time. Only when they have an interest or we need clarification.

  3. August 13, 2012 at 7:31 AM

    Well, I have worked as consultant for a long time and have taken up projects from all around the world. Back then when I did not know cucumber, I remember coming across requirements where people offered cucumber features as requirement specifications.

    So it is not just about clients now, companies who are outsourcing part of the project would also get a great help with this.