VSO:具有分层区域结构的单个项目? [英] VSO: Single project with a tiered area structure?

问题描述

从历史上看，我们一直对每个正在开发的逻辑项目有单独的 VSO 项目.这一点特别重要，因为我们需要为每个项目分别准备好待办事项.每个项目都有自己的产品负责人.

Historically we have always had separate VSO Projects for each logical project undergoing development. This is particularly important as we need to have separate backlogs for each project. Each project has its own Product Owner.

我们有一个大约10名开发人员的团队，他们在两个星期的冲刺中在这些项目之间工作.

We have a team of around 10 developers who work between these projects over 2 week sprints.

使用VSO的Scrum工具时，此设置导致了一些严重的问题:

This setup has led to some serious issues when using VSO's Scrum tools:

• 多个燃尽图，累积流量和速度图
• 在冲刺期间拆分团队成员的能力

这使得监视sprint期间的工作进度以及有效地计划下一个工作非常困难.这导致我创建了 StackOverflow问题.

This has made it very difficult to monitor work progress during sprints and to plan effectively for the next. This led me to create this StackOverflow question.

基于MrHinsh的回答，我现在可以拥有1个VSO项目，然后将所有项目划分为多个区域:

Based on MrHinsh's answer, I can now have 1 VSO project and then split all the projects into areas:

这意味着我们在项目中拥有以下团队(全部映射"到了他们的相关区域):

This means we have the following teams in Project (all "mapped" to their relevant areas):

• 项目1团队
• Project 2团队
• Project 3团队
• Project 4团队

在区域结构中增加一层是个好主意吗?

例如，项目属于某个产品.逻辑分组对于报告缘故(速度/燃烧日期/等)可能很有用.它将非常适合我们的组织模型:

For example, projects belong to some product. A logical grouping could be useful for reporting sake (velocity/burn date/etc). It would fit our organisational model quite well:

根据我的理解，然后我们需要再创建两个团队:

From my understanding, we would then need to create two more teams:

• 产品团队
• 产品B团队

其他问题:

从本质上讲，这意味着产品A团队的待办事项将是项目1和项目2的待办事项的积累.但是，成员仍可以将项目添加到产品A的待办事项中，这有点不对，因为待办事项仅应在项目1和2中创建.是否没有办法禁用此功能?

This would essentially mean that the Product A Team backlog would be an accumulation of the Project 1 and 2 backlogs. BUT, members could still add items to Product A's backlog, which is somewhat wrong because backlog items should only be created in Project 1 and 2. Is there no way of disabling this?

我一直在VSO中进行操作，发现无论成员属于哪个区域，他/她似乎总是可以访问项目中的所有区域.这意味着访问控制不太可能.另外，这意味着我无法隐藏"产品层.

I have been playing around with this in VSO and have found that no matter which Area a member belongs to, he/she always seems to have access to all areas in the Project. This means that access control isn't quite possible. Also, it means that I cannot "hide" the Product layer.

此外，在导航到团队区域时，没有明确的层次结构指示(请参见下面的屏幕截图).这可能会误导成员.这将是隐藏此类产品层的另一个原因.我还没有找到一种方法.

Additionally, when navigating to a team area, there is no clear indication of the hierarchical structure (see screenshot below). This may be misleading for members. This would be another reason to hide such Product layers. I haven't found a way to do this.

推荐答案

无法隐藏产品"层，但是您可以做一些关于权限和默认值的事情.

There is no way to hide the Product layers, however you can do something about permissions and defaults.

权限

您可以直接在区域路径上设置权限.这使您可以限制可见性或将访问权限写入区域路径的内容.如果打开区域路径管理器并单击鼠标右键，则可以看到权限"选项.请记住，未设置"比拒绝"要好得多，因为拒绝"总是赢.

You can set permissions directly on Area Paths. This allows you to restrict visibility or write access into the contents of an area path. If you open the Area Path manager and right-click you can see the "Permissions" option. Remember that "not set" is way better than "Deny" as "deny" always wins.

如果选择根区域->安全->参与者，则可以不设置"不想继承的权限.然后授予团队访问所需区域的权限.

If you select the root Area->Security->Contributors you can "not set" the permissions that you don't want to inherit. Then give Teams access to the areas that you want.

积压管理

如果打开积压树，而不是选择"ProductA"节点作为"ProductA"团队的积压迭代，则可以选择"Project1"作为默认区域.然后，添加到"ProductA"积压中的所有新项目都会自动显示在"ProductA \ Project1"上，而不是根目录上.

If you open up the backlog Tree and instead of selecting the "ProductA" node as the backlog iteration for the "ProductA" team you can select "Project1" as the default area instead. Any new items added to the "ProductA" backlog then automatically appear on "ProductA\Project1" instead of the root.

您要做的只是将鼠标悬停在"Project1"条目上，然后选择设置默认值"以使其成为默认值.

All you do is hover over the "Project1" entry and select "set default" to make that the default.

这篇关于VSO:具有分层区域结构的单个项目?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！