Menu
Tomek's blog
  • Contact & About
Tomek's blog
Photo by sydney Rae on Unsplash

Card Colors on Kanban Board

Posted on January 10, 2016November 3, 2022 by Tomek Kaczanowski

There are many ways to organize your kanban (or scrum) boards. One difference is the meaning of colors of cards. Here are some examples of how we can use colors so that the board tells us as much as possible about the current work.

Size of task

One team I worked with used the following color code:

L – large task
M – medium task
S – small task
bug

As you can see, for features colors of cards answer the question “when it will be done” (well, at least they give some hint about completion time…) which is quite important for PO. The red color is special – it says something is a bug without specifying how long will it take to fix it.

This worked pretty well. For large tasks, we usually put them on the board but we also put their subtasks so that we could observe the progress.

Type of task

technical task
maintenance task
new feature
bug

A different approach. This time the colors say nothing about the (expected) completion time, but allow to understand what type of tasks is prevalent: is the team mostly fixing bugs or maybe we are working on our architecture to prepare it for the expected increased number of requests?

Green and red are obvious but let me say a few words about technical and maintenance. It is not obvious which tasks should go where, but the criteria we use is the purpose of the task. Usually, non-feature things requested by customer support ended up as maintenance and things like redesign were treated as technical. To be honest there was some confusion about these two types (especially when we begun) but now it is not a problem anymore.

Share this:

  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on Pocket (Opens in new window) Pocket
  • Click to email a link to a friend (Opens in new window) Email
  • Click to print (Opens in new window) Print

Like this:

Like Loading...

Related Posts

  • agile
  • kanban
  • scrum
  • team
  • tips & tricks
  • Leave a ReplyCancel reply

    Follow me on Twitter

    My Tweets

    Subscribe to Blog

    My Books

    Practical Unit Testing - JUnit Practical Unit Testing - TestNG Bad Tests, Good Tests kanban for your team 1,2,3 kanban Złe testy, dobre testy

    Tags

    4dx agile book review capacity planning conference constraints continuous improvement daily scrum decision taking discussion effectiveness review estimation experiment facilitation feedback funny getting things done goals interview kanban leadership management management 3.0 meetings notes organisational culture procrastination productivity psychological safety rant remote work retrospective scrum scrum sprint sociocracy sociocracy 3.0 team testing tips & tricks tools transparency visualization wip work in process work in progress

    There is no Planet B. Act Now!

    There is no Planet B. Act Now!
    There is no Planet B. Act Now!

    Follow me on LinkedIn

    Tomasz Kaczanowski

    Top Posts & Pages

    • ACE! Conference 2015
      ACE! Conference 2015
    • Sociocracy 3.0 Effectiveness Review
      Sociocracy 3.0 Effectiveness Review
    • Interview Tool: Moving Motivators
      Interview Tool: Moving Motivators
    • 4DX: LAG vs. LEAD
      4DX: LAG vs. LEAD

    Categories

    • agile (32)
    • book (7)
    • event (2)
    • facilitation (2)
    • organization (11)
    • productivity (32)
    • sociocracy (10)
    • team (5)
    • testing (2)
    • tools (16)
    • Uncategorized (9)
    • varia (30)
      • remote work (2)
      • ux (2)

    No Business On A Dead Planet

    No Business On Dead Planet
    No Business On Dead Planet
    ©2025 Tomek's blog | WordPress Theme by Superb Themes
    %d