I started my agile journey twenty years ago. At the time, I was a Java programmer and a UML modeler, and I lucked into working in an XP team. Joining an experienced XP team was uncomfortable at first. The practices were very different from what I was used to. Kent...
The post explains a systems thinking approach for team learning, emphasizing mental models, curiosity over knowledge accumulation, and the importance of actionability. It introduces a technique involving a series of steps to foster collective understanding and address the blind spots inherent in any team environment. These steps guide a team to identify factors affecting their performance, analyze cause and effect relationships, identify dominant causes and effects, and ultimately make informed decisions to improve productivity and tackle challenging work. The method values facilitation, engagement, and the realization that learning is a continuous, shared process within a team’s system.
This is the last part in the series “Trapped in Wagile”. In the kick-off article I outlined three fundamental characteristics of waterfall organizations. In subsequent articles I explained Phase-Gates (part 2) and Large-batch handoffs (part 3). In this article:...
This is part three of the continuing series of articles. In the first article of this series, I outlined three fundamental characteristics of the waterfall system. In the previous article (part 2), I explained Phase gates and the unintended consequences when phase...
In previous article, I outlined three fundamental characteristics of waterfall system. Phase-gates are the most distinguishable characteristic of a waterfall organization. Recap on Phase Gates Phases are are strictly linear sequence of activities to build a product or...
Organizations attempting to transition to Agile demonstrate waterfall characteristics - residually or resurgently. Understanding these characteristics and learning to observe manifestation of these tendencies in organization systems will help you uncover impediments...