规划扑克已经在其他地方讨论过了(包括软件教育“敏捷需求-故事”课程)，因而在此不会讨论它的细节。
Planning poker has been discussed in other places (including the Software Education "Agile Requirements - Stories" course) so we will not discuss it in detail here. However we will discuss.
如果您的大多数系统都是同类型的，并且您对于产品在最常见的支持周期之外没有特殊的敏捷需求，前者可能是一个很好的选择。
The former can be a good choice if most of your systems are homogeneous and you don't have specific needs for agility beyond the most common support cycles, of the products.
图1显示了敏捷项目中需求定义与设计的迭代循环过程。
Figure 1 illustrates an iterative cycle for requirement definition and design for agile projects.
应用推荐