在开发过程中，产品经理需要培养和维护与许多人的关系. The most intimate of these, 然而, will be with the product user. 你应该彻底了解他们:他们是谁，他们的喜好，他们的需求. One way to develop and maintain this relationship is by writing 用户故事.
就像宣言和愿景文档一样，用户故事是一个不可分割的部分 产品开发. 好的用户故事是推动高效规划和交付的关键, 团队参与, and customer satisfaction. 模糊的用户故事通常表明团队将努力完成进一步的任务-这是我作为一名工程师经常目睹的 产品经理.
我参与过一些成功的初创公司，也有一些失败了，这让我亲身体会到花时间构思高质量用户故事的重要性. 本指南将帮助您和您的团队掌握每个元素，并一次又一次地编写高质量的用户故事.
用户故事是产品的一个小增量，表示它将为最终用户提供的价值. 一组用户描述 创造史诗, and a single product can comprise multiple epics. 用户故事可以进一步分解为更准确地反映工作和概述如何完成故事的任务. 用户故事通常采用这样的公式:用户-功能-效益, which can be applied effectively to most industries and businesses.
通常, 产品经理 负责编写用户故事，但有时这可能落在 产品负责人, Scrum master, or engineering manager. 理想情况下，每个用户描述都将由承担这项工作的一个或几个人进行审查.
A good user story has several benefits for the 团队与产品:
If, 例如, you are building a house for your customer, one of your stories would be about creating the enclosing walls. 一个糟糕的用户故事可能会说“我需要墙”——确定“什么”，但仅此而已. A better one would be: “作为房主, I want my house to have enclosing walls to keep out the elements, and so the roof doesn’t fall on my head.“我相信, 虽然, that if a user story is truly fulfilling its purpose, it should clearly and concisely answer all of the following questions:
This is the template I use—it has evolved with my product management knowledge and worked well for me for many years:
组件 | 问题 | 回答 | 目的 |
|---|---|---|---|
用户角色 |
用户是谁?? | 用户是一个来自芝加哥的富人，他正在汉普顿建造一座豪华的避暑别墅. | To fully envision the user, teams work with many different personas, so it is important to be as detailed as possible. |
用户故事 | 用户想要什么? 为什么 does the user want this? | “作为房主, 我想在我的家周围装饰成对角线编织图案的砖墙，因为我每天都会看到它们，希望它们是一个令人愉快的景象.” | To understand the motivation of the user and their reasoning. |
Summary | How should the engineering team interpret this story? | The user wants elaborate walls, 所以我们需要建立一个规则的中央墙，然后有脚手架所需的风格(i.e.(斜线编织). We can use regular bricks for the core wall, 但是需要使用高质量的装饰砖来装饰墙两侧的立面层. | 将故事逻辑地分解成任务，这有助于跟踪进度. |
先决条件 | Does this story depend on another story being completed beforehand? | In order to start work on this, 房子的地基需要完成，准备在上面建造. | 解释故事在工作流层次结构中的位置，并可视化整个交付时间线. |
后置条件 |
Does the completion of this story enable another story in the backlog?
| 墙建好后，我们就能搭起支撑柱，最后是屋顶. | 解释故事在工作流层次结构中的位置，并可视化整个交付时间线. |
完成的定义 | 范围是什么?? | There should be a continuous set of exterior walls around the house, with a diagonal basketweave-style facade on both sides of the wall. 墙的端到端宽度应不小于12英寸. | To define when a story is complete. The solution will need to include everything listed here. |
t恤尺寸 | 这个故事有多大? | 媒介 |
To loosely estimate delivery time for the overall story. 然后，执行者将为每个任务完成更细粒度的评估.
|
When it comes to judging whether 用户故事 are good or bad, there is a pervasive myth that I want to dispel.
Many people believe that a user story should be completed in a 单一的冲刺, and, if it isn’t, it was a bad user story. 事实并非如此. 当然, 最好是在sprint中完成用户描述(这应该是可以实现的)。, 但是团队的带宽和外部因素可能会影响可以完成的工作量——这在每个sprint之间都是不同的. 也, estimates generally assume that every development team member has the same skill level across all domains; the fact is, 经验丰富的工程师比初级工程师完成任务所需的时间要少.
You shouldn’t try to craft short 用户故事 just so that they will be completed quickly; rather, 您的用户描述应该设法表示交付的价值的逻辑增量. Don’t let a schedule dictate your creation of a compelling user story.
我发现，当我对自己的能力有信心时，项目是最愉快、最成功的 用户的知识—you can learn more about my experiences on my 个人博客. 无论我是在推销新功能还是与我的团队决定交付范围, 知道用户会说什么是测试我的视觉的最可靠的方法. 它是, 然而, 如果我不经常想到他们，就很容易失去与用户的联系，因此也就失去了“为什么”. 对于大多数产品经理来说，这是事实，他们的注意力经常被拉到其他任务和职责上. 编写好的用户故事可以帮助您和您的团队成员在您的脑海中保持用户的形象, and even enhance your relationship with them.
When writing a user story, you should include details about the user persona, 他们想要什么，为什么, how the story will be broken down into tasks, any other connected or affected stories, 故事的范围, 和大小.
A good user story encourages a customer-centric approach, provides clarity of purpose, 激励团队成员, 提高效率.
至少, a user story should identify three essential things: who the user is, 他们想要什么, 以及他们为什么想要它.
World-class articles, delivered weekly.
World-class articles, delivered weekly.
加入总冠军® 社区.
