http://blogs.msdn.com/b/willy-peter_schaub/archive/2009/11/27/tfs-integration-platform-asking-the-right-questions.aspxThe dust is settling after the TFS Integration Platform “Alpha” shipped, although the downloads indicate that the dust is far from over. While the platform team is working on the BETA release, the Rangers are continuing with the samples for the customen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/willy-peter_schaub/archive/2009/11/27/tfs-integration-platform-asking-the-right-questions.aspx#9929298Fri, 27 Nov 2009 07:02:18 GMT91d46819-8472-40ad-a661-2c78acb4018c:9929298Marco<p>Version Control Specific</p> <p>What migration / synchronisation type are you considering?</p> <p>Two-way SVN &lt;-&gt; TFS</p> <p>What is your definition of required history?</p> <p>Reflect history at a file-level</p> <p>What volume of data in terms of MB and number of files is involved?</p> <p>4,000 files, representing 100 MB of data</p> <p>What is the overall project structure?</p> <p>3 projects, 18 solutions</p> <p>What is the priority/ranking of migrating/sync’ing the project version control?</p> <p>What does your branching structure look like on the source?</p> <p>None.</p> <p>What does your branching structure look like on the target?</p> <p>None.</p> <p>Is it necessary to keep current parent-child relationship between branches ?</p> <p>No.</p> <p>What are the dependencies between projects ?</p> <p>Nothing special?</p> <p>What is the manual process of migrating/sync’ing the data?</p> <p>None.</p> <p>What trigger are you expecting? Manual or automatic? In case of latter timer or event based?</p> <p>Automatic, when a checkin occurs on source</p> <p>What is the evaluation and validation process and criteria? What makes the use case a win?</p> <p>Reliability and ease to setup!</p> <p>Work item Specific</p> <p>What migration / synchronisation type are you considering?</p> <p>Two-way JIRA &lt;-&gt; TFS</p> <p>What is your definition of required history?</p> <p>Per work item, maily comments are important</p> <p>What are the linking requirements?</p> <p>Be able to mark dependencies and duplications</p> <p>What volume of data in terms number of work items and revisions is involved?</p> <p>2000 work items, roughly 10 revisions/WI</p> <p>What is the overall project structure?</p> <p>1 project</p> <p>What is the priority/ranking of migrating/sync’ing the project work items?</p> <p>What does your process template (fields and states) look like on the source?</p> <p>Standard JIRA template</p> <p>What does your process template (fields and states) look like on the target?</p> <p>Custom WI which mirrors standard JIRA template</p> <p>What are the field and state mapping rules?</p> <p>1:1, mapping generally based on lookup values</p> <p>What trigger are you expecting? Manual or automatic? In case of latter timer or event based?</p> <p>Time-based (eg 10 minutes)</p> <p>What is the evaluation and validation process and criteria? What makes the use case a win?</p> <p>Reliability and ease to setup!</p> <p>Are we supposed to migrate attachments ?</p> <p>Yes</p> <p>Are there any many-to-one field mappings ?</p> <p>No</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9929298" width="1" height="1">