用户故事-无法成为用户故事的问题 [英] User Stories - Problems that can't be made user stories
问题描述
我来自XP背景。我非常了解该过程，并且具有扎实的工作经验。我发现这是开发软件的最佳方法。
I am from an XP background. I know the process very well and have solid working experience with it. I have found it to be the best way to develop software.
我发现自己是一名过程医生，这会引起很多自我检查和对自己理解的重新评估。
I find myself in the position of a process doctor of sorts and this creates much self examination and revaluation of my own understandings.
我听到的一个很常见的事情是，有些作品无法写成故事。我个人不相信这一点。借口包括
A very common thing I hear is that some work can’t be made into stories. I personally don’t believe this. The excuses include
- 它太大（开发者在5周后将无法显示任何内容）。
- 这是一个复杂的算法或抽象概念（需要花费5周的时间编写，且没有任何显示）。
此问题是要获得提示，技巧或建议。
This question is to get hints, tips or suggestions.
我正在寻找有关如何解决这些和类似的感知问题的提示，技巧和建议（如果可以的话，还有更多信息）
I am looking for hints, tips, and suggestions as to how to address these and similar perceived problems (and more if you can think of them).
我将标记答案，该答案提供了有关如何绕开不会写故事并解决其许多借口的用户/开发人员的最多信息。至于为什么不这样（我只列出了几个，还有更多）。
推荐答案
所以基本上，您的问题是如果人们声称任务对于用户故事而言太大而不能拆分，该怎么办。
So basically, your question is "What can I do if people claim a task is too big for a user story, and can't be split up.
根据我的经验，几乎问题可以分解，问问他们是否可以实现简单化d版本，省略高级功能，甚至在某些地方甚至可以使用默认值；基本上所有可以在一次迭代中产生有意义（即可测试）结果的东西。
In my experience, almost any problem can be split up. Ask them if they can implement a simplified version, leave out advanced features, maybe even use default values in some places; basically anything to produce something that gives meaningful (i.e. testable) results within one iteration.
记住：迭代的重点不是提供完整的功能，而只是有用和可测试的功能。
Remember: The point of an iteration is not to deliver complete functionality, but just useful and testable functionality.
拆分可能很困难，但是它迫使您首先考虑自己真正需要的东西，这非常有价值。开发人员可能对此有些恶心（我经常自己做:-)），但这确实是必要的。将大型任务分解为可管理的用户故事是所有敏捷方法的核心。
This splitting can be difficult, but it forces you to consider what you really need first, which is very valuable. The developers may bitch about it (I often do myself :-)), but it's really necessary. Breaking down big tasks into manageable user stories is at the very heart of all agile methods.
也就是说，如果任务真的，真的，真的无法分解（在研究环境中考虑复杂的数学算法，甚至需要数周的时间才能了解其基础知识），因此迭代太短了。迭代需要足够长的时间才能产生有意义的结果。而且，如果您的大多数问题都如此艰巨，以至于需要2-3个月来完成，那么这就是您的迭代时间。但是我从未见过真正的案例……
That said, if the task really, really, really cannot be broken down (think complex mathematical algorithm in a research setting, that takes weeks to even understand the basics of), then your iteration is too short. The iteration needs to be long enough to produce meaningful results. And if most of your problems are so hard that they take 2-3 months to get anything done, then that's your iteration length. But I've never seen a project where that was really the case...
这篇关于用户故事-无法成为用户故事的问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
