试试这个。要求 BA 考虑系统需要提供的所有功能 - 系统将使用户或公司能够执行的所有操作。作为指导，我们在一个为期 1 年的项目中大约有 30 个这样的单词，它们都是单个单词或首字母缩略词。
其中一些非常容易理解，并且与其他类似的项目相同。其他人将会是新的，或者你会对他们一无所知。这是获得 BA 帮助的好地方。
如果 BA 无法提供足够的帮助，请尽快交付这些有风险的事情并尽可能频繁地获得反馈。如果 BA 无法帮助您提供反馈，那么您需要更直接参与的利益相关者的帮助。
You don't necessarily need all the user stories up front. The main reason you might want this is to determine how long the project will take and get slightly better accuracy. There are other ways of engaging the trust of stakeholders.
Try this. Ask the BA to think of all the capabilities that the system needs to provide - all the things that the system will enable the user or the company to do. As a guide, we had about 30 of these on a 1 year project, and they were single words or acronyms.
Some of these will be very easy to understand, and will be the same as other, similar projects. Others will be new, or you'll be ignorant about them. This is a great place to engage the BA's help.
If the BA can't help enough, deliver these risky things as soon as possible and get feedback as frequently as you can. If the BA can't help you with that feedback then you need help from a stakeholder who's more directly involved.
Since there are so many areas that are a bit "grey", should a developer sit with him and make sure that all areas are covered?
Of course, how else do you know what to build? Guessing costs everybody time and money and it's practically impossible to be 100% correct.
I'd say go back to the whiteboard and try to agree on all features management can expect for a first version.
BDD/TDD/DDD is no silver bullet to this problem, however, it can give developers and business analyst inspiration. BDD really shines when you want to communicate what your application can do right now.
发布评论
评论（2）
您不一定需要预先了解所有用户故事。您可能希望这样做的主要原因是确定项目需要多长时间并获得稍微更好的准确性。还有其他方法可以赢得利益相关者的信任。
试试这个。要求 BA 考虑系统需要提供的所有功能 - 系统将使用户或公司能够执行的所有操作。作为指导，我们在一个为期 1 年的项目中大约有 30 个这样的单词，它们都是单个单词或首字母缩略词。
其中一些非常容易理解，并且与其他类似的项目相同。其他人将会是新的，或者你会对他们一无所知。这是获得 BA 帮助的好地方。
如果 BA 无法提供足够的帮助，请尽快交付这些有风险的事情并尽可能频繁地获得反馈。如果 BA 无法帮助您提供反馈，那么您需要更直接参与的利益相关者的帮助。
You don't necessarily need all the user stories up front. The main reason you might want this is to determine how long the project will take and get slightly better accuracy. There are other ways of engaging the trust of stakeholders.
Try this. Ask the BA to think of all the capabilities that the system needs to provide - all the things that the system will enable the user or the company to do. As a guide, we had about 30 of these on a 1 year project, and they were single words or acronyms.
Some of these will be very easy to understand, and will be the same as other, similar projects. Others will be new, or you'll be ignorant about them. This is a great place to engage the BA's help.
If the BA can't help enough, deliver these risky things as soon as possible and get feedback as frequently as you can. If the BA can't help you with that feedback then you need help from a stakeholder who's more directly involved.
当然，您还怎么知道要构建什么？猜测会花费每个人的时间和金钱，而且几乎不可能 100% 正确。
我想说回到白板并尝试就第一个版本的所有管理功能达成一致。
BDD/TDD/DDD 并不是解决这个问题的灵丹妙药，但是，它可以给开发人员和业务分析师带来启发。当您想要传达应用程序现在可以做什么时，BDD 确实会发挥作用。
Of course, how else do you know what to build? Guessing costs everybody time and money and it's practically impossible to be 100% correct.
I'd say go back to the whiteboard and try to agree on all features management can expect for a first version.
BDD/TDD/DDD is no silver bullet to this problem, however, it can give developers and business analyst inspiration. BDD really shines when you want to communicate what your application can do right now.