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

User stories: cards, conversations and determinations; based on three steps.

Example: Project: Company A is a subsidiary of a testing equipment company. Its main service object is manufacturing. Due to the outdated software system, customer satisfaction is very low. The company decided to redevelop a software that caters to the current market for the pain point of manufacturing, which should include enterprise infrastructure, production operation management, production quality management, production process monitoring, energy consumption management, etc., and needs to be launched within 3 months. Fortunately, customers are willing to assign docking staff to plan the system with R & D staff.

One morning of the week, the customer, the product owner, the R & D team, and the Scrum Coach meet in a separate environment to discuss system requirements and identify system capabilities.

Identify customers:

A pile of blank cards was placed in front of each person. Next, all the members began to rack their brains to write user role cards on the cards: BOSS factory manager line length qc frontline employee inspector quality director assembly worker... Until everyone can no longer remember other roles, the next step is to summarize all user role cards and remove the same roles. The process is slightly...

After a long time...

The roles are defined as:

BOSS factory manager line length qc frontline staff......

Character modeling: Next, the team considers adding detailed descriptions to each character card. The detailed description will vary depending on the domain and software type, taking into account:

How often users use the software; how specialized users are in their field of expertise; how familiar users are with computers and software; how proficient users are with the software being developed; and what the users really want to use the software for.

........

Based on the team discussion above for each character card, they felt the need to update the user character cards:

BOSS： Pay attention to the annual, quarterly and monthly production plan achievement rate and quality data, rarely use the system, mainly observe the production status of the plant through icons; Factory Director: pay attention to the annual, quarterly and monthly production plan achievement progress and quality, often use the system, mainly pay attention to the rationality of the production plan, supplier incoming materials, incoming materials quality, orders, even production status and quality information; Line Length: often use the system, Focus: put into production according to the production scheduling order, prevent team members from cheating, and ensure that the quantity and quality of the production process are controllable;qc: frequently use the system, focus on ensuring the quality of products in process and finished products, find out the reasons and report them; front-line employees: do not log in to the system, determine whether the current operation is correct through SOP, and pay attention to working hours;

With the user persona cards and malleable notes above, the Scrum Coach suggests creating user portraits to the team, explaining that user portraits can make user personas more solid, not cold requirement codes, but real.

Therefore, the portrait of factory director Ye Hailong was born in this way: (based on real personnel)

Is this portrait more specific to the image of a certain user of the system? Whether the team members are clearer about the specific users that the product is intended for, then the system functions will be relatively clear and clear, avoiding the "natural needs" based on the customer/R & D personnel's mind;

With this initial list of stories, the team moved on to the next step,"Write Story Workshop," where members began another brainstorm:

The first way:

The user cannot register the system, and the administrator needs to configure it in the system; the administrator sets roles for the user, and different roles have different role permissions in the system; the user can see the real-time production quantity of the production line; the user can punch in the card; according to different product barcodes, RFID will automatically identify, and the system will automatically play sop; defective products are prohibited from flowing to the next station; incoming materials need to be inspected; equipment needs to be inspected; production plans can be made; attendance system can be connected; Inspection templates can be uploaded to the system; production plans can be written; production real-time Kanban

......

Second way:

Ye Hailong:

You can check whether the scheduling is reasonable, and the system automatically calculates according to the output of each line; you can see the real-time production quantity of the production line; you can view the incoming material summary information of a certain supplier, and decide whether to accept the payment signature;... end

When the group couldn't write any more story cards, they gathered all the story cards together and eliminated the duplicates. Finally, the group could relax and have a cup of coffee. Don't get too excited, the work isn't done yet. What's next? Think about it...

Summary:

User portraits can be simply understood as labels of massive data, which can be divided into different types according to the differences in users 'goals, behaviors and opinions, and then typical features are extracted from each type, and names, photos, some demographic elements, scenes, etc. are given to describe them, forming a persona prototype.

1. Macro-build concrete cognition, build strategic and tactical direction: In order to make the team achieve unified and concrete cognition on the core users, it is convenient to target the subsequent investment; product design based on the information of user portraits must clearly know what the user looks like, what behavioral characteristics and attributes, so as to provide strategic and tactical guidance for the product.

2. Macro-Explore user footprint, user (market) orientation: Learn in detail how our real users interact with products and related content; we must start from business scenarios to solve actual business problems. The reason for user profiling is either to acquire new users, improve user experience, or recover lost users, and finally design products for users.

3. Micro-building the underlying data base, as mentioned in the second article, can make the product more in line with the real needs of the use, so as to better fit the customer; everything is only for customer satisfaction, no quarterly KPI is lost.

4 Micro-convenient information processing: With labels, team members can easily process and classify each quantitative requirement and evaluate the iteration cycle.

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.