Collaboration is a catchall buzzword that many leaders are adopting these days. They seem to understand that it is difficult for groups of people who are located all across the globe to work together as a highly effective team. Talking about the need to work collaboratively is great… but until the way work gets done changes, collaboration will remain a buzzword.
This post puts forth kanban as a way to facilitate collaboration. I am a huge advocate of kanban, having seen it first hand. I’m anxious to hear your take on this article. Sign in and comment!
There is a general trend and desire to make work more collaborative. Yet when I ask teams to draw a diagram of how they work, they often come up with something like this (I’m simplifying it):
In this view, the workers form an assembly line. But their work doesn’t really flow like an assembly line. For example, a Software Developer may find a logical inconsistency in a feature specification and send the work back to a Business Analyst. A Quality Assurance specialist may do the same when testing the implemented software. The BA will update the spec and send the work back to QA. QA may find a bug in it and send the work back to the Developer. The Deployment Specialist may find something in the code to be an impediment to deployment. The Developer then makes the necessary change. The code now needs retesting, so it goes back…
View original post 751 more words