MSF for CMMI Process Improvement 5 – Process Guidance in Word format

Well people loved the MSF for Agile Word doc that I posted so much, I thought I’d go ahead and post my Word doc of the CMMI process also.

I think the CMMI process gets a bad wrap because, well, it has the CMMI name in it. CMMI has become synomous with heavyweight, formal processes that developers hate, but this process is still iterative and lightweight. Plus it provides you with rich Work Items such as Change Requests (an almost necessary evil). So give it a go too, you never know… it might fit better than the Agile template!
MSF for CMMI Process Improvement v5 – Process Guidance

Updated it on 12/13/2010

MSF for CMMI Process Improvement v5 – Process Guidance


About Leonard Woody
Software Engineer

3 Responses to MSF for CMMI Process Improvement 5 – Process Guidance in Word format

  1. Sherman says:

    I would like to know how you handle a change to a requirement that already exist.

    From my point of view a change request should be created to identify there is a change to the requirement. Then the legacy requirement should be moved into the development cycle and updated. As part of the requirement there should be a revision log and development/test task assigned to the requirement.

    Reading your document it appears when you are speaking of task assigned to the change request they are closely related to analysis and the creation of new requirements.

    A couple of points of interest. UAT is part of a requirement not a Change Request. If you are a developer and you have to go back to a requirement it is more simplistic to have the complete requirement in one location then to open each change request against that requirement to assemble the current state of the requirement. (We have a customer who changes their needs almost every iteration. In some cases we have had 8 change request in 8 separate iterations).

    So back to my original question; how would you recommend handling a change to existing requirement?

    • Good points about change requests. Just to clear though, I did not write this document; Microsoft did 🙂
      It’s a hard question, how to handle multiple change requests. Maybe after a certain point (e.g. 4 change requests), you go ahead and write a new requirement? If it’s a Use Case, I would keep it in SharePoint and then just create a hyperlink to it from the work item. That way, the developer could always get the most up to date requirement and you would have versioning. Food for thought….

  2. How to Download process Template for TFS 2010. Any direct Link?

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: