Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

Kanban は、どの時点においても、特定のワークフローの状態に割り当て可能な作業量を抑制する手法です。これにより、チームは納期 (または サイクルタイム) 、つまり作業完了にかかる平均時間を最適化するのに役立ちます。

  • 多くの Agile 開発チームは、Kanban が特に、受信タスクがトリアージされ、優先度に従って対応されるようなバグ修正やメンテナンスリリースに適していると考えています。完了済みタスクの数が十分溜まって大きな値になると、マイナーバージョンが作成およびリリースされます。
  • 開発チーム、または Agile 配信チームは、Kanban を頻繁に使用します。これらのチームは顧客への価値の提供を含めた、実行の定義を設定します。

本チュートリアルは Kanban 環境の設定プロセスを順を追って説明し、サイクルタイムをできるだけ短期間かつ予測可能にするよう、継続的に監視します。

On this page:

1) ワークフローの可視化

チームが現在何に取り組んでいるかを理解するには、既存のプロセスとワークフローを可視化することが必要不可欠です。

  1. プロジェクトを示すボードを作成 (または選択) する必要があります。ボードの作成を参照してください。
  2. If you are using a customised workflow, you will need to set up suitable columns to map to your workflow statuses. See Tutorial - Adding a Column to a Board.
  3. 現在の作業をJIRA ウォールボードに表示し、チームの活動に透明性を持たせます (スクリーンショット 1) を参照。

2) 進行中の作業の制限

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.

  1. Go to your board and select Tools > Configure.
  2. Click the 'Columns' tab, then for the relevant column click either the 'Min' box (yellow) or the 'Max' box (red). Type the new value and press the 'Enter' key. (For more details, see Configuring Columns.)
    (tick) As a starting point, you may want to set a 'Max' value of 6 for the 'In Progress' column.

3) 課題での作業

毎日行う操作

  1. Go to 'Work' mode on your preferred board (see Using Work Mode).
  2. Choose the highest ranked issue in the 'To Do' column (or 'Backlog', depending on the name you have given it) and drag them to the 'In Progress' column. (See Transitioning an Issue.)
  3. As you complete each issue in the 'In Progress' column, drag it to the 'Done' column. (See Screenshot 3.)

4) サイクルタイムの測定

定期的に行う操作

  1. 優先ボードへ移動します。
  2. Select 'Report' > 'Control Chart' (see Viewing the Control Chart). This will show you the average length of time that it took to complete each issue — that is, your cycle time. See Screenshot 4.
    (tick) If you want to see the average length of time that issues spent in a particular status, filter the issues to show only specific columns by using the 'Refine' option in the top right of the report.

チームのワークフローを視覚化し、進行中の作業を制限することで、ボード全体で無駄を減らし、作業の流れを改善して、より早く顧客へ価値を提供することができます。

スクリーンショット 1：ウォールボードに表示されているボード



スクリーンショット 2：WIP がサイクルタイムにどのような影響を与えるかを示す CFD

Kanban CFD


スクリーンショット 3：課題のトランジション

Kanban プロセス

 

スクリーンショット 4：課題を完了するための手段と実際の時間を示す管理図


 

 

 

12 Comments

  1. Anonymous

    Oct 13, 2011

    In measuring cycle time, is there a way to do a 90 day cumulative average instead of averaging everything?

  2. Ram Ramalingam

    Oct 24, 2011

    Cycle 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

    1. Anonymous

      Jun 22, 2012

      My understanding is that if you are using Kanban you would not be using story points.

  3. Anonymous

    Feb 08, 2012

    Kanban story cards doesn't contain Kanban marker, that the story is ready to go to the next stage.

    1. Anonymous

      Mar 20, 2012

      I have asked Atlassian to implement this feature in https://jira.atlassian.com/browse/GHS-2526

  4. Martin Waller

    Mar 13, 2012

    Is 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?

  5. Anonymous

    Apr 10, 2012

    Hi 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

    1. Anonymous

      Sept 06, 2012

      Sub-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

  6. user-86a2e

    Aug 30, 2012

    hi, 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.

    1. Rosie Jameson [Atlassian]

      Sept 04, 2012

      We are planning to work on this in the near future – please watch GHS-3474 - Getting issue details... STATUS . Thank you for your input.

  7. Anonymous

    Nov 12, 2012

    Hi.

    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?

  8. Neil Sproul

    Nov 30, 2012

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



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.