Scrum 方法的工作区域是什么
What are work areas used for with the scrum methodology
在 visual studio 线上，有一个配置工作区的选项。我创建了一个项目，它使用 "Microsoft Visual Studio Scrum 2013.4" 过程模板。
我开始在项目中输入工作项并找到配置工作区的选项，但我不确定如何在此上下文中使用工作区。
在 scrum 方法的背景下，工作区域的目的是什么？
当您有多个团队（团队然后有自己的区域）、构成您的产品的多个物理事物（网站、胖客户端、某种集成库）时，区域是组织积压工作的一种方式。
或者，非常常见的用途，您产品的功能区域（例如购物车、搜索、check-out、付款、用户管理）。您可能可以从 PBI 标题中得出其中的一些内容，或者为此使用标签。这导致故事包含所有层的工作，从而确保每个故事本身都提供价值。
Scrum 中没有任何内容与此直接相关，尽管许多较大的 Scrum 项目使用功能团队并尝试在多个这些区域中分解产品以防止团队在同一段代码中相互绊倒.它为团队提供了明确的重点并帮助他们进行改进（因为他们不需要一直了解整个产品的所有来龙去脉）。
过去很多团队使用领域来表示产品的技术领域（front-end、业务层、数据库层、数据库架构、网络服务等），这被认为不是最好的拆分方式积压，因为它通常会导致本身不提供任何价值的组件或层故事。
官方文档can be found here。我认为页面底部的这些问题也会对您有所帮助：
* 问：一个团队应该定义什么样的区域节点？
You don’t have to add any area nodes. However, areas are useful to filter work item queries and reports based on features. Consider these guidelines when adding area nodes:
- Define areas that support your traceability and security requirements.
- Avoid creating an area structure that is too complex. You can create areas to partition permissions on work items, but complex trees require significant overhead for permission management. You might find that it is too much work to duplicate the structure and permissions in other team projects.
- Each team can create a hierarchy of areas under which the team can organize their backlog items, user stories, requirements, tasks, and bugs.
- Use areas to represent logical or physical components, and then create child areas to represent specific features. Your team can use this structure to keep work items organized and improve traceability by component or feature.
(Remark: Be careful with this is it also reflects your team
structure. It may lead to delayed value.)
- Create areas that you want to restrict access to.
* 问：如何构建团队、区域和迭代以支持分层团队或在企业内扩展敏捷性？
A: Although there is no concept of sub-teams, you can create teams whose area paths are under another team, which effectively creates a hierarchy of teams. To learn more, see Add another team.
Also, these two white papers can walk you through the steps for configuring teams, area paths, and iterations to support portfolio management or enterprise organizations:
* 问：有没有办法将团队与团队区域路径分离？
A: Yes. If your organization has several teams that work from a common backlog and across many product areas, you might want to change how teams are configured. By adding a custom field to represent teams in your organization, you can reconfigure the agile planning tools and pages to support your teams and decouple assignment to teams and area paths.
(Remark: this is currently not possible on visual-studio-online)
在 visual studio 线上，有一个配置工作区的选项。我创建了一个项目，它使用 "Microsoft Visual Studio Scrum 2013.4" 过程模板。
我开始在项目中输入工作项并找到配置工作区的选项，但我不确定如何在此上下文中使用工作区。
在 scrum 方法的背景下，工作区域的目的是什么？
当您有多个团队（团队然后有自己的区域）、构成您的产品的多个物理事物（网站、胖客户端、某种集成库）时，区域是组织积压工作的一种方式。
或者，非常常见的用途，您产品的功能区域（例如购物车、搜索、check-out、付款、用户管理）。您可能可以从 PBI 标题中得出其中的一些内容，或者为此使用标签。这导致故事包含所有层的工作，从而确保每个故事本身都提供价值。
Scrum 中没有任何内容与此直接相关，尽管许多较大的 Scrum 项目使用功能团队并尝试在多个这些区域中分解产品以防止团队在同一段代码中相互绊倒.它为团队提供了明确的重点并帮助他们进行改进（因为他们不需要一直了解整个产品的所有来龙去脉）。
过去很多团队使用领域来表示产品的技术领域（front-end、业务层、数据库层、数据库架构、网络服务等），这被认为不是最好的拆分方式积压，因为它通常会导致本身不提供任何价值的组件或层故事。
官方文档can be found here。我认为页面底部的这些问题也会对您有所帮助：
* 问：一个团队应该定义什么样的区域节点？
You don’t have to add any area nodes. However, areas are useful to filter work item queries and reports based on features. Consider these guidelines when adding area nodes:
- Define areas that support your traceability and security requirements.
- Avoid creating an area structure that is too complex. You can create areas to partition permissions on work items, but complex trees require significant overhead for permission management. You might find that it is too much work to duplicate the structure and permissions in other team projects.
- Each team can create a hierarchy of areas under which the team can organize their backlog items, user stories, requirements, tasks, and bugs.
- Use areas to represent logical or physical components, and then create child areas to represent specific features. Your team can use this structure to keep work items organized and improve traceability by component or feature.
(Remark: Be careful with this is it also reflects your team structure. It may lead to delayed value.)- Create areas that you want to restrict access to.
* 问：如何构建团队、区域和迭代以支持分层团队或在企业内扩展敏捷性？
A: Although there is no concept of sub-teams, you can create teams whose area paths are under another team, which effectively creates a hierarchy of teams. To learn more, see Add another team. Also, these two white papers can walk you through the steps for configuring teams, area paths, and iterations to support portfolio management or enterprise organizations:
* 问：有没有办法将团队与团队区域路径分离？
A: Yes. If your organization has several teams that work from a common backlog and across many product areas, you might want to change how teams are configured. By adding a custom field to represent teams in your organization, you can reconfigure the agile planning tools and pages to support your teams and decouple assignment to teams and area paths.
(Remark: this is currently not possible on visual-studio-online)