Kanban has become the hot topic of discussion amongst the IT community since 2010, due to its accelerated rate of adoption and remarkable impact on organizations — from the few-employee company to the tens-of-thousands-employee company — where it has been adopted despite its young age. This fast pace is both good and bad, Kanban is benefiting organizations when adopted properly, but there is a risk of doing it wrong by rushing an adoption without fully understanding it. For example, people frequently ask if Kanban is a methodology for software development, or for software maintenance, or for project management, or a systematic approach to cultural change in the organization, or something else. Another frequent question is Read more
Posts Tagged 'kanban'
2010 saw the rapid growth of quantitatively-driven performance improvement among organizations serious about getting lean and seeing results. Much of this can be attributed to newer techniques in agile practices such as Kanban for software, and related awareness resulting from these practices. Organizations getting serious about real, measurable improvement take being a learning organization to heart. They have started to explore blended approaches where they may bring together more than one “named” approach, firmly internalize the salient themes from them and synthesize a custom method that meets their specific business needs. Some of these organizations have also started to investigate and pursue use of CMMI as a framework for organizing and benchmarking their performance accomplishments. In Read more
I have four predictions that I’d like to share with you: The decline of Scrum will become obvious in 2011. The shine started to come off Scrum in 2009 when teams started to publicly report that they had run into trouble applying it effectively and this snowballed in 2010. The squabbling between the Scrum thought leaders over their various certification schemes exacerbated the problem in 2010 and there seems to be no end in sight. My recent 2010 Scrum Certification survey found that only 27% of Certified Scrum Masters (CSMs) were willing to admit publicly that they were CSMs and another 37% would do so seldomly, an indication of the Agile community’s growing embarrassment surrounding “Scrum Read more
The next two years will show a major change in the Agile world: The predominant position of Scrum will suffer from both the inside and the outside. On the inside, the struggles within the community will weaken the thrust effect of the certification program. Right now, we already have two competing certification programs, and, at least in Europe, single trainers are trying to establish their private programs, too. This will lead to several dialects and maybe even more competing certification programs. Though competition generally helps progress a profession, I consider this a sign of increasing weakness for the Scrum Alliance. The ongoing merger between Scrum and XP – now marketed as “Scrum development practices” – Read more
The March issue of Cutter IT Journal invites useful and thoughtful debate and analysis on the opportunities and challenges presented by implementing Kanban methodologies in the enterprise. We invite experts, IT professionals, consultants, customers, and all other Kanban practitioners to share their perspectives — either positive or negative — with Kanban implementation. We also encourage authors to go beyond Kanban as a methodology and address other related factors such as communication, collaboration, environment, end-user issues, and how Kanban has been used in conjunction with other methods to reach project success. Proposals of interest are due 20 December. To respond, please visit http://www.cutter.com/content-and-analysis/journals-and-reports/cutter-it-journal/callforpapers03.html
I recently worked on Kanban adoption with a new customer, who informed me that Kanban was already underway and wanted me to help finish the adoption. On the first day, I was taken to the Kanban boards, two of them, and was introduced to the 15-person team. I noticed right away that the Kanban boards lacked a good number of essential elements to be considered an actual Kanban board, such as explicit policies and well-defined classes of service. Furthermore, the boards were not for separate projects. One was for the development phase; the other for the test phase. Also, the adoption work was delayed by a month because a key person (the champion) wasn’t available Read more
Under pressure from the continuing economic crisis, enterprises are struggling to maintain their level of competitiveness, or even remain in the market. What has been considered key to success will begin to shift, from the search for effective methodologies to the realization that innovation and value are the most important differentiators for success. For many years, enterprises have considered effective management of scope, schedule, and budget as the key to success. This has been proven over and over to be incorrect. (Just ask the professionals you know. How many projects have they been involved with where scope, schedule, and budget were really effectively managed?) Furthermore, there are projects that accomplish this goal and still do Read more