Two Types of Scrum
I’ve come to realize recently that there are two types of Scrum. One is goal-driven, the other is story-driven.
The Story-Driven Scrum
This approach seeks to identify and prioritize user stories (or any requirements) small enough to fit in the iterations. In these Sprints, the team commits to delivering the selected set of stories. These stories can be estimated and the amount of results can be measured for longer term planning. This approach works best when enough design work can be done in advance to eliminate most significant elements of uncertainty prior to committing to work in a Sprint. I could call this type the Mike Cohn Scrum as this approach is excellently defined in his Agile Estimation and Planning book.
The Goal-Driven Scrum
This approach sets a goal, or a problem or a challenge, for the team to solve during the sprint. The commitment is to solving the problem, not so much on the characteristics of this solution. The goals are harder to measure and therefore it is more difficult to gain information on the team performance for future planning, but the whole approach is geared toward research and problem solving, both of which are by nature impossible to estimate accurately. I could call this type Ken Schwaber Scrum, or maybe Takeuchi-Nonaka Scrum, as this approach was quite prevalent in the original Scrum texts and especially in the Takeuchi & Nonaka article The New New Product Development Game where Scrum was first described.
There is a lot of experience of story-driven Scrum in the world out there. Majority of Scrum implementations are of this type. However, I’ve recently come to perceive this approach as potentially the weaker type of Scrum. I guess I have to explain.
The power of Scrum is in transformation and innovation. The more cross-functional the Scrum team, the greater is its power for said innovation. The more leeway the team has in solving the problem, the greater is its potential for finding breakthrough solutions. The very extreme is the team described in The New New Product Development Game article that was given three months of time, full support, and the goal of developing a new product for the market. The team itself had all the expertise needed to understand the problem, explore solutions and deliver the goal.
The difficulty with goal-driven Scrums is that they require much more transformation from the organization than story-driven ones. Goal-driven Scrums force the involvement of most or all functions in an organization. Much more rapidly, the organization must face redesign of the way it works. I bet it will fail rapidly if the Agile values are not embraced at all levels and functions of the company.
The story-driven approach is much more-forgiving to the organization. In it, the development teams can be pretty much like development teams have been in the past, primarily consisting of software developers of various roles. They can also be fed quite similar problems (just transformed into stories). While doing that well will result in significant improvements in several ways, it still more easily allows sticking to old paradigms. All of this is obviously dysfunction, but that is not so apparent to many organizations.
When looking at most contemporary Scrum teams, they are typically quite homogenous in terms of skill sets and background (e.g. software developers). While there can still be significant differences between team members, we rarely see people with marketing, sales or domain expertise (except in the very good Scrum teams). The “Agile transformation” has been nicely constrained to the development group. As a result, these teams must receive pretty well-defined work. The capability to innovate entirely new solutions is very constrained.
Unfortunately, there isn’t a clear pattern how a goal-driven Scrum would operate. Many Scrum and Agile trainers don’t teach about its existence. I know I haven’t. I should, at least to open up minds to its existence, but I’m really short on time as it already is with the CSM course. There are so many topics already that adding that might prove impossible. Yet I think I should, somehow.
I believe the goal-driven Scrum would be instrumental in transforming organizations beyond product development.