Choose a process
Team Services | TFS 2015 | Previous versions
Anytime you create a team project, you must choose a process (formerly referred to as a process template).
A process defines the building blocks of the work item tracking system as well as other sub-systems you access through Team Services or the web portal for an on-premises Team Foundation Server (TFS).
Agile, CMMI, and Scrum
The three default processes differ mainly in the work item types (WITs) they provide for planning and tracking work. Scrum is the most light-weight and CMMI, which stands for Capability Maturity Model Integration, provides the most support for formal processes and change management.
Choose the process that provides the best fit for your your team.
Choose Scrum when your team practices Scrum. This process works great if you want to track product backlog items (PBIs) and bugs on the Kanban board, or break PBIs and bugs down into tasks on the task board.
This process supports the Scrum methodology as defined by the Scrum organization.
Tasks support tracking remaining work only.
Choose Agile when your team uses Agile planning methods, including Scrum, and tracks development and test activities separately. This process works great if you want to track user stories and (optionally) bugs on the Kanban board, or track bugs and tasks on the task board.
You can learn more about Agile methodologies at the Agile Alliance.
Tasks support tracking Original Estimate, Remaining Work, and Completed Work.
Choose CMMI when your team follows more formal project methods that require a framework for process improvement and an auditable record of decisions. With this process, you can track requirements, change requests, risks, and reviews.
This process supports formal change management activities. Tasks support tracking Original Estimate, Remaining Work, and Completed Work.
Main distinctions among the default processes
The default processes are designed to meet the needs of most teams. If your team has unusual needs and connects to an on-premises TFS, you can customize a process and then create the team project. Or, you can create a team project from a process and then customize the project.
The following table summarizes the main distinctions between the WITs and states used by the three default processes.
|Product planning (see note 1)|
|Portfolio backlogs (2)|
|Task and sprint planning (3)|
|Bug backlog management (1)|
|Issue and risk management|
You can add these WITs from the product backlog or Kanban board. The product backlog shows a single view of the current backlog of work that can be dynamically re-ordered and grouped. Product owners can quickly prioritize work and outline dependencies and relationships.
Also, each team can configure how they want bugs to show up on their backlogs and boards.
With portfolio backlogs you can define a hierarchy of backlogs to understand the scope of work across several teams and see how that work rolls up into broader initiatives. Each team can configure which portfolio backlogs appear for their use.
You can define tasks from the sprint backlog and task board. With capacity planning, teams can quickly determine if they are over or under capacity for a sprint.
Workflow states, transitions, and reasons
Workflow states support tracking the status of work as it moves from a new state to a closed or a done state.
Each workflow consists of a set of states, the valid transitions between the states, and the reasons for transitioning the work item to the selected state.
The following diagrams show the typical forward progression of those WITs used to track work and code defects for the three default processes. They also show some of the regressions to former states and transitions to removed states. Each image shows only the default reason associated with the transition.
Product backlog item
Most WITs used by Agile tools, ones that appear on backlogs and boards, support any-to-any transitions. You can update the status of a work item using the Kanban board or the task board by dragging it to its corresponding state column.
Removed, Closed, and Done states
When you change the state of a work item to Removed, Closed, or Done, the system responds like this:
- Closed or Done: Work items in this state don't appear on the portfolio backlog and backlog pages. However, they do appear on the sprint backlog pages, Kanban board, and task board. Also, when you change the portfolio backlog view to show backlog items, for example, to view Features to Product Backlog Items, items in the closed and done state will appear.
- Removed: Work items in this state don't appear on any backlog or board.
Work items are maintained in a team project as long as the team project is active. Even if you set them to Closed, Done, or Removed, a record is kept in the data store. You can use a record to create queries or reports.
If you need to permanently delete work items, see Remove or delete work items.
Work item types added to all processes
The following WITs are the same across all processes.
Teams create and work with these types using the corresponding tool:
- Test Plan, Test Suite, Test Case Shared Steps, and Shared Parameters: Microsoft Test Manger.
- Feedback Request and Feedback Response: Request feedback.
- Code Review Request and Code Review Response: My Work (from Team Explorer) and Code Review Request.
Work items from these type definitions are not meant to be created manually and therefore are added to the Hidden Types category. Work item types that are added to the Hidden Types category don't appear in the menus used to create new work items.
Note: If you upgraded your team project from TFS 2013 or an earlier version to the current version of TFS, you might have to add WITs that didn't exist in the earlier versions. For more information, see Configure features after a TFS upgrade.
WITs that support the test experience
WITs that support the test experience and work with Test Manager and the TFS web portal are linked together using the link types shown in the following picture.
From the web portal or Test Manager, you can view which test cases are defined for a test suite, and which test suites are defined for a test plan. However, these objects aren't connected to each other through link types. You can customize these WITs as you would any other WIT. See Customize work tracking objects to support your team's processes.
If you change the workflow for the test plan and test suite, you might need to update the process configuration as described here. For definitions of each test field, see Build and test integration field reference.
Depending on whether you're working in the cloud or on-premises, you can learn more about how to manage your process or process template from these articles.
|Create a team project||Create a team project|
|Add an inherited process, migrate team projects to a process||Upload or download a process template|
To access the latest versions of TFS process templates, first install the latest version of Team Foundation Server.
|Customize a process||Customize a process template|
|N/A||Configure an existing team project with new features|
Terminology note: Both "process" and "process template" refer to an interdependent set of files used to create a team project.
If you have additional questions, search for answers or post a question in the Team Foundation Server - Team Project and Work Item forum.