Index![]()
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
Kanban is a methodology that constrains the amount of work that can be assigned to a particular workflow state at any one time. This helps teams to optimise their lead time (or cycle time) — that is, the average time taken to complete a task.
This tutorial will walk you through the process of setting up your Kanban environment, and continuously monitoring it so as to make your cycle time as short — and predictable — as possible.
On this page:
Visualising your existing process and workflow is essential to understanding what the team is currently working on.
Specifying columns constraints allows a team to limit the amount of work-in-progress, as WIP directly affects your cycle time (see Screenshot 2). The team will be notified when a constraint has been busted, and can then take corrective action.
On a daily basis,
At regular intervals,
By visualising a team's workflow and limiting work-in-progress you reduce waste, facilitate a better flow of work across the board, and deliver value to customers faster.
Screenshot 1: a board displayed on a Wallboard
Screenshot 2: CFD showing how WIP affects your cycle time
Screenshot 3: Transitioning an issue
Screenshot 4: Control Chart showing the mean and actual time taken to complete issues
12 Comments
Anonymous
Oct 13, 2011In measuring cycle time, is there a way to do a 90 day cumulative average instead of averaging everything?
Ram Ramalingam
Oct 24, 2011Cycle time on # of stories seems like a misleading generalization - a 1 point story will surely have a different cycle time as 8 pointer. And what the chart above seems to give is an average across all the story sizes. And just dividing that by the average story size across doesn't work since the relationship between story size and time are not necessarily (not usually) linear
Anonymous
Jun 22, 2012My understanding is that if you are using Kanban you would not be using story points.
Anonymous
Feb 08, 2012Kanban story cards doesn't contain Kanban marker, that the story is ready to go to the next stage.
Anonymous
Mar 20, 2012I have asked Atlassian to implement this feature in https://jira.atlassian.com/browse/GHS-2526
Martin Waller
Mar 13, 2012Is it possible to add the facility to manually change the order of tasks within the TODO column in order to prioritise them at a finer level than the issue priority field?
Anonymous
Apr 10, 2012Hi there,
I cannot seem to get the info I need here. So please help me. If I have a Project with issues and sub-tasks. Some sub-tasks will also have smaller tasks. Can you tell me how I can log this smaller tasks?
Thanks
Anonymous
Sept 06, 2012Sub-tasks cannot have sub-tasks of their own. However, if you need to break up a sub-task into smaller sub-tasks, you could achieve this by first converting the sub-task to a standard issue. You would then be able to create sub-tasks for it.
See rsCreating a Sub-Task
user-86a2e
Aug 30, 2012hi, I'm using a KANBAN board. Is it possible to configure what fields show on a card? i liked the old version (ha) where you had different 'views' for small cards, and large cards. These one's are quite large but have only few data fields on them.
Rosie Jameson [Atlassian]
Sept 04, 2012We are planning to work on this in the near future – please watch GHS-3474 - Getting issue details... STATUS . Thank you for your input.
Anonymous
Nov 12, 2012Hi.
How did you get those yellow arrows with the exact WIP and cycle time measurements? On my several months old CFD with around 1600 done items, all I can see is that WIP is somewhere between 80 and 120.
Is there also a way to determine, not necessarily graphically, what the actual WIP was at a certain time, or the average WIP (across arbitrary columns) between two times?
Neil Sproul
Nov 30, 2012We use an Elaboration lane before something goes In Progress, we use this to measure time spent understanding a problem. Is there a way on the control chart to have the way the mean/max/min are calculated to only be based on the time period you selected. It seems regardless of the time period selected for one or many lanes JIRA is just taking the sum of time spent in a lane. Not the sum in context of the time people selected.