I settled into the visitor’s chair across the desk from Nate. Looking at Nate I said “So tell me about your project.” RULE II: START WHERE THE SYSTEM IS1 Nate smiled and wistfully said: “Well, I’m the project manager and ScrumMaster. John will be the Product Owner. He works in our North East office. He […]
Joe Little does a marvelous job recruiting speakers for the Agile-Carolinas meetings. This month was no exception. Israel Gat from BMC Software discussed “Leading the Disruption”. This presentation focused on releases 2.3 and 2.4 of their distributed system management software. Near the presentation’s end Brooks’ Law was mentioned and the question posed, “Does Brooks’ Law […]
Esther Derby recently ranted about Force Ranking. I’m not an expert on force ranking, or maybe as an independent consultant I am. I’m force ranked every time I work with a client.
Causal Loop Diagrams (CLDs) share several things with books: they both tell stories, they can be fact or fiction, and they’re both easier to read than write. Keep reading to learn how to write CLDs. The Buddy System The first step in creating CLDs: find a buddy, friend or coworker with whom to share the […]
Causal Loop Diagrams (CLDs) can help us understand complex interactions and events by revealing system structure. Unlike buildings, most systems don’t have visible structure. We notice systems by observing events. When the events form a pattern (usually over time), there’s indication that a system is working. We use CLDs to diagram the system and reveal […]
In Changing Quicker we looked at reducing or removing system delays to reduce the time delay between realizing a change needs to be made, and when the change’s effects occur. Another way to change quicker involves learning to change. Learning is a process that depends on experience and leads to long term changes in behavior potential.
Sharkey, the sales VP of UberDenke Software Products, firmly believes he needs to have the next release of the UDCRM product in three months. Engelbert, the software engineering VP, estimates a minimum of twice that long – six months – to implement all the new features. During the discussion, Sharkey drops some thinly veiled threats: