There’s a nasty misassumption in common Agile practice: that there’s a single person responsible for writing stories and conducting all these story conversations. In the Agile process Scrum, that person is called the product owner. There are two big reasons, however, why this logic doesn’t work, and probably a lot of smaller reasons, too.
Requiring a single product owner to write all of the stories and be present for all story conversations doesn’t work.
Don’t get me wrong here. In my vision of good product development, the product owner is a critical leader. He keeps the product and whole team focused on moving the same direction.
The alternative is design by committee—a seriously bad anti-pattern where everyone gets an equal say in what we do. In a committee, when we only have time and resources to do one thing, we compromise. My ex-wife and I would often do this when choosing a ...