The figure is based on a story Kanban agile or an agile process, there is nothing better than a personal investment. The user, through its own members the demand side of investment, in order to allow the expression of team members to better understand their thoughts and ideas unified team members. User story is a way of thinking, thinking that is the story, using the elements of the story and design thinking, problem solving, to achieve a certain effect.
User Story core design is to pass information through the story, resonate, to solve the problem.
Storytelling is not a simple task, requiring excellent organizational skills, articulate way to reach the audience we want to express clear. Here is my suggestion, if you usually communicate with people in too little time, by writing blog, etc., to organize your central idea, let the audience know what we want to express.
Product design, easily a few extreme bias: 1 experts in the field; 2 users, the demand side, 3 favor R & D side.... Experts tend to use less product threshold is too high, can not be universal, tend to the needs of users of products considered too messy, unfocused nature (the user may not know what they want in the end); bias R & D side products may be acclimatized.
At this time, we need a group of people: customers, experts, users, developers , etc. together, definitions and questions scene to face what is the product? Those problems can be solved by the product? How high products give the company's rate of return? Bring any value to users? Product development, the needs of users will be many, many, like a huge map, and "user stories" good at focusing build know the characteristics, focusing on small details, the lesson by example can be seen, different user stories block prone to mismatch of product parts, used, there is a new way to "user story map" appeared;
The following problems can be solved through the map:
- Let's easier to see the whole picture of pro backlog;
- Provides a better tool for screening new features and planning priorities, we help those decisions backlog into TODO;
- Ease of use, and other collaborative brainstorming ways to generate user story, namely how to more effectively in story workshop in output;
- Help us better incrementally iterative development, but also remember, the lesson "must have, should have, could have, would not have" these concepts?
- It provides a better alternative to the traditional tools for project planning, change from passive to active participation;
- It allows us to project planning from different dimensions, and make sure not to miss each different ideas, to avoid authoritarian.
How to create a story?
1. preparation:
Several product called core staff, the best is odd, easy to make a decision. From the user, product managers, business analysts, architects, etc., because the title of each project represents the views of the main characters, so the story maps created later to avoid a lot of unnecessary debate preach to all plan . Prepared the day shift, electronic tablet, various stickers, tapes, coffee, tobacco, a lighter and relatively independent office.
2. organize creative framework
Definitions and questions, what products to face the scene? Those problems can be solved by the product? How high products give the company's rate of return? Bring any value to users?
Single answer, to clear objectives on post, in accordance with the priorities in good order. * This step is important
3. portray user portrait
Referring to the article written before, but introduce more;
4. From the most important user starts to write big stories, attention is not epic type of.
5. ferret out the details: start from the user's point of view the portrait, the previous cases, "Ye Hailong," the director, he was in the system, based on a process, what would he do? Are there other options? Character does not meet his habits? When problems arise, he hopes, how he would deal with?
6. division MVP release plan : Why divide MVP? think for a while.