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
With the latest update to SwiftKanban, we have made some exciting progress in supporting Enterprise Services Planning, Upstream or Discovery Kanban – and Portfolio Management with Kanban. At the same time, we have tackled one of the most needed, and fairly tricky, feature of customizing the information one can see on Kanban cards in the Kanban Board view. Upstream Kanban and Minimum WIP Limits. Enterprise Services Planning helps organizations focus on the need to look at various organizational functions (departments) as services that need to be delivered smoothly…
We often hear the question – In Kanban, what should we do if a User Story in Test column is found to have a bug that needs to be fixed? Let’s say the workflow is something like this: Todo -> Development -> Test -> Release. If a User Story has completed Development and moved to Test, and a tester finds a bug, what should we do to that User Story? Is it right to leave that User Story in Test and the developer should stop their current development work to fix this Defect first? If so, does this mean that developers must be interrupted all the time to clear the bugs found in Test?
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.
It’s been more than 10 years since the launch of the body of work that ultimately led to the Kanban Method for knowledge teams by David Anderson. During last month’s Lean Kanban India conference (the very first official Lean Kanban conference in India), which we were very proud to co-host and be a Title Sponsor of, David presented a journey down memory lane of 10 years of Kanban. During this period, Kanban, and the Kanban Method, have emerged, depending on who you talk to, as an “alternate path to Agility”, an alternative to Scrum, a way to improve your Scrum
I was in Bangalore for a few days, in part to attend the Agile India 2015 conference. The Sunday morning after the conference got done, I decided to go for a walk. Instead of the picturesque Cubbon Park close by, I decided to go exploring the city. In keeping with the Lean/ Kanban principles discussed at the conference, I decided to maximize flow – and turn in whichever direction the pedestrian crossings were open. That immediately put me on Kasturba Road. I thought fleetingly, “Of course, Kasturba Gandhi (Road) had to be next to her husband Mahatma Gandhi (MG) Road!”
As the year draws to a close, the overwhelming feeling at Digité is one of gratitude! It has been a momentous year for us here at Digité – and we have our employees, customers and partners to thank for that! During the year, we saw tremendous strides in our products SwiftKanban and SwiftALM – and a surge in their usage around the globe. This has been possible due to 3 key factors.
While starting with Kanban may appear simple enough – after all, what can be simpler than ‘start with what you have’?! – modeling your first Kanban board does require some thinking and planning as it depends on a number of factors. Learn how do you design your first Kanban board.
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! The same applies to software or product development processes. Most teams have a general idea of what their development process is or looks like. In fact a lot of them have the processes well-documented as well (altho’ not many people might be able to find that documentation! But that is a different post.)
Try SwiftKanban Enterprise Plan FREE for 30 days.