How would we go about converting an agile project to a CMMI project

How would we convert a project from an agile method to a CMMI project without losing all of our work items?

[108 byte] By [barton] at [2007-12-17]

«« FormattedText and DrawText location point
»» DataGridView: Scrolling to Selected row

# 1

You commit to a project type on project creation. There's no "change" project type feature. We're not anticipating many people will attempt to completely re-set a methodology mid-project. Although I can imagine this is possible, a feature to help would be handy, we don't have it. But your question makes me think of an even more significant case where we'll find this behavior required -- upgrading an ongoing project from Agile 1.0 to Agile 1.1. Stay tuned.

KevinC.Kelly at 2007-9-9 >

top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...

# 2

As Kevin said, this is not something that the tool was designed for as it's not a normal thing to do. You'd think the work items in one process would be very different to those in another.. If you really wanted to do this, then it isn't a matter of just porting the data over, you'll have to manually manipulate it.

What you can do is create a new project in VSTS following the CMMI process. You can export all your work items from your old agile project into Excel. You will then need to copy that data into a new spreadhseet and do some bulk changes to the work items in excel to get them to fit into the CMMI process work item types. Once you have the data as you want it you can then open a third sheet and connect it to your new project. You can then copy/paste all the data across and publish your work items. As certain types can only be in certain states when they are created you may need to copy some of the columns a second time and re-publish.

This is exactly how we moved work items from early versions of VSTS into Beta 2. You loose all your history, but it does the job. You gotta love the Excel integration for doing bulk updates!!

MartinWoodward at 2007-9-9 >

# 3

Another option is to manually port all of the CMMI processes into your existing Agile project. You could download the CMMI process template locally (via the Process Template Manager), and then extract its content and manually apply it to your existing project. Use WITImport.exe to bring in the CMMI work item types to your existing project, over-ride the Agile process guidance and document templates with the CMMI process guidance by uploading it to the right location on the SharePoint server, and upload the CMMI reports to the existing project. It is a very manual process, but you'd still be working on the same project and thus wouldn't lose your work items.

-Amy

AmyRHagstrom at 2007-9-9 >

# 4

Amy,

Is there any downfall using your approach versus the approach stated in the previous reply from Martin Woodward.? We are fairly new in our use of TFS and began with Agile about a month ago. We have about 500 work items, many of them completed or closed. We are not concerned yet at this point in losing history since our development team just began using Tasks and Bugs last week after our migration from VSS to TFS Source Control. CMMI definitely suits our process better than Agile so we are going to migrate no matter what, but wanted to get input on other's experiences. Thanks in advance for any suggestions you can offer.

Jennifer

JenniferS at 2007-9-9 >

Visual Studio Team System Hot Topic

Visual Studio Team System New Topic

Visual Studio Team System

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech