October 17, 2016

Kanban and the Importance of Work In Progress (WIP) Limits

Attending Kanban Training 
October 12, 2016

How Granular should my (Personal) Kanban Board be?

This question comes up not only in Personal Kanban but also for teams and enterprise (portfolio) kanban boards as well. It is a great question – and quite often tricky to answer!
August 21, 2016

Handling ticket Issues With Kanban

David J Anderson's book on Kanban shows us that a way to handle ticket issues is by attaching a color tag to a ticket to make it visible. An issue is a ticket-related event that becomes an impediment to its value flow, such as a defect, insufficient definition, unresolved dependency, etc. What I encounter often is, people have a natural tendency to move the ticket to where the dependency lies.
January 31, 2016

Kanban – The Product Manager/ Owner’s BFF!

Of all the roles in a software or product development organization, I will argue the Product Manager’s (or Owner’s) job is the most challenging. On the one hand, the task of figuring out just what to build is complex and multifaceted. On the other hand, in any reasonably mature product organization, there is so much work that is going on and so much new demand, that the Product Manager can wish all they want in terms of product innovation and focus on the product roadmap, but failure and customer demand pretty much hijacks most of the Dev capacity in the organization.
September 7, 2014

Does your Kanban Board Reflect the Process you Actually Have?

I’m sure most of us have seen the famous cartoon strip about requirements management – which highlights what the customer asked for vs. what they really wanted!
February 10, 2014

SwiftKanban 3.5.2

Hello again! We've improved our card search capabilities with this update and you now have the ability to track throughput for every Smart Lane!
October 25, 2013

Visual Requirements Management with Kanban

There is a lot of attention given to Lean/ Agile product development teams around the work done and the (Lean/ Agile) processes adopted in by the Dev team once a set of features (backlog items) have been identified for a set of sprints (scrums) and/ or Releases.