Documentation for GreenHopper 6.2.x. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.
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