How feasible is it to add a traditional template to the Agile template?
We have created our own customised process template based on the traditional template. We may need to have a mixture of Project Areas based on our customised traditional template and some using the out-of-the box Agile template.
It has been suggested whether we could merge our customised traditional template into the Agile template to maintain a single process template. This would involve adding our custom work item types, roles and permissions to the Agile template so long as each template used unique names. Would there be any issues with task management.
I realise it may give a maintenance issue every time we upgraded RTC if the Agile process changed.
The Users in each Project Area would still operate either a traditional process or Agile process but not a mixed at the same time.
Is this sensible or feasible to do?
Accepted answer
Yes, it is feasible to merge the processes of two project areas, but it would be a manual process, not an automated one.
Whether it is sensible to do is largely based on how different those processes are.
If they are very different, then you will need to negotiate with the development teams about what would be a logical merge, and each team would be presented with the work item types of the other team that they would need to just ignore. On the other hand, to the extent that you can get the two types of teams to agree on a merged process, the easier it will be for those two kinds of teams to interact.
So if you can get the teams to agree on a large common set of work item types, then it might be worth the effort, but if you cannot, then it is best to just maintain two different project area templates with largely distinct work item types.
Whether it is sensible to do is largely based on how different those processes are.
If they are very different, then you will need to negotiate with the development teams about what would be a logical merge, and each team would be presented with the work item types of the other team that they would need to just ignore. On the other hand, to the extent that you can get the two types of teams to agree on a merged process, the easier it will be for those two kinds of teams to interact.
So if you can get the teams to agree on a large common set of work item types, then it might be worth the effort, but if you cannot, then it is best to just maintain two different project area templates with largely distinct work item types.
One other answer
I actually don't see any benefit of the merging. It can be confusing to the end users, to start with. They will ask questions like "why can I use this, but not that". It's not easy to maintain either, as you may have the same confusion as the end users.
Comments
1 vote
