Process Templates

In Team Foundation Server (TFS)—now evolved into Azure DevOps Server—a Process Template defines the rules, workflow, work item types, and project structure used to manage software development projects.

What is a Process Template?

A Process Template in TFS is a predefined package that includes:

• Work item types (Bug, Task, User Story, etc.)
• Workflow states (New → Active → Resolved → Closed)
• Project lifecycle rules
• Reports and dashboards
• Security settings
• Agile planning structure

It determines how your team tracks work from idea → development → release.

Main Process Templates in TFS

TFS traditionally provides three built-in process templates:

1. Agile Process Template

Designed for flexible and iterative development.

• Work items: User Stories, Tasks, Bugs
• Lightweight process
• Continuous feedback encouraged
• Supports Scrum-like iterations but less strict

Workflow example: New → Active → Resolved → Closed

Best for: Fast-moving teams, Startups, Projects requiring flexibility

2. Scrum Process Template

Based on the Scrum framework.

• Work items: Product Backlog Item (PBI), Task, Bug
• Uses Scrum terminology
• Sprint-based planning
• Strong focus on velocity and backlog

Workflow example: To Do → In Progress → Done

Best for: Teams strictly following Scrum, Sprint-based development, Agile maturity teams

3. CMMI Process Template

Stands for Capability Maturity Model Integration

• Work items: Requirement, Change Request, Risk, Bug
• Highly structured and formal
• Strong documentation and approvals
• Includes compliance tracking

Workflow example: Proposed → Approved → In Progress → Resolved → Closed

Best for: Large enterprises, Government or regulated industries, Projects requiring strict governance

What’s Inside a Process Template?

A process template includes several components:

1. Work Item Definitions

Defines types like:

• Bug
• Task
• Requirement
• User Story

2. Workflows

Defines states and transitions:

• New → Active → Closed
• With rules for movement

3. Areas & Iterations

Used for:

• Team structure (Area Path)
• Sprint planning (Iteration Path)

4. Reports & Dashboards

Includes:

• Burndown charts
• Velocity charts
• Progress reports

5. Security Settings

Defines:

• Permissions
• Role-based access control

Why Process Templates Matter

They ensure:

• Consistent project tracking
• Standardized workflows across teams
• Better reporting and analytics
• Alignment with Agile/Scrum/CMMI practices

Simple Analogy

Think of a Process Template like: A construction blueprint for a software project management system

• Agile = flexible house design
• Scrum = structured apartment plan
• CMMI = highly regulated commercial building design