Conversational Story

One of the most prominent misconceptions that we can see within agile environment is assuming that the product owner is creating user stories and placing them in front of all the developers to work on. This would highlight the fact that the product owner is responsible for understanding what has to be done and the product owner communicates with the developers on how it has to be done.

However, this approach is quite different in the real world. The product owner is aware about the business and he has a good understanding about the need for software. On the other hand, the developers are versed with technology and they know how to implement things. Hence, it is possible for the developers to figure out the requirements put in front of them by the product owner.

To overcome all sorts of misconceptions associated with this process, it has become important for the product owners to use Conversational Stories. A Conversational Story will help the developers to get a better understanding on what has to be done to support a business.

There are some unique qualities that you can find within a Conversational Story. For example, it would spot the gaps and inconsistencies that exist in between the stories. On the other hand, it would use technical knowledge to offer new stories, which would fit perfectly well to the vision of the product owner. It is even possible to use Conversational Stories as the base and look out for alternative stories, which can be cheaper to develop based on the existing technological landscape. On the other hand, it is possible to split the stories further, so that it is possible to plan and implement easily. Due to all these reasons, the process of creating Conversational Stories can be considered as something that would help people to invest on the stories.

— Slimane Zouggari