Visualising The Flow - Revision history

Mmusij at 22:31, 10 January 2019

2019-01-10T22:31:00Z

← Older revision		Revision as of 22:31, 10 January 2019
Line 1:		Line 1:
	[[Category:Agile:Articles]][[Category:Agile:Kanban]]		[[Category:Agile:Articles]][[Category:Agile:Kanban]]

			==Value Stream Mapping==
	The Value Stream is the process flow of how work arrives at a team, what work is done in the team, and how it leaves the team. Visualising this workflow allows teams to understand waste in the system and enables decisions, enhancements and adaptations to be made to reach an optimum flow.		The Value Stream is the process flow of how work arrives at a team, what work is done in the team, and how it leaves the team. Visualising this workflow allows teams to understand waste in the system and enables decisions, enhancements and adaptations to be made to reach an optimum flow.

Mmusij: /* No Estimation */

2018-12-20T02:07:20Z

No Estimation

← Older revision		Revision as of 02:07, 20 December 2018
Line 65:		Line 65:
	[[File:Kanban_Framework06.jpg\|500px\|Kanban Framework]]		[[File:Kanban_Framework06.jpg\|500px\|Kanban Framework]]

	===No Estimation===		==No Estimation==
	If all cards are the same size, then metrics are just simply adding up the number of cards and the activity of estimation, which is rarely correct, can be bypassed and a focus on the value of the work items can be the main focus instead.		If all cards are the same size, then metrics are just simply adding up the number of cards and the activity of estimation, which is rarely correct, can be bypassed and a focus on the value of the work items can be the main focus instead.

Mmusij: /* Work Items */

2018-12-20T02:06:58Z

Work Items

← Older revision		Revision as of 02:06, 20 December 2018
Line 56:		Line 56:
	* '''Blocker Indicator''' - this may be as simple as a small red sticky note that is highly visible to help teams understand which work items have been blocked and why		* '''Blocker Indicator''' - this may be as simple as a small red sticky note that is highly visible to help teams understand which work items have been blocked and why

	===Classifications of Service===		Another common form of a work items are [[User Stories]] that have some basic structure and are used in conjunction with [[Test Driven Development (TDD)]] approaches.

			==Classifications of Service==
	Not all work items are the same, with some items being naturally more important than others and automatically placed at a higher prioritisation.		Not all work items are the same, with some items being naturally more important than others and automatically placed at a higher prioritisation.

Mmusij at 00:16, 19 December 2018

2018-12-19T00:16:07Z

← Older revision		Revision as of 00:16, 19 December 2018
Line 3:		Line 3:
	The Value Stream is the process flow of how work arrives at a team, what work is done in the team, and how it leaves the team. Visualising this workflow allows teams to understand waste in the system and enables decisions, enhancements and adaptations to be made to reach an optimum flow.		The Value Stream is the process flow of how work arrives at a team, what work is done in the team, and how it leaves the team. Visualising this workflow allows teams to understand waste in the system and enables decisions, enhancements and adaptations to be made to reach an optimum flow.

	[[File:~~Kanban_Framework02~~.jpg\|500px\|Value Stream]]		[[File:Kanban Framework02.jpg\|500px\|Value Stream]]

	==Kanban Board==		==Kanban Board==

Mmusij at 00:12, 19 December 2018

2018-12-19T00:12:15Z

← Older revision		Revision as of 00:12, 19 December 2018
Line 2:		Line 2:

	The Value Stream is the process flow of how work arrives at a team, what work is done in the team, and how it leaves the team. Visualising this workflow allows teams to understand waste in the system and enables decisions, enhancements and adaptations to be made to reach an optimum flow.		The Value Stream is the process flow of how work arrives at a team, what work is done in the team, and how it leaves the team. Visualising this workflow allows teams to understand waste in the system and enables decisions, enhancements and adaptations to be made to reach an optimum flow.

			[[File:Kanban_Framework02.jpg\|500px\|Value Stream]]

	==Kanban Board==		==Kanban Board==
Line 10:		Line 12:
	* '''Queues''' on a card wall are simply where work happens and are an active part of the process flow.		* '''Queues''' on a card wall are simply where work happens and are an active part of the process flow.
	* '''Buffers''' by comparison are where work is waiting to be pulled into the next queue.		* '''Buffers''' by comparison are where work is waiting to be pulled into the next queue.

			[[File:Kanban_Framework03.jpg\|500px\|Kanban Task Board]]

	===Concurrent and Parallel Processes===		===Concurrent and Parallel Processes===
Line 25:		Line 29:
	===Expedite Lane===		===Expedite Lane===
	Occasionally teams encounter work items that need to be worked on immediately such as production issues, for example. A simple way to represent this is to create an ''Expedite'' swim lane that clearly indicates to a team that anything that sits in this swim lane is of automatic high priority.		Occasionally teams encounter work items that need to be worked on immediately such as production issues, for example. A simple way to represent this is to create an ''Expedite'' swim lane that clearly indicates to a team that anything that sits in this swim lane is of automatic high priority.

			[[File:Kanban_Framework04.jpg\|500px\|Expedite Lane]]

	==WIP Limits==		==WIP Limits==
Line 30:		Line 36:

	Based upon queueing theory the idea is that in a particular queue or column on the task board a limit is set to the capacity or number of work items that can be done at once for that particular part of the process.		Based upon queueing theory the idea is that in a particular queue or column on the task board a limit is set to the capacity or number of work items that can be done at once for that particular part of the process.

			[[File:Kanban_Framework05.jpg\|500px\|Kanban Framework]]

	Limits can be adjusted at any time and so initially it may be the best guess to get things started, and then adjust there after.		Limits can be adjusted at any time and so initially it may be the best guess to get things started, and then adjust there after.
Line 52:		Line 60:

	To help with this colour coding the work item cards can help teams to understand which items are more important and of a higher priority over other cards.		To help with this colour coding the work item cards can help teams to understand which items are more important and of a higher priority over other cards.

			[[File:Kanban_Framework06.jpg\|500px\|Kanban Framework]]

	===No Estimation===		===No Estimation===

Mmusij: /* No Estimation */

2018-12-18T05:46:40Z

No Estimation

← Older revision		Revision as of 05:46, 18 December 2018
Line 60:		Line 60:
	* the cycle time (time taken for work items to traverse the value stream,)can be used as a Service Level Agreement (SLA) to indicate the statistical probability of how long cards of a uniform size take to complete		* the cycle time (time taken for work items to traverse the value stream,)can be used as a Service Level Agreement (SLA) to indicate the statistical probability of how long cards of a uniform size take to complete
	* work items are prioritised by business value		* work items are prioritised by business value

			==See Also==
			* [[Kanban Framework]]

			==References==
			# [https://www.amazon.com.au/Kanban-David-J-Anderson-ebook/dp/B0057H2M70 Kanban, Successful Evolutionary Change For Your Technology Business], Anderson D. J., 2013

Mmusij: /* Work Items */

2018-12-18T05:45:14Z

Work Items

← Older revision		Revision as of 05:45, 18 December 2018
Line 52:		Line 52:

	To help with this colour coding the work item cards can help teams to understand which items are more important and of a higher priority over other cards.		To help with this colour coding the work item cards can help teams to understand which items are more important and of a higher priority over other cards.

			===No Estimation===
			If all cards are the same size, then metrics are just simply adding up the number of cards and the activity of estimation, which is rarely correct, can be bypassed and a focus on the value of the work items can be the main focus instead.

			An alternative approach:
			* each work item is the same uniform size and causes the team to think in depth about the work and how to structure the tickets to achieve the outcome
			* the cycle time (time taken for work items to traverse the value stream,)can be used as a Service Level Agreement (SLA) to indicate the statistical probability of how long cards of a uniform size take to complete
			* work items are prioritised by business value

Mmusij: /* Kanban Board */

2018-12-18T05:38:18Z

Kanban Board

← Older revision		Revision as of 05:38, 18 December 2018
Line 8:		Line 8:
	Adding in queues and buffers to the card wall then provides a good representation of where work is done and where it waits ready to be pulled into the next queue.		Adding in queues and buffers to the card wall then provides a good representation of where work is done and where it waits ready to be pulled into the next queue.

	~~===Queues===~~		* '''Queues''' on a card wall are simply where work happens and are an active part of the process flow.
	Queues on a card wall are simply where work happens and are an active part of the process flow.		* '''Buffers''' by comparison are where work is waiting to be pulled into the next queue.

	~~===Buffers===~~
	Buffers by comparison are where work is waiting to be pulled into the next queue.

	===Concurrent and Parallel Processes===		===Concurrent and Parallel Processes===

Mmusij: /* Work Items */

2018-12-18T05:37:23Z

Work Items

← Older revision		Revision as of 05:37, 18 December 2018
Line 47:		Line 47:
	* '''Index or Key''' - these can be an electronic ticket reference if needed		* '''Index or Key''' - these can be an electronic ticket reference if needed
	* '''Description''' - don't be tempted to write too much, as the less is written the more the team will talk about the ticket and understand it		* '''Description''' - don't be tempted to write too much, as the less is written the more the team will talk about the ticket and understand it
	* '''Time Indicator''' - these can be ~~used~~ to indicate ~~the number of~~ days ~~that~~ a ~~ticket~~ has ~~been~~ in ~~a particular column for example,~~ and becomes a visual reference for when a team may want to place cards ~~with lots of time as~~ a higher priority over other cards		* '''Time Indicator''' - these can be simple dots added to indicate how many days a card has spent in the queue and becomes a visual reference for when a team may want to place cards at a higher priority over other cards
	* '''Avatar''' - sometimes it works well for team members to use avatars to indicate who is working on which item. (A fixed number of avatars representing the capacity of a team member also helps teams to only volunteer for work for which they have capacity.)		* '''Avatar''' - sometimes it works well for team members to use avatars to indicate who is working on which item. (A fixed number of avatars representing the capacity of a team member also helps teams to only volunteer for work for which they have capacity.)
	* '''Blocker Indicator''' - this may be as simple as a small red sticky note that is highly visible to help teams understand which work items have been blocked and why		* '''Blocker Indicator''' - this may be as simple as a small red sticky note that is highly visible to help teams understand which work items have been blocked and why

Mmusij: /* Concurrent and Parallel Processes */

2018-12-18T05:02:08Z

Concurrent and Parallel Processes

← Older revision		Revision as of 05:02, 18 December 2018
Line 20:		Line 20:

	The stacked multiple column approach provides an explicit representation of what is happening in each part of the process and is good when an explicit understanding is needed in the team.		The stacked multiple column approach provides an explicit representation of what is happening in each part of the process and is good when an explicit understanding is needed in the team.

			===Swim Lanes===
			Swim lanes are great to represent partitions of the work such as when working on several features or on work that relates to different contexts.

			Simply draw some horizontal lanes on the Kanban board and then the board is explicitly partitioned for specific contexts.

			===Expedite Lane===
			Occasionally teams encounter work items that need to be worked on immediately such as production issues, for example. A simple way to represent this is to create an ''Expedite'' swim lane that clearly indicates to a team that anything that sits in this swim lane is of automatic high priority.

	==WIP Limits==		==WIP Limits==