In our current project, a software for managing sports events, user stories play an important role when it comes to development. Interestingly the focus of the requirements conversation changed completely from one level of maturity to the next. And there is a pattern behind it, as it seems. It leads to story mapping.
A few days ago, we had a discussion about Scrum and one person asked the question if it really isn’t possible to run effective estimation meetings with 16! persons involved. If you have an answer ready, wait. Once the problem becomes clearer, the solution is getting more interesting. It may rather be a question of maturity than of team size.
Pin the maturity cards on the wall. Ask how well do we foresee the change we’re going to inflict with the planned features. “Customers will love it”, the engineer proclaims putting the features on tree level. The sales rep sourly adds: “If they’ll ever grasp it”, moving them up into the clouds.
Ask this question in a workshop to a round of engineers and product managers. After a few blank stares you will start hearing comments like “we’re ready to build it”, or “they’re pretty sound”, and “well, we actually have no idea what this is all about”. Quite often we hear completely different opinions about the same item. Try it yourself, it works. Stunning, isn’t it?