Design of TFS Kanban

Column

The entire process of product development, for example, is to configure the process to a column of Kanbans:

Demand Pool--ready-to-develop-------------off

In general, the bug and requirements on a piece of the processing, work items have their own state, can be adjusted through the template settings, but not recommended (configuration is more difficult, and the more common), so here work items need to correspond to the Kanban column, so that in the Kanban operation can use the process to do some default data filling (for example, assigned to, time, and so on), the Kanban column and status correspondence are as follows:

type \ column	Demand Pool	Ready	Development	Test	Pending Acceptance	Pending Release	is closed
Demand	New	New	Activities	has been resolved	has been resolved	has been resolved	is closed
Bug	New	New	Activities	has been resolved	has been resolved	has been resolved	is closed

Lane

Sequentially from top to bottom, in order

1. Insert events: Urgent release requirements, bugs, or urgent issues to resolve
2. BUG: Demand defect or data defect
3. Requirements: Only the requirements of the current iteration are placed

WIP restrictions

It's best to do one thing at a time, whether you're developing or testing. If two pieces are processed at the same time, then there are generally two cases

1. There is an impediment to the cessation of a certain thing (need other people to help solve).
2. Two things are relatively strong (unreasonable demand splitting).

Both of these problems need to be exposed and resolved in a timely manner.

An important role in product restriction is to find the problem in time and find out the root of the problem to solve and improve it. The corresponding limit for each column is as follows (0) is unlimited, the initial setting can do two things for each person at the same time, according to the actual use of the team can be adjusted;

Demand Pool	Ready	Development	Test	Pending Acceptance	Pending Release	is closed
0	0	Number of developers x2x (whether split: yes-2, no-1)	Number of test x2x (whether split: yes-2, no-1)	0	0	0

Card Design User Story fields

1. Id
2. Assigned person
3. Story Point
4. Mark
5. Zone path
6. Priority level
7. Status Update Date

New requirement (beige) in front of style

1. Iteration date [email protected] current iteration
2. Date Created ≥@ today-1

3-day work item without progress (orange)

Iteration Date = Current iteration
Change date ≤ current date-3
State ≠ new
Board ≠ pending release

Bug Field

1. Id
2. Assigned person
3. Story Point
4. Mark
5. Zone path
6. Severity level
7. Status Update Date

Style 3-day unresolved bug (yellow)

1. Activation date ≤ current date-3
2. Status ≠ (new, closed)

Submitted 2 months ago not closed bug (red)

1. Creation date ≤ current-60
2. Status ≠ is turned off

Serious bug that is not currently closed (purple)

1. Iteration Date = Current iteration
2. Status ≠ is turned off
3. Severity level = Critical

Task field

1. Id
2. Assigned person
3. Remaining Work
4. Mark
5. Activities
6. Initial estimate

Style initial estimate more than 8 hours (red)

1. Initial estimate >8

Design of TFS Kanban