Due to the uncertainty of our times, I’m going to make two predictions. First, the world will come to an end on December 21st, exactly as the Mayans DID NOT predict hundreds of years ago. Granted, the Mayan calendar runs out on the 21st but to be quite frank my calendar runs out every year on December 31st and the world has still gone on despite of that dire prediction. The Mayan calendar myth dates back to the mid-1970s, a time when we were seeing Sasquatches in every forest, aliens eviscerating cows in every farm field, and chariots of the gods in the skies of South America. At that time we were also doing prodigious Read more
Posts Tagged 'lean'
Last year I predicted that enterprises would take an increasingly holistic systems view. I said “they will take an increasingly strategic view of improvement, coordinating change across divisions and functions to achieve a higher overall level of performance. This trend is reversing [of] short-term, every-division-for-itself fractionalization…[so that] the Enterprise, at the end of 2012, will look more like an effective, coordinated whole and less like a collection of disparate…parts.” This happened as predicted. One of the best indicators of it is the rapid acceleration since that time of “reverse offshoring” or “inshoring.” Reverse offshoring is the return of business from lower labor-cost nations where it had been transferred in previous years. Offshoring is a useful Read more
Since we announced the forthcoming “Big Agile” webinar (click here for details), I have been exposed to numerous questions and comments about “Big” vis-a-vis “Lean” in the Agile context. The intensity of some of these discourses was so high that I decided to comment on the subject in advance of the webinar. A lively debate during the webinar is, of course, goodness. In contrast, starting the webinar with a potentially gross misunderstanding as to where we are coming from and where we are heading is not too desirable. In general, “big”, to me, can be “lean”. As a matter of fact, big should be lean as otherwise scale will quite possibly pose a problem. Specifically, Read more
In 2011, and with increasing speed in 2012, Enterprises are embracing the whole-system view of themselves. This means they will take an increasingly strategic view of improvement, coordinating change across divisions and functions to achieve a higher overall level of performance. This trend is reversing the short-term, every-division-for-itself fractionalization that many organizations adopted during the financial pressure years 2008 – 2010. In the coming year we will see more of the team mindset (with some “taking one for the team” while others seemingly gain) than the “spread the pain” approach. The most successful organizations will compensate those groups which bear the greater pain so the whole can prosper. The systems-wholistic trend will continue even if Read more
I see the demand for actual performance results over declarative symbolic victories (e.g., certifications) taking a significant bend upwards. I’ve already begun to see the more forward-thinking companies maturing in their thinking about how they use “named” business, technology, and management concepts, e.g., Scrum, Lean, Kanban, CMMI, ISO 9000, ITIL, COBIT, Devops, etc. There’s growing skepticism in the efficacy of popularized approaches. Executives are less likely to rush into using new ideas just because they’ve heard “the name”. Whether they’re skeptical for the right reasons or not, their cautious approach offers a better have a chance of implementing these “named” initiatives effectively, keeping them off their list of failures – a list that contributes to Read more
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
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