Free download: 200 User Story Examples
Participants in my Certified ScrumMaster courses are often surprised when I recommend that programmers participate in story-writing workshops. After all, a story-writing workshop is a meeting targeted at determining the functionality to be built next. I like to do story-writing workshops about quarterly to focus on bigger initiatives. But some projects will do story writing every sprint.
Regardless of how often these meetings occur, I think it's vital that programmers, testers, database engineers, and so on participate. Collectively I refer to individuals in any of these roles as developers, and I think there are four critical reasons to include developers in story-writing meetings.
Reason 1: Increased Engagement
The first reason I like to include developers is that doing so increases the engagement of developers. You want your developers excited about, bought into, and engaged with the product being built. A team with developers who come to work with no passion or interest in what they’re developing will not perform at its highest level.
Involving developers in story writing allows them an opportunity to contribute to discussions about what is being built. It’s unlikely their ideas will be as good as those of the product owner or most others with a deeper understanding of the business and its customers, but still important enough to be heard.
Reason 2: Increased Learning
How did the business people get that deeper understanding of the business and its customers? By spending time thinking about the product, the business or its customers.
Bringing developers into story writing workshops gives them that opportunity. And this is our second reason for including developers: The more they are involved, the more they’ll learn. Over time, you may just find that some of the best ideas are coming from the developers.
Reason 3: It Doesn’t Cost as Much Time as You Think
A common objection to involving developers is that they don’t have the time to spend in yet another meeting. Fortunately, some of the time spent in the actual meeting is saved in coming sprints because the developers will have fewer questions.
When the developers are there when ideas are generated, they will have fewer questions about why customers want something, if there are other ways to satisfy that need, and so on.
There is a time cost to having developers in these meetings, but it’s not as great as you might think. And the other advantages outlined here more than make up for the investment.
Reason 4: It Leads to Increased Creativity
A final reason for including developers in story writing is the increased creativity it will lead to. With more people thinking about ways to make your product the best it can be, the product owner will have more ideas to choose from when prioritizing.
I find this especially true because developers often have such different ways of thinking about a problem than the business people do. Neither one is superior. It’s the diversity of backgrounds, skills, and ways of thinking about a problem that creates the best solution for a product’s users.
Have I Missed Some?
I'm sure I've missed some. What other reasons do you have that support having programmers (and other technical people) participate in story writing meetings?