Capturing work in parallel groups in ADO
There is no relevant tag for Azure DevOps (or TFS)
I have an engineering group configured, with teams and paths. In parallel I have a product group configured - with teams and paths. Each has 2-3 team leads and 6-10 team members.
Both need to use the their own area paths as they have their own items to manage, BUT - at times the product needs an item to move to the engineering as it belongs there - for backlog, boards and sprint use (as the product don't really need those - it's more of an action item list for them).
What would be the best way to capture this work in both groups if - it must be in the engineering backlog hence should have the relevant area path, but also stay in the focus of the product? For backlogs, boards and sprints - would the best solution be for both teams to have both area paths defined and only filter out what is not relevant specifically? and hence should each stay with its original area path?
Or should the product change the area path to suit the engineering needs and manage their items in a custom quarry or a delivery plan?
And then for a delivery plan - I can add teams and have a specific plan per epic\feature?
What would be the best practice?
Sign in to comment