Scrum, Kanban, and all the other Agile frameworks are based on the empirical process. Successful empirical processes define a hypothesis, run experiments, and validate the hypothesis based on real data. In Agile, we then use these real data and observations to adjust or Inspect and Adapt our processes to optimize the system. Many Agile teams have refined the retrospective to quickly adjust the team’s process to optimize the work completed. However, many teams fail to think of the larger picture. They fail to realistically account for the impact the change will have on other teams, processes with Agile at Scale.
System Thinking is about thinking in the larger context, thinking “whole”. By implementing System Thinking, an advanced Agile team can begin to predict the positive or negative impact that local changes will have on the large-scale organization. System Thinking is understanding the simple rules of how thinking works and applying those rules to solve complex problems.
A few things that most teams fail to observe about System Thinking:
- Most Agile projects are complex projects. Meaning, they fail to recognize that one small part of the project cannot be separated from the project or the system as a whole.
- Improving the performance of one project or sub-project will not necessarily improve the performance of the whole system. In fact, it is likely to worsen the overall performance.
- High performing Agile teams are adept at creating transparency within the team, but using a Systems Thinking approach can more effectively create transparency in terms of how the Agile team interacts with the system. In this way, it becomes easier to highlight where these interactions are ineffective or damaging, and how these poor interactions manifest themselves as anti-patterns.
Agile teams should seek to classify problems and solutions along the following lines:
- An analysis of the system conditions and depiction of those which affect the Agile team and its work.
- Does the problem emanate from the team or from the wider system?
- What internal experiments can the team conduct where the ongoing effects may be felt outside the team and within the wider system?
- Can/Do we address the systemic cause, rather than the symptom felt by the team?
- Which problems that we are now surfacing started as solutions?
- Will this solution be felt elsewhere within the team?
- What /where are the feedback loops between the Agile team and the wider system and can they be improved?
At Web Age, we have added System Thinking to many of our Advanced Course including: