I didn't find a proper place to post this, hence posting it here. Please direct me to correct space/forum where I can get some opinions on below.
I tried to look for an answer but not able to finalize on the Collection/Project structure needed to be implemented in my company. Below I am going to list our current projects as brief as possible and in the end I will give two options that I have in mind. Please help me decide on the best way to move forward.
Current projects in TFS
Customer 1
Project 1 (repo/code for download)
Project 2 (repo/code for upload)
Customer 2
Project 1
Project 2
Libraries
Library 1 (Used in all Projects above and below - tools)
Library 2 (Used in Project 1 on both customers above)
Tools
Project 1
Project 2
Proposed DevOps Structure 1
Collection Customer 1
Project 1
Project 2
Collection Customer 2
Project 1
Project 2
Collection Libraries
Library 1
Library 2
Problem with above option is implementing automatic builds and having supporting DLLs in Artifacts as DLLs from Libraries Collection need to be accessed in other two collections (Customer projects). Advantage is I can have separate boards/work items and track each project efficiently.
Propose DevOps Structure 2
Collection Company
Customer 1
Project 1 (Not sure how to make this a "sub-project" but maybe I can have separate repositories?)
Project 2
Customer 2
Project 1
Project 2
Libraries
Library 1
Library 2
Above I can store all DLLs accessed by projects in Artifacts and use that while creating build/pipelines. But issue is how can I create boards/work items for each project (sub-project) under a main project (customer 1) and track separately?