TFS & Visual Studio ALM – by Neno Loje

(formerly Team System, VSTS)

Workflows of MSF Agile and CMMI Process Templates for TFS

January 8th, 2009 · 3 Comments · 1531, Microsoft Solution Framework (MSF), Project Management with TFS, Team Foundation Server, TFS Process Customization

When trying to decide which of the two MSF Process Templates – Agile vs. CMMI Process Improvement – for TFS is the right starting point for your company, it helps to compare the work item types and its workflows.

You can download the full guidance from:

MSF for Agile Software Development

featuring 5 work item types: Bug, Requirement, Quality of Service Requirement (QoS), Risk and Task.

Work Item Type: Bug

msfagile_wi_bug_flow

Work Item Type: Scenario

msfagile_wi_scenario_flow

Work Item Type: Quality of Service Requirement (also known as “technical requirement”)

msfagile_wi_qos_flow

Work Item Type: Risk

 msfagile_wi_risk_flow

Work Item Type: Task

 msfagile_wi_task_flow

MSF for CMMI Process Improvement

featuring 7 work item types: Bug, Requirement, Change Request, Issue, Review, Risk, Task

Work Item Type: Bug

cmmi_bug

Work Item Type: Requirement

cmmi_requirement_wit

Work Item Type: Change Request

cmmi_change_request

Work Item Type: Issue

cmmi_issue_wit

Work Item Type: Review

cmmi_review_wit

Work Item Type: Risk

cmmi_risk_wit

Work Item Type: Task

cmmi_task      

As a personal note:

Both templates are a great starting point. The agile template might be a bit more lightweight whereas the CMMI template might fit more the vocabulary and processes that you are used to.

However, both are really just a starting point. In customizing the process you get way more out of TFS than with just using the built-in process templates.

Tags:

3 Comments so far ↓

  • John Calvert

    Can anyone point to a further comparison of these two process templates, covering more than the differences in work item workflow?

  • Paul Croteau

    Looking at the workflow for Bug. (I do not think that you can go from “Active” to “Closed”. In Active state, Developers have control and are reviewing Bug. Developers should NOT be allowed to close a bug. I think this is just an error in the diagram.

  • neno

    @Paul: it’s not an error in the diagram, that’s the way the template works. You can easily customize it, and add permissions to the transition from Active to Closed for example.

Leave a Comment