Anyone an azure devops expert?
If you managed a small team covering multiple varied software dev products covering categories of customer solutions, internal business applications and infrastructure how would you structure it?
Single project, each product is an area path, custom field for categories
Single project, categories are area paths, custom field for products
One project per product
Something else
I'm erring on side of single project because I need overall visibility of all activity at any one time and because that's Microsoft's recommended approach, however I can set draw backs to it.
Comments
Oooh arrrr m'hearties, I be looking for a map that marks the spot where the Azure ops of dev be laying. I be paying 1 wiz for ye troubles. Arrrrr.
Anyway, have you considered a single project containing a hierarchy of areas, with top level areas representing categories, sub-divided into child areas for each product in that category?
Custom fields don’t seem necessary for what you’re trying to achieve.
As for categories, if there is little intrinsic value to them other than a label, then have them as a custom field, and create all the project Areas as a flat structure. But if you want to leverage the extra management capabilities that an Area provides for each category (historic stats? Dashboard widgets? I'm just guessing here as I've never used Devops) then it might make sense to have a hierarchy of Areas. It's up to you.
Feedback
My feedback thread is here.