![causal loop diagram stella architect causal loop diagram stella architect](https://ssl.iseesystems.com/images/connector/2016-fall/marcus-1.png)
Accordingly, in large-scale agile adoption it is useful to be able to get together with colleagues and effectively reason about the mental models, causal relations, feedback loops, and control mechanisms (or illusions of control) in a big system that is about to be seriously perturbed. It bumps into product management, budgeting, beta-testing, launch, and governance and HR policies. Another is that large-scale adoption of Scrum, lean thinking, and agile principles is not isolated to the development group. Problems stemming from mental models and assumptions are one issue. These reflect the impact of our mental models on the system, a subject that will be revisited later in this section.
CAUSAL LOOP DIAGRAM STELLA ARCHITECT SOFTWARE
Weinberg-Brooks’ Law: More software projects have gone awry from management’s taking action based on incorrect system models than for all other causes combined.Ĭausation Fallacy: Every effect has a cause… and we can tell which is which. Gerry Weinberg highlights two decisive factors in this situation:
![causal loop diagram stella architect causal loop diagram stella architect](https://www.iseesystems.com/resources/help/v2/Content/Resources/images/LtmOverview03.png)
In small groups the forces at play are more quickly seen and informally understood, but in large product development-or any large system-it’s tough. What’s going on? Systems thinking may help. “No matter what we do, the number of defects in our backlog remains about the same,” a manager told us this for a 15 MSLOC C and C++ product with several hundred developers where we were working. I took a speed reading course and read “War and Peace” in twenty minutes.