Essential Checklist for Scaling Kanban Across Teams: A Guide From Your Friends at LeanKitObtenir le livre numérique • Essential Checklist for Scaling Kanban Across Teams
Planview LeanKit: Optimize your business flow to deliver more value
Watch the demo to see how LeanKit can help you see the big picture, drive agility, integrate applications, and improve continuously.Regarder la démo du produit • Planview LeanKit
Learn what factors to consider when choosing a Kanban tool and determine whether practicing Kanban with LeanKit or Trello is right for you.
Visualization is the bread and butter of Kanban. The ability to convey information visually through the face of a card is an important feature for any Kanban tool. Research shows that images convey information significantly more efficiently than words – and customized visualization on your board might help you keep your thoughts, as well as your work, organized.
In LeanKit, you can convey information about a card through the card’s color, visual icons, due date icons, and the text displayed on the card face. The board background color and general structure stay consistent across all boards, which can help reduce confusion between boards in larger organizations using a hierarchy of boards.
Trello allows for a more customized card face; you can display images on a card face to convey information. You can also customize the background of your board. This is a great way for teams to make their board personal, branded, and fun, which might result in a productivity boost when practicing Kanban with Trello.
Organization of Project Tasks
When practicing Kanban, the goal is always to break work down into manageable tasks, to avoid scope creep, limit communication breakdowns, and keep work moving. In LeanKit, you can create a task board for each card, if it has small, distinct tasks within it.
LeanKit also allows you to connect all the tasks in a project across multiple boards, so you can track progress and quickly identify issues. This is critical for larger organizations that require project portfolio visibility, and can be helpful for any organization with cross-functional teams.
Trello does not have a card hierarchy capability. Teams committed to practicing Kanban with Trello can make it work, as long as the team is not distributed across too many boards (or the task breakdown is not too complex). If board hierarchy is important to you, LeanKit is a better option.
Organization of Project Information / History
A major benefit to Kanban is that it allows you to keep all information related to a piece of work in the same place, instead of distributed across various emails, spreadsheets, notes, and documents. This level of organization makes it easier to keep everyone on the same page; if they need to understand the context of a piece of work, then can look into the card’s history to get up to speed.
While both LeanKit and Trello have room for attachments, notes, links, and other project documentation, Trello also lets you use images to share information, which is helpful for people in creative / visual fields or who are using the board to organize information (not represent a workflow).
If your goal with Kanban is to improve productivity, project analytics are pretty important. You can generate your own analytics with Trello (or LeanKit) by manually counting how many cards your team completes in a given time period. That’s a great exercise in learning Kanban, but you’re more likely to stick with it if your tool has analytic capabilities built in.
LeanKit’s analytics can give you valuable information about the productivity and efficiency of individuals, teams, and your organization as a whole.
While there are integrations with Trello that can provide productivity analytics, they might not be as accessible to your team members as built-in, self-service board analytics.
If you analyze the flow of work through most team’s processes, they don’t move smoothly from one step to the next. Most teams actually have several concurrent value streams that have unique steps associated with them. For example, within one marketing team, some team members might mostly work on campaigns, which involve consistent work over time, while others might create deliverables, which go through distinct steps from beginning to end.
Teams get the most value out of their Kanban boards when they reflect the team’s actual process. In LeanKit, you can create horizontal swimlanes to represent different parts of your process. Horizontal swimlanes allow you to represent multiple related value streams on one board, so work can flow through the actual process it follows. Trello only allows for vertical lanes.
Which Tool is Right for You?
When choosing a Kanban tool, it’s important to consider your goals for practicing Kanban. If you’re a team or small organization of teams looking to increase visibility and communicate more effectively, Trello could be a great fit for you.
If you need a tool to support a larger organization, or would like to rely heavily on data to drive your Lean / Kanban initiative, LeanKit might be a better option. And if your organization can’t seem to decide which to use, there is an easy way to integrate the tools, so everyone can use the tool of their choice.