Hello all, I am trying to get a mental model for how to layout my Azure Devops Instance.

• I will have 2-4 teams of developers working on a single Corporate Initiative.
  
• We will be starting from scratch as we develop.
• We will be building Microservices in mono-repo fashion based on bounded contexts
• There will no doubt be code that is cross cutting across several of the mono repos (like a common logging library-- please don't argue the Logging library aspect of this, it is only an example)
• I would like a single backlog and board for each team.

Here is what I think I have to do:

• Make a single project in Azdo
• Make Multiple teams in the Project
• Let the Teams make multiple repos (for each bounded context)
• Accept the fact that my Project is now the root for all development for all of my teams and oll of my code repos (including the logging library)

My heartburn comes with the fact that I feel like there should be a Backlog and boards at the organization level. It would seem likely that a team might in fact work on codebases from multiple projects.

Does anyone know if there is a way to do this?

I am trying to have a single backlog that all of my initiatives work is on while at the same time, having the code broken up into projects based on bounded context.

I would be OK if there is a way to merge multiple boards into a single view, but I am unaware of this feature.

Maybe I am just looking for a different mental model. If someone has a different way to look at this I would love to hear it as well

​

Thanks in advance,

​

Tal