How do you design your first Kanban board? This thought was triggered by a question posted by someone who works at an agency and were trying to figure out the best way to set up their Kanban board. The agency appears to be a small team working on multiple customer assignments and they wanted to use Kanban to track all of the work they do.
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.)
We’ve added some new features and made quite a few enhancements to SwiftKanban over the past few weeks. This post details some of the highlights.
New! Net Work-Time Report
Get a report of the ‘net’ work-time for each card while the card was in an ‘in-progress’ lane, and was neither blocked nor unassigned. This enables you to compare the actual work on a card to the initial estimation. Read More…
In the last few weeks, I read 4 very interesting articles that underscore the value of using Kanban for Project Management, and yet represent two extreme ends of how Kanban is gaining recognition in this field.
First, there was a series of 3 great blog posts by none other than our friend, philosopher and guide, and Kanban pioneer, David Anderson.
As Agile gets larger acceptance across the (Indian software) industry, the (manual) testing community has been concerned about how it will impact them. They hear about developers doing testing, test automation and hence wonder – what role am I going to be play? Is this going to kill my job? The concern is natural given a general perception that in Agile, developers should be doing testing. This concern has been part of the resistance that some of the organizations are facing in adopting Agile thinking.