Sequence the Features
The purpose of a Minimum Viable Product is to create a product that we can use to validate a small set of assumptions about a product and it's role in a business. Now that we have a map of features integrated with user journeys, we are in a position to work out the first MVP and its following iterations. We do this by defining a Features Sequencer
An example of a features sequencer
How we do it
- Create the Features Sequencer template (typically a flipchart with numbered lines; the line height should fit one feature card, the line width should fit three feature cards).
- Explain the feature sequencer rules.
- Remind everyone about the activity goal: To define the sequence that we will deliver the features of the product. Our goal with an MVP is to learn from each iteration by building an MVP that will allow us to test if our business case is effective.
- Everyone places the feature cards on the sequencer, moving them around as we explore the options, until we reach an agreement.
- The result shows the features for each iteration of the MVP.
The Feature Sequencer rules
- Rule 1: A line can contain a maximum of 3 features.
- Rule 2: A line cannot contain more than one feature with a red card (high uncertainty).
- Rule 3: Each line must have at least one green feature (low uncertainty).
- Rule 4: The effort score of the features cannot add up to more than 5 Es.
- Rule 5: The value score of the features must sum to at least 4 $s.
We came up with these rules after running many lean inceptions, finding them a good way to guide the iterative construction of the MVP.
Rule 1 limits the number of features being worked on at the same time (work in progress). By focusing on just a few prioritized features, it avoids having partially-done features clogging up the discovery process.
Rules 2, 3 and 4 prevent an unbalanced work period with either too much uncertainty, or too much effort. Rule 5 keeps a constant focus on delivering high business value.
Workshop teams using the Features Sequencer
|Monday||Introduce the inception, kick off, and Write the Product Vision||The product Is – Is not – Does – Does not|
|Tuesday||Describe the Personas||Discover the Features|
|Wednesday||Technical and Business Review||Show the User Journeys|
|Thursday||Display Features in Journeys||Sequence the Features|
|Friday||Build the MVP Canvas||Showcase the results of the inception to those interested in the project|