VSTS | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013
The Microsoft Agile glossary is a short dictionary of terms used in tracking work using Agile tools on the Visual Studio Team Services (VSTS) and Team Foundation Server platforms. See also:
A family of engineering best processes with a goal of enabling rapid delivery of high-quality software and a business approach that aligns development with customer needs and company goals. In this paradigm, frequent inspection and adaptation is necessary, with teamwork, self-organization, and accountability all critical to project success.
A suite of web-based tools used to track work and support Agile methodologies. Agile tools support the core Agile methods—Scrum and Kanban—used by software development teams today. Learn more: About Agile tools and Agile project management.
Area paths allow you to group work items by team, product, or feature area. Whereas, iteration paths allow you to group work into sprints, milestones, or other event-specific or time-related period. The area path allows you to define a hierarchy of paths. Learn more: About area and iteration paths.
A type of work item that records a potential source of dissatisfaction with the product. The common name of a work item type for tracking code defects.
Groups one or more work item types to support flexible reporting, queries, and other functions made available through Agile tools. Categories support the process configuration used by the web portal backlog and task board pages. For example, you can add custom work item types to the Requirements category and manage them using the product backlog and Kanban boards. To learn more, see Use categories to group work item types.
User-configurable interactive signboards that provide real-time information. Dashboards are associated with a team and display configurable widgets to display information. Learn more: Add and manage dashboards.
A method for tagging an object to support quick navigation by yourself or other team members. You can tag work item queries and build definitions as personal and team favorites. Other objects you can favorite for yourself only include code branches, delivery plans, test plans, and teams or projects. Learn more: Set personal or team favorites.
Supports tracking a piece of information about the work to perform. Values you assign to a field are stored in the work tracking data store which you can query and generate charts to view status and trends. Your project contains 100 or more data fields. You update data by modifying the data field within a work item. Each work item is associated with a work item type (WIT), and the data you can track corresponds to the fields assigned to the WIT. For a definition of each predefined field, see Work item field index.
A tool for tagging specific work items or pull requests for which you want to receive email updates when changes are made to them. Learn more: Follow a work item or pull request.
Defines a list of menu items or pick list items that are shared across WITs and projects within a project collection. Global lists help to minimize the work that is required to update lists. You can define global lists within WITs that you upload with your process template. Learn more: Manage global lists for work item types. (Only supported for Hosted XML and On-premises XML process models)
Specifies both work item fields and global lists that multiple projects and types of work items can share. Learn more: Manage global workflow (Only supported for On-premises XML process model).
Hidden types categories
Specifies the set of work item types that you don't want users to create manually. By default this set includes:
- Code Review Request and Code Review Response
- Feedback Request and Feedback Response
- Shared Steps and Shared Parameter
- Test Plan and Test Suite
You can use TFS Team Project Manager, an open-source client available from github to quickly determine which WITs belong to the Hidden Types Category.
Hosted XML process model
The Hosted XML process model provides support for customizing work tracking objects and Agile tools for a project by modifying and importing a process template. This process model is only available for select accounts hosted on the Visual Studio Team Services cloud platform. To learn more, see Hosted process model.
Inheritance process model
The Inheritance process model provides support for customizing work tracking objects and Agile tools for a project through the user interface. This process model is only available for accounts hosted on the Visual Studio Team Services cloud platform. Projects inherit the customizations made to a process. To learn more, see Inheritance process model.
Iteration paths (aka sprints)
A time period, usually two to three weeks, used to group work items to be completed during that time period. Sprints are used in Scrum methods to support sprint planning, sprint burndown, and other Scrum processes. Iteration paths allow you to group work into sprints, milestones, or other event-specific or time-related period. Learn more: About area and iteration paths.
An interactive, electronic sign board that supports visualization of the flow of work from concept to completion and lean methods. Learn more: Kanban basics.
Specifies an object used to form link relationships between different WITs. Learn more: Link work items to support traceability and manage dependencies and LinkTypes elements reference.
On-premises XML process model
The On-premises XML process model provides support for customizing work tracking objects and Agile tools for a project. With this model, you can update the XML definition of work item types, the process configuration, categories, and more. You can also update the attributes of fields. This process model is only available for on-premises TFS. To learn more, see On-premises process model.
Specifies an enumerated set of values that appear within a drop-down menu in a work item form and the Value column within the query editor. The method you use to customize a pick list varies depending on the field and the process model.
Plans (aka delivery plans)
A configurable view that displays work from multiple teams and projects laid out within a calendar based on each team's iterations. Each row in the view represents the work from a team's product or portfolio backlog, with each card corresponding to a work item—user story, feature, or epic. Learn more: Review team delivery plans.
An interactive list of work items, similar to the product backlog, that supports organizing or grouping work under features, epics, or scenarios. Portfolio backlogs work similarly to product backlogs in that you can prioritize work and view the tree hierarchy of work. Learn more: Define features and epics.
Defines the building blocks of the work tracking system. To customize a process, you first create an inherited process from one of the default system processes—Agile, Scrum, or CMMI. Changes you make to a process are seen by all projects that use it. Learn more: About process customization and inherited processes.
Specifies the default configuration and functional capabilities that your teams can access using the Agile tools. These web portal tools include the product backlog, sprint backlogs, Kanban board, and task board. (Only supported for Hosted XML and On-premises XML process models)
The work tracking customization method supported by your organization or collection. One of three process models are supported, Inheritance and Hosted XML for VSTS and On-premises XML for on-premises TFS. Learn more: Customize your work tracking experience
Specifies an inter-related set of files that contain the XML definitions for tracking work and defining the initial configuration of other functional areas. The system provides three default process templates—Agile, Scrum, or CMMI. You can create a project and then customize it, or customize a process template that you then use to create a project. (Only supported for Hosted XML and On-premises XML process models)
An interactive list of work items that corresponds to a team's project plan or roadmap for what the team plans to deliver. The product backlog supports prioritizing work, forecasting work by sprints, and quickly linking work to portfolio backlog items. You can define your backlog items and then manage their status using the Kanban board.
Each product backlog can be customized by a team. Learn more: Create your backlog.
Product backlog item
A type of work item that defines the applications, requirements, and elements that teams plan to create. Product owners typically define and stack rank product backlog items which are defined with the Scrum process. Learn more: Scrum process work item types and workflow.
A project (previously referred to as a team project) provides a repository for source code and a place for a group of people to plan, track progress, and collaborate on building software solutions. A project is defined for a VSTS organization or within a TFS project collection. It provides support for focusing on those objects defined within the project. Learn more: About projects and scaling your organization.
A query supports finding and listing work items. Queries are used to support managed searches which you can use to triage work versus adhoc searches used to find a specific work item. Learn more: About managed queries.
Sprints (aka Iterations)
A time period, usually two to three weeks, used to group work items to be completed during that time period. Sprints are used in Scrum methods to support sprint planning, sprint burndown, and other Scrum processes. Sprints are defined via Iteration Paths. Learn more: About area and iteration paths (aka sprints).
An interactive list of work items that have been assigned to the same sprint or iteration path for a team. The sprint backlog supports teams that use Scrum methodologies. Learn more: Sprint planning.
An interactive board of work items that support reviewing and updating tasks defined for the sprint backlog. The task board supports teams that use Scrum methodologies. Learn more: Update and monitor your Taskboard.
A team corresponds to a selected set of project members. With teams, organizations can sub-categorize work to better focus on all the work they're tracking within a project. Each team gets access to a suite of Agile tools. These tools provide teams the ability to work autonomously and collaborate with other teams across the enterprise. Each team can configure and customize each tool to meet their work requirements. Learn more: About teams and Agile tools.
A type of work item that defines the applications, requirements, and elements that teams plan to create. Product owners typically define and stack rank user stories. User story is defined with the Agile process. Learn more: Agile process work item types and workflow.
Widgets display information and charts on dashboards. Many of them are configurable and display information available from one or more data stores or charts created by the system. Learn more: Widget catalog.
Work item types (WITs)
A WIT specifies the fields, workflow, and form used to track an item of work. Each WIT is associated with 30+ system fields and several more type-specific fields. You use work items to plan and track the work required to develop your project. For an overview of predefined WITs provided with the default processes, see Choose a process.
Workflow is an integral aspect of a work item and is defined by it's corresponding work item type. The workflow determines the logical progression and regression of work items, tracking the status of work as it progresses from a New or Active state to Closed or Completed state. It also specifies the values that appear in the drop-down menus for the State and Reason fields. Learn more: Workflow states and state categories.