Scrum process template artifacts in Visual Studio Options

codeling Posts: 1089 Points: 4569
Posted: Monday, March 25, 2019 1:40:58 PM

Anytime you create a project in Visual Studio TFS, you must choose a process or process template based on the process model you use. A process or process template defines the building blocks of the work item tracking system work item tracking system as well as other sub-systems.

Basic is the most lightweight and is in a selective Preview. Scrum is the next most light-weight. Agile supports many Agile method terms, and CMMI, which stands for Capability Maturity Model Integration, provides the most support for formal processes and change management.

The work tracking objects contained within the default processes and process templates—Basic, Agile, CMMI, and Scrum—are the same and are summarized below.

Basic

Choose Basic when your team wants the simplest model that uses Issues, Tasks, and Epics to track work.

Tasks support tracking Remaining Work.

Basic work item types

Agile

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 taskboard.

Tasks support tracking Original Estimate, Remaining Work, and Completed Work.

Agile work item types

Scrum

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 taskboard.

Tasks support tracking remaining work only.

Scrum work item types

CMMI

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.

CMMI work item types

codeling Posts: 1089 Points: 4569
Posted: Monday, March 25, 2019 1:46:03 PM

The Scrum process supports the following work item types (WITs) to plan and track work, tests, feedback, and code review. With different WITs you can track different types of work—such as product backlog items, tasks, bugs, and more. These artifacts are created when you create a project using the Scrum process. They are based on Scrum principles and values.

Scrum process work item types, conceptual image 

 


codeling Posts: 1089 Points: 4569
Posted: Monday, March 25, 2019 2:02:35 PM

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 server, you can customize a process and then create the project. Or, you can create a 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.

Tracking area Basic Agile Scrum CMMI
Workflow states
  • To Do
  • Doing
  • Done
  • New
  • Active
  • Resolved
  • Closed
  • Removed
  • New
  • Approved
  • Committed
  • Done
  • Removed
  • Proposed
  • Active
  • Resolved
  • Closed
Product planning (see note 1)
  • Issue
  • User story
  • Bug (optional)
  • Product backlog item
  • Bug (optional)
  • Requirement
  • Bug (optional)
Portfolio backlogs (2)
  • Epic
  • Epic
  • Feature
  • Epic
  • Feature
  • Epic
  • Feature
Task and sprint planning (3)
  • Task
  • Task
  • Bug (optional)
  • Task
  • Bug (optional)
  • Task
  • Bug (optional)
Bug backlog management (1)
  • Issue
  • Bug
  • Bug
  • Bug
Issue and risk management
  • Issue
  • Issue
  • Impediment
  • Issue
  • Risk
  • Review

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.

Agile Scrum CMMI

Epic

Epic workflow states, Agile process

Epic

Epic workflow states, Scrum process

Epic

Epic workflow states, CMMI process

Feature

Feature workflow states, Agile process

Feature

Feature workflow states, Scrum process

Feature

Feature workflow states, CMMI process

User story

User story workflow states, Agile process

Product backlog item

Product backlog item workflow states, Scrum process

Requirement

Requirement workflow states, CMMI process

Bug

Bug workflow states, Agile process

Bug

Bug workflow states, Scrum process

Bug

Bug workflow states, CMMI process

Task

Task workflow states, Agile process

Task

Task workflow states, Scrum process

Task

Task workflow states, CMMI process

 

 

Users browsing this topic
Guest