All geek questions in one place

VSO and several projects for one product group

We have a team of 10 developers working on a new product.

We divided this product into two team projects on Visual Studio Online. Developers can work on both projects during any sprint. Although we have two team projects, the whole team works together as one flexible unit.

Why did we do this?

  • We want individual product backlogs
  • Each project has its own product owner.

But this led to two problems:

  • We have two burns that can make it difficult to track team progress.
  • We must divide the capabilities of people between the two projects, which is not easy to do in Sprint planning, and also makes it difficult to track individual successes.

I feel this can be a common problem. Does anyone have any experience here? Any suggestions?

+6
source share
1 answer

You must have both teams in the same team project. You and Dan are creating several teams that all exist within the same team project and get their own backlogs.

http://nakedalm.com/creating-nested-teams-visual-studio-alm/

Most of my clients moved to a single team project, and I have a simple rule:

“If you have assets that are related (with assets defined as code, people, or work items), you should be on the same team project.

I just did in London, combining about 15 team projects into one so that the whole organization can work together. It was 6 teams of 12 products, all moved to one team project.

The only effective way to work together is in one bucket of work.

+12
source

Source: https://habr.com/ru/post/986545/

More articles:


All Articles