Transfer: https: //www.leangoo.com/9944.html
The story is the main way to express user requirements in agile development, agile development when we do have the concept of pool needs, demands in Scrum this pool is the product backlog, there is a demand pool of entry requirements, each usually a user story. By definition of Scrum, a product backlog is worth ordering mandatory queue-based team in accordance with the level of value, order delivery requirements.
In the development process, the team will gradually refined product backlog, in order to ensure the delivery of fast track, high-priority user stories will be broken down into smaller particle size. But this poses a problem, for those slightly larger scale in terms of products, the number will be much the story, after story splits often have the feeling of missing the forest for the trees. The story is a kind of map users to organize and manage user stories Jeff Patton inventive method, can solve this problem. Jeff Patton has also written a book, "user story map" to help us better learn the story map, the Chinese translation of the book (translated Baidu Li Tao) in March this year will be in the domestic market.
This article describes how to use Kanban to achieve Leangoo story map to help us better manage and visualization needs.
Before introducing the story map, let's review the basic concepts of user stories. User stories are described from the user's perspective eager to get user function. A good user story consists of three elements:
1. Role: Who use this feature.
2. Activities: What kind of function needs to be done.
3. Commercial Value: Why do you need this feature, which brings what kind of value.
User stories are usually expressed in the following format:
English:
of As A <Role>, the I want to <Activity> SO that <Business Value>.
Chinese:
As a <character>, I want <event> in order to <commercial value>
Example:
As a "webmaster" I want "every day count how many people visit my site" in order to "my sponsors that my site is what will bring them benefits."
Note that user story can not use technical language to describe, to use the user can understand the business language to describe.
User story map is a way to organize user stories and prioritizing. User story map can bring some benefits as follows:
1. The story maps provide a big picture of demand, can help us visualize business processes or value chains through billboards.
2. The establishment of a sub big story after story of split and direct correspondence.
3. Let us to complete the backlog of cases at a glance.
4. You can help us to prioritize and release planning from the perspective of an overall perspective, the user value.
User map comprises two stories latitude, traffic flow is a lateral, longitudinally value order. Below is an example:
figure 1
In Figure -1, the orange card on behalf of the coarse-grained user stories can be understood as Epic- epic story, Jeff Patton called the user's activity (User Activity), those users' activities on behalf of the skeleton of the product, we From left to right according to the time line to arrange these activities, then lined up, the main business processes on the system presented itself. It should be noted that, in order to identify those users activities, the first step is to do character modeling, the user role first extracted. In each epic story below, we can split the more fine-grained user stories. These user stories together constitute the main function of the product needs to be done, and the system has been in accordance with the cytoskeletal organization better.
FIG -1 latitude in the transverse direction, we use these cards orange dashed lines into three transverse lanes, each lane represents a release. So, from this story map, transverse represents the system's skeleton, context, vertical represents the importance, priority, release order.
We need to think in terms of value to users on this business process, which is the most central, most important, we can follow the idea of refining MVP (minimum viable product) is to find out the core of the scene, put the previous release, the low priority into the back of the publication. The purpose of this is to do value-driven, let's products from the perspective of the user's core values, and sustained, incremental delivery.
Understanding of the Story Map of thinking, we look at how to use the tool to achieve such Leangoo to a story map. User Story Map 2 weft, Leangoo Kanban tool is easy to implement, in billboards, we have a list of concepts and lanes, the list represents the vertical latitude, lane represents the horizontal latitude. In Leangoo, we usually use the list represents a different release, so we usually build several lists: traffic flow, Sprint1, Sprint2, Sprint3-N, it has been delivered to the story. Traffic flow this list represents the orange card, which is the epic story of the epic story each lane. Sprint1, Sprint2, Sprint3-N which is split out by Epics different story, and into which Sprint different according to the priority, the lateral lanes represent the corresponding relationship between the sub-story and split Epics Epics. As shown below:
figure 2
The story has already delivered the list put the complete story, so you can release burndown by leangoo generated by the release burndown progress in understanding the development of the product or project.
Story Map implementation textbook example Leangoo site as shown below:
image 3
By Leangoo billboards, we can very easily through the stories of the demand for the product map Panorama show out of product planning at a glance, for which we continue to focus on core product value, better product planning very helpful.