The second step of the agile framing which starts at the end of “mission and challenges” is to work on the product vision. Now that the vision and the challenges are clear, the agile framing team will be able to work easier on the product vision. Alignment with this product vision will allow:
- the team to go together in the same direction
- to guide customer and user interviews
- to make sure that the expected product is clear to everyone
Here is in red the step represented on the canvas:
Setup the Obeya
Before starting to work on the product vision, the team will have to carry out two important successive actions:
- prepare the Obeya with its visual management
- carry out the first planning meeting
This second step of the agile framing can be very variable about duration. The time required to complete all of the workshops can range from 3 days to 6 days. On complex products, the team may even have to start the third step before even finalizing this second step. For example, if a “user” is essential to complete a customer journey but he will not be available for two weeks, the team can start the step 3; the team doesn’t have to wait until they are 100% finished before starting the next step. Indeed, this is the main reason that we define agile framing as a lean-agile framework and not waterfall framework.
The workshops for this second step are:
- Product vision board (soon)
- Personae (soon)
- Customer Journey (soon)
- Impact Mapping [optionnel]
- Before, over, after [optionnel]
- Story mapping advanced (soon)
- Wireframe (soon)
* You can see all these articles available in the french blog (english version is not already complete) !
Agile framing v2 greatly strengthens the product vision aspect by offering several possible alternatives to complete the product vision. It is really essential to have an excellent vision of the product so that it advances under the best conditions.
Indeed, as each product can be very different, it’s essential to know effective alternatives to optimize this work on the vision as much as possible. For example, on a product that represents an application with a single page presenting dashboards of IT indicators, it will be no interesting to work on a customer journey; indeed, there will be no real user journeys. However, an Impact mapping or even a before, over, after could be very interesting workshops to understand the objective of these dashboards and the use that users will have of them.