This post invites you for input on a possible scenario we are considering as part of the guidance for the VSTS Rangers TFS Migration Tools project, which is listed as one of the VSTS Rangers initiatives mentioned in the index post here. We would appreciate your candid input, either by adding a comment to this blog post, or by contacting me directly.
The illustration shows a hypothetical scenario with two team projects, one based on the CMMI process template and the other on Agile. The Version Control (VC) data is migrated/synchronised as is, while the Work Item Tracking (WIT) data is migrated/synchronised with a re-mapping/translation between CMMI and Agile.
While there are other tools focused on Work Item Tracking data mapping, export and import, we are investigating the feasibility of including this specific scenario in our migration guidance and making it available as a viable scenario in the TFS Migration Tools solution. The latter is obviously not just focused on Work Item Tracking (WIT) data, but migration/synchronisation of Version Control (VC) and linking between WIT and VC as well.
So what are the questions?
- Do you have environments that would like to move a team project from one project template, i.e. CMMI, to another project template, i.e. Agile? This is typically a result of a team project team selecting one process template and realising during the development cycle that they selected the wrong process template, or alternatively by organisational changes that are linked with methodology changes.
- If you answered yes to (1), which process templates would be most relevant?
- Would there be a need to synchronise two team projects with different process templates, or would the need be primarily a migration from type A to type B?
Thanking you for your candid feedback!