We have a small group < 4 but work on several different applications that we support. Each application gets its own Git repo, but as for managing the effort I really don't want to setup a separate team as well for each product.
Questions:
- For a small group working on several different products (eg. websites, services, utilities etc), can a single "team" within one project allow us to work on 2 sprints at the same time that are within different area paths?
- If I have already defined multiple teams, can I migrate all the content into the backlog of a single team?
- Assuming one team and multiple area paths, the project "hierarchy" would look something like this, correct?
Project
|__Team
Area-1
|__Sprint 1-n
Area-2
|__Sprint 1-n
Area-3
|__Sprint 1-n
[ update ]
On further inspection looking at the docs, the iterations can have their own paths.
It seems that if we want to manage 2 or more simultaneous sprints or overlapping sprints that involve different products, it makes sense to go ahead and configure a team per product or possibly one team per "business area" (eg. Sales, Operations, Warehouse etc). Within a business area, our group would only have 1 active sprint at a time, which seems straightforward, compared to trying to manage multiple sprints within the same team.
https://docs.microsoft.com/en-us/azure/devops/organizations/settings/set-iteration-paths-sprints?view=azure-devops
So the better approach might be multiple teams, with one (default) area per team and a iteration list for each team.
答案 0 :(得分:1)
团队的区域和团队的迭代是不相交的。我认为您可以将不同的产品领域(网站,服务,实用程序)分配给团队,但是只有一个迭代列表,而不必尝试按区域隔离迭代。如果不同区域的冲刺日期不同,则无法使用此方法,但是如果它们不同,则我认为您尝试在应用程序中尝试使用的任何方法都不会起作用。
区域:
Sandbox
|__Team
|___Websites
|___Services
|___Utilities
迭代次数:
Sandbox
|__Sprint 1
|__Sprint 2
|__Sprint 3
即使您可以使用该工具使某些产品可行,但如果不同产品区域的sprint开始/结束日期不同,我认为您不会找到一个好的解决方案。