希腊罗马神话中的爱情故事

In my work with agile teams and as a trainer I often hear  statements about user stories that cause problems in practice. Time to  get rid of the most common myths.

在与敏捷团队合作和作为培训师的工作中，我经常听到有关在实践中引起问题的用户故事的陈述。 是时候摆脱最普遍的神话了。

误解1：在Scrum中，您使用用户案例记录需求。 (Myth 1: In Scrum, you document requirements with user stories.)

The Scrum Guide leaves it open how backlog items are documented. I  like user stories because they shift the perspective from the system to  the user. But they are not mandatory. And they should be used more for  conversation than f or documentation.

《 Scrum指南》保留了如何记录积压项目的信息。 我喜欢用户故事，因为他们将视角从系统转移到了用户。 但是它们不是强制性的。 而且，与f或文档相比，它们应更多地用于对话。

误区二：如果编写用户故事，则必须使用特定的模板。 (Myth 2: If you write user stories, you have to use a certain template.)

You probably think of: As a user I want function so that fulfilled need.The user story concept had nothing to do with this template at the  beginning. Later the template became popular. It's possible to document  user stories informally. Don't get hung up on the template.

您可能会想到：作为用户，我需要功能以便满足需求 。用户故事的概念在开始时与该模板无关。 后来，模板开始流行。 可以非正式地记录用户故事。 不要挂在模板上。

误解3：使用故事点估算用户故事。 (Myth 3: User Stories are estimated with Story Points.)

As a Scrum Master, I watched teams go crazy with discussions about story points, estimates and velocity.There is a simple alternative. The team agrees on small stories. So 1 or  2 days to implement them. Then after the sprint, the team counts the  stories it has finished. There's the velocity.

作为Scrum Master，我看到团队疯狂地讨论故事点，估计和速度，这是一个简单的选择。 团队同意小故事。 因此需要一到两天的时间来实施它们。 在冲刺之后，团队计算完成的故事。 有速度。

Learn more about by visiting my online course. If you want to keep up with what I'm doing, follow me on , or . Or visit my .

通过访问我的在线课程，了解有关更多信息。 如果您想跟上我的工作，请在 ， 或上关注我。 或访问我的 。

翻译自:

希腊罗马神话中的爱情故事