What If We Could Use The Code To Write Our User Stories?

We often see the code as the outcome of the user stories, but what if we could turn it around? What If we could make our code work as well for the team?

David Rodenas PhD

--

A robot ready to write your User Stories, by DiffussionBee

The writing of user stories, might seem an easy task, but it has several challenges. Nevertheless, they often progress because all members in the team collaborate to overcome any problem, not without friction. We want to reduce any difficulty, and made all the process the most smooth possible.

Three of the challenges of user stories are:

  • Everyone on the same page: That is a huge challenge. When we write a user story, it is not only writing well all the details, but making everyone understand the same thing. User stories are written in plain English, but English is a human language, full of ambiguities and assumptions. It is the reader who adds its own knowledge and context to fill the gaps and clear ambiguities. And that creates a different user story for every team member. Consequently, the result is not what is imagined, QA raises unexpected bugs for the developers, and we end facing several reworks, delaying all the release.
  • Up-to-date documentation: Developments grow, and sooner than we realize, we have plenty of user…

--

--

David Rodenas PhD

Passionate software engineer & storyteller. Sharing knowledge to advance our skills. Join me on a journey of discovery in the world of software engineering.