Two skills of creating product to-do list

Product backlog is one of the three artifacts in agile framework (the other two are iterative backlog and potential publishable increment). Generally speaking, the product to-do list is extracted from the development of product vision. There are two common technologies that can help product managers improve their product vision:

1. Customer itinerary map

Customer experience journey map is a tool to visually present the process that users go through to achieve a certain goal. By creating a journey map, we can better understand the feelings, thoughts and behaviors of target users at a specific time, realize the evolution of this process, and find the pain points of users.

From the customer's point of view, this diagram completely describes all the links that customers achieve their goals. By marking the pain points, thoughts and behaviors of users in each link, the quality of products can be intuitively reflected.

For example, when customers get up for work in the morning, they need to go through the steps of turning off the alarm clock, watching the mobile phone, washing, dressing, dressing up, making breakfast, eating breakfast, watching the news and checking the road conditions before going out. Each link has different emotions and pain points, which can be further developed into user stories to meet the needs of customers.

Typical CJM:

To draw a complete CJM as above, you need to get to know users through user interviews, literature collection, questionnaires and other ways, create a customer role model, completely describe customers' goals and behaviors in using your products, and finally draw a CJM, marking customers' operations, feelings and needs in each link.

2. User story mapping.

User story diagram is a popular iterative planning method in agile framework, which can help you transform the product agent list into a two-dimensional diagram, and integrate the user journey and iterative/release planning from the customer's point of view.

On this picture, from top to bottom, it is generally divided into user activity (from left to right is generally the order of user journey), user task, (epic) and user story. User stories will be placed in different lines according to the publication. A line is usually 1~2 iterations, which can help product managers determine the priority of user stories and the purpose of iterative publishing under each activity, and quickly recover feedback.

Please refer to: /pd/270289.html for specific operation process guidance.