My company are trying to use CMMI in TFS for our development.
In CMMI is used a Change Control Board, a board of people deciding which changes that can be included in the next release.
The way I am planning to work is to make a developer branch where all developers deliver there work.
My job as a configuration manager is to make a list of all changes (as workitems) to the configuration board, so they can decide which workitems they want to include in the next build. Then I cherry-picking the workitems and merge them into the last release in another branch.
My question is, how do I find dependencies between the changesets (Seen from a workitem point of view)
Developer one, creates a date converter function in a common func package and check it in with a association to workitem #1
Developer two, creates a screen using the date function created in workitem #1, he checks it in with a association to workitem #2
Developer three creates another screen using the common func package but not the date convertion func.
Now I want to create a report to the change control board stating which workitems there are ready to include in the next build.
The report I need is one saying that if I want workitem 2 to be included I have to pick workitem #1 as well due to dependencies.
I don’t need to include workitem #1 if I only will include workitem #3 because it can use an old version of the common package.
Is there a way to do this in TFS
Is there any form of warning if I try to merge a workitem that have a dependency that are not included
Visual Studio Team System38