AgileBlooper1 – Stories Too Detailed Mate.
Post Statistics
This post has 392 words.
This post has 2348 characters.
This post will take about 2 minute(s) to read.
Banks, your user stories are too detailed!!
What’s A User Story?
User stories are drivers for a conversation within the scrum team. They are not carriers of perfection or nuggets of glory. A user story is a negotiation and a compromise of sorts to help drive the team to deliver a piece of work within a time box. This assures order, manages stakeholder expectations and provides visibility on the piece of work.
In this scenario, a member of the scrum team called me aside and personally told me that my stories were too detailed. I went through the whole shock life cycle till I came to the place of empathy. I decided to respond to what should be the perfect user story. I also reminded my colleague that user stories drive negotiation within the team and is a continuously evolving, value adding tool to help the team and the business continuously add value.

It is noteworthy to remember that user stories are not requirements – they only seek to explain and are planning tools for delivering requirements. Not every requirement can be delivered via a user story. Per Lundholm in his write up explained that “User stories are about being able to explore options and seize opportunities. Requirements are about deciding up front and sticking with that” and I sincerely and wholeheartedly agree with that.
While there are rituals and ceremonies within an agile delivery team to help drive and seal direction for the sprint goals, there is also the need to constantly define and redefine the goal where necessary. Changes within the market that is outside the control of the business is a major reason for this. The business wants to remain customer centered and must respond to the changes evolving as such. Also, it in these ceremonies that true negotiation occurs and this includes grooming the stories for value and adaptation to the sprint goal
So when next you are told that your requirements are too detailed, sit back, relax and ask for a negotiation meeting with the whole team. Why? its because user stories are negotiable!!