After reading this great piece two things from other great minds came to my head. David Pereira writing that great PMs write shitty stories and Niels Davis with VALUABLE framework for requirements and his comparison to popular INVEST. When art goes over substance you’re probably ears deep in a hard feature factory. For me writing stories was always a pain. I very much prefer continuously discussing and working together to make sure all parties are aligned and have the same understanding.
Excellent post. I can remember telling POs who asked me to help them write "better user stories" to write worse ones. It either worked, or they thought I was mad, and fired me. I'd see that as win-win ;)
User stories have always been a token for discussion, Maarten Dalmijn. It is about alignment, the why/what/how, not about efficiency in creating artifacts.
After reading this great piece two things from other great minds came to my head. David Pereira writing that great PMs write shitty stories and Niels Davis with VALUABLE framework for requirements and his comparison to popular INVEST. When art goes over substance you’re probably ears deep in a hard feature factory. For me writing stories was always a pain. I very much prefer continuously discussing and working together to make sure all parties are aligned and have the same understanding.
Excellent post. I can remember telling POs who asked me to help them write "better user stories" to write worse ones. It either worked, or they thought I was mad, and fired me. I'd see that as win-win ;)
User stories have always been a token for discussion, Maarten Dalmijn. It is about alignment, the why/what/how, not about efficiency in creating artifacts.
This is the essence of user stories! This is why I consider a definition of done s as a helpful suggestion, but the tag value lies in the discussion.
Agreed.