This project has moved and is read-only. For the latest updates, please go here.

Structure for large amounts of customisations per product

Jun 19, 2013 at 3:04 PM
Edited Jun 19, 2013 at 3:08 PM
Hi,

I am working with a customer who is building 1 (or more) core products using TFS2012 which they will "supply" to another department within the organisation. This other department will, in turn then customise the product (including code changes if necessary) for individual customers. These customisation projects could number in the 100's. The organisation would like to share all of the artifacts from the core product with the customisation project (including test cases) so that they can be used for regression testing etc. The process template is a customised version of CMMI.

I am wondering if anyone has any opinions on what I see as my two options (or if there are options I have not considered):

1 Create new team projects branched from the core product.
'+ Shared work items build resources
'+ Ability to push bug fixes
'- May hit PC project limit
'- Managing security

2 Create a separate project collection and create a custom application based on the TFS integration platform to create and update team projects as a copy of the core project.
'+ No problem PC project limit
'+ Managing security
'+ Work Items only a copy
'+ No current support for Test cases in TFS IP as well as limited support for TFS2012 from what I can see on the blogs.

Thanks in advance for any guidance!

John.

WOW the rendering was a long way from what I wrote originally! Fixed now.