Shulou(Shulou.com)06/03 Report--

The image above is a Kanban or one of the Agile processes based on Agile stories, and nothing works better than investing in it yourself. Users, team members demand side through their own input, expression in order to make team members better understand their ideas and unify the ideas of team members. User story is a kind of thinking, that is, story thinking, which uses the elements of the story to think and design to solve problems and achieve a certain effect.

The core of user story design is to convey information through stories, resonate and solve problems.

Storytelling is not a simple task. It requires excellent organizational skills and clear expression so that the audience can clearly understand what we want to say. Here, the author suggests that if we usually have too little time to communicate with people, we can organize our own central idea by writing a blog and let the audience know what we want to express.

In the design of products, it is easy to tend to several extremes: 1. Domain experts; 2. User, demand side, 3. Biased towards the R & D side. Biased to domain experts, then the threshold for the use of products is too high to popularize, biased to demand, user products are too messy, and there is no focus (users may not know what they want); preferred R & D products may be dissatisfied.

At this time, we need a group of people: customers, experts, users, R & D, etc., to define and ask questions, what is the scenario that the product has to face? What problems can be solved through the product? What is the rate of return that the product can bring to the company? What value does it bring to users? In the development of the product, there will be many, many user requirements, like a huge map, while "user story" is good at focusing on building knowing features and focusing on small details. As can be seen from the example of last lesson, different user story blocks are prone to mismatched parts of the product. By using, a new method "user story map" has emerged.

The following problems can be solved through maps:

Makes it easier for us to see the full picture of pro backlog; provides better tools for new feature screening and planning priorities to help us decide which backlog is put into TODO; to facilitate brainstorming and other collaborative ways to generate user stories, that is, how to produce more effectively in storytelling workshops To help us better carry out incremental iterative development, do you remember the concepts of "must have, should have, may have, and will not have" in the last lesson? It provides a better alternative to traditional project planning, from passive to active participation, allows us to plan projects from different dimensions, and ensures that every different idea is not left out and dictatorship is avoided.

How do I create a story?

1. Preliminary preparation:

Call together several core personnel of the product, preferably an odd number, to facilitate decisions. From users, product managers, business analysts, architects, etc., because each title represents the views of the main players in the project, the story map can be created to avoid many unnecessary debates when the plan is presented to the whole in the future. Prepare day shifts, handwriting boards, stickers, tape, coffee, cigarettes, lighters and a relatively separate office.

two。 Organize the creative framework

Define and ask questions, what is the scenario that the product will face? What problems can be solved through the product? What is the rate of return that the product can bring to the company? What value does it bring to users?

Unify the answer, write down the clear goals on the post-it notes, and put them in order of priority. * this step is very important

3. Depict user portraits

Refer to the previous article, but introduce more

4. Start with the most important users, write big stories, and note that they are not epic.

5. Dig into the details: from the perspective of user portraits, for example, the former "Ye Hailong" factory director, he is in the system, based on a certain process, what will he do? Are there any other options? Is it in line with his usage habits? When a problem arises, how does he hope and how will he deal with it?

6. Divide MVP release plans: why divide MVP? Think about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.