Not happy with the user stories your product owners or business analysts are writing? Speak up.
I don’t mean that in a rebellious way. I mean it collaboratively.
Let them know where you’re having trouble understanding to produce and deliver results.
Think a different choice of words would clear things up? Consider writing them yourself. Put it down in your own words.
Share it with the team and see if it brings clarity for everybody. It may or may not resonate with others. Pay attention.
The people writing the stories may be fighting their battles and are thankful to see better deliverables, regardless of reworded stories that facilitated communication and collaboration.
User stories aren’t requirements. They’re placeholders for conversation. You’ve heard that before.
With good conversations, stories don’t have to be fully spelled out. Some details can be left out. Too much detail may leave too much room for (mis)interpretation.
Don’t understand the meaning of a word within the context? Ask for clarification.
Don’t understand the context? Ask.
Need different perspectives to understand the context? Ask.
A coder might be able to offer solutions to the problem a story means to solve. So can a UX designer. Or a QA team member. In the context of a scrum team, they’re all developers. Let’s develop great stories.
Great stories are told and retold.
Great stories yield great products.
Great products are talked about, over and over.
Leave a Reply