How to use Leangoo to do demand management? (User Story map)

User stories are the main way to express demand in agile development, we have the concept of demand pool when we do agile development, in scrum this demand pool is the product backlog, the requirements pool is an entry requirement, each is usually a user story. As defined by scrum, the product backlog is a queue of value-based ordering, in which teams deliver requirements in order of value.

In the development process, the team will gradually refine the product backlog, in order to ensure the delivery of fast track approach, high-priority user stories will be broken down into smaller granularity. But this brings a problem, for those of the larger size of the product, the number of stories will be many, the story after the split will usually have trees trees feeling. The user story map is a method that Jeff Patton invented to organize and manage user stories, which can be a good solution to this problem. Jeff Patton also wrote a book "User Story map" to help us better learn the story map, the book in the Chinese version (Baidu Li Tao translation) will be listed in China this March.

This article will show you how to use Leangoo Kanban to implement a story map to help us better manage and visualize requirements.

Before introducing the story map, let's review the basic concepts of the user story. A user story is a user's point of view to describe a user's desired functionality. A good user story consists of three elements:
1. Role: Who wants to use this feature.
2. Activity: What functions need to be completed.
3. Business value: Why this feature is needed and what value this feature brings.

User stories are usually expressed in the following format:

English:
As a <role>, I want to <activity>, so that <business value>.
Chinese:
As a < role, I want to < activities, in order to < business value >

Example:
As a "webmaster", I want to "count how many people visit my site every day", so that "my sponsor knows what my website will do for them." ”
It is important to note that user stories are not described in technical languages, but are described in a business language that users can understand.

A user story map is a way to organize and prioritize user stories. User Story maps can bring some of the following benefits:
1. The story map provides a large picture of the needs that can help us visualize the business process or value chain through Kanban.
2. Set up a large story and split the sub-story of the direct correspondence.
3. Let us have a clear picture of the completion of the backlog.
4. Can help us to prioritize and release plans from a holistic perspective, from the perspective of user value.

User story map includes two latitude, landscape is business flow, portrait is value order. is an example:

Figure-1

In Figure 1, the orange card represents a coarse-grained user story, which can be understood as the epic-epic story, which Jeff Patton calls user activity, which represents the skeleton of the product, and we arrange these activities from left to right in the timeline, Once arranged, the main business process of the system is presented. It is important to note that in order to find out these user activities, the first step is to do character modeling, to extract the user roles first. Below each epic story, we can split a finer-grained user story. These user stories together make up the main function of the product, and have been organized according to the system skeleton.

In the horizontal latitude of Figure 1, we use the orange dashed line to cut these cards into 3 lanes, each of which represents a release. So, from this story map, the horizontal representation is the skeleton of the system, the context, vertical represents the importance, priority, release order.

We need to reflect on the value of the user in this business process, which is the core, the most important, we can refine the MVP (the smallest feasible product) to find out the core scene, put in the previous release, the low priority to put in the post. The purpose of this is to do value-driven, let us from the user's perspective product core value, and continuously, incremental delivery.

After learning the idea of a story map, let's look at how to use the Leangoo tool to implement a story map like this. User Story map is 2 weft, Leangoo Kanban tool is easy to implement, in Kanban, we have the concept of lists and lanes, the list represents the longitudinal latitude, the swimlane represents the horizontal latitude. In Leangoo, we typically use lists to represent different releases, and we typically build so many lists: business flow, sprint1,sprint2,sprint3-n, delivered stories. Business Flow This list represents an orange card, an epic story, a swimlane for each epic story. Sprint1,sprint2,sprint3-n is a story that splits different epic stories, and is placed in different sprints based on priority, and the horizontal swimlane represents the correspondence between the epic story and the sub-story that the epic story splits. As shown in the following:

Figure-2

The story that has been delivered this list is the completed story, so that you can generate a release Burndown chart by Leangoo, and release Burndown charts to understand the development of the entire product or project.

The story map for the Leangoo implementation of the book site is shown in the following example:

Figure-3

Through the Leangoo Kanban, we can easily through the story map to show the product needs panorama, product planning is also at a glance, which is our continuous focus on product core value, better product planning is very helpful.

About

Liao Jingbin, International Scrum Federation certified CSP,CSM, a nationally renowned agile coach, consultant, trainer

Article turned from: leangoo.com

How to use Leangoo to do demand management? (User Story map)