Choose a Process Template

By choosing the best process template when you create a team project, you provide your team with tools that support the way it works, and you help your team focus on quality by reducing overhead. The process template defines the set of work items, reports, and dashboards that you will use to plan and track your project.

A process template defines the types of work items that are available for tracking, in addition to the default rules, policies, security groups, and queries that team members use. As a rule, you can make your selection based on the following considerations:

• Choose Microsoft Solutions Framework (MSF) for Agile Software Development v5.0 if your team uses Agile methods and you resolve work items before closing them.

• Choose MSF for Capability Maturity Model Integration (CMMI) Process Improvement v5.0 if your team requires a rigorous audit trail and has a formal process for change management.

• Choose the Scrum process template if your team uses Scrum, manages bugs along with product backlog items during sprint planning, and wants work items and processes designed to support Scrum. You can download this process template here: Microsoft Visual Studio Scrum 1.0. You'll need to upload the process template to your team project collection.

Otherwise, you can customize a process template to meet your needs.

For more information about these process templates, see the following topics:

• Artifacts (Agile)

• Artifacts (CMMI)

In this topic

• Main Distinctions between MSF for Agile and MSF for CMMI

• Key Differences between the Agile and CMMI Workflow States

• Customizing Process Templates

Main Distinctions between MSF for Agile and MSF for CMMI

The following table summarizes the main distinctions that exist between the two MSF process templates:

Process area	MSF for Agile	MSF for CMMI	Distinctions
Workflow states	Active Resolved Closed	Proposed Active Resolved Closed	Choose MSF for Agile when your team progresses most work by changing the state of a work item from active to resolved to closed. Teams create a work item in the active state and resolve it after they complete the work. Choose MSF for CMMI when your team progresses most work by changing the state of a work item from proposed to active to resolved to closed. Teams create a work item in the proposed state, and it moves to the active state only after it has been accepted.
Product planning	User Story (Agile) Product Planning Workbook	Requirement (CMMI) Change Request (CMMI)	Choose MSF for Agile when you plan your product around user stories and story points. Choose MSF for CMMI when you plan your product based on requirements and change requests.
Iteration backlog management	Task (Agile) Iteration Backlog Workbook	Task (CMMI)	MSF for Agile provides an Iteration Backlog Workbook, which you can use to plan iterations.
Bug backlog management	Bug (Agile) Triage Workbook	Bug (CMMI)	MSF for CMMI provides additional fields for tracking symptoms and proposed fixes.
Project management	Issue (Agile) Issues Workbook	Issue (CMMI) Risk (CMMI) Review (CMMI)	With MSF for Agile, teams can track known or potential problems, impediments, or risks to the team project by creating issue work items. With MSF for CMMI, teams can track known or potential problems, impediments, or risks to the team project by creating issue or risk work items. Also, code reviews can be tracked formally using the review work item.
Test management	Test Case (Agile)	Test Case (CMMI)	Information that is tracked for test cases is basically the same for both MSF process templates. Test management reports are basically the same for both MSF process templates.
Audit trail	Supported	Supported	Choose MSF for Agile when your team is not required to support rigorous audits. Choose MSF for CMMI when your team is required to maintain a rigorous audit trail or is working toward a Capability Maturity Model Integration (CMMI) appraisal.

Key Differences between the Agile and the CMMI Workflow States

The following illustrations show the workflow states of four types of work items that are provided with the MSF for Agile and MSF for CMMI process templates. The main difference between these workflow states is that the work items from MSF for CMMI always start in a Proposed state instead of an Active state.

Also, the MSF for Agile workflow provides a simpler, two-state processfor tasks, but the MSF for CMMI workflow provides a four-state process.

MSF for Agile	MSF for CMMI
User Story State Diagram	Requirement State Diagram
Task State Diagram	Task State Diagram
Bug State Diagram	Bug State Diagram
Issue State Diagram	Issue State Diagram

Customizing Process Templates

You can customize any process template to fit your particular needs. You can also customize your team project's process after you have created it using a particular process template. You can add artifacts from one process template to use with another process template. For more information, see the following topics:

• Checklist: Plan and Track Changes to Your Process Template

• Customizing Process Templates.

• Customizing Team Projects and Processes

See Also

Concepts

Artifacts (Agile)

Artifacts (CMMI)

Other Resources

Launching a New Team Project