Case Study: from Component Teams to Team Topologies to FaST Agile
This article is a detailed analysis of James Shore's talk at the Hands-on Agile Meetup. We're looking at this case study from the viewpoint
top of page
Gain Radical Clarity with
Mapping Frameworks
Stop Framework Thinking
Framework thinking is the belief that we need to implement an industry-standard framework to develop digital products at a large scale.
People incorrectly assume that the implementation of a standard framework will magically solve the root causes of malfunctioning product development organizations. Also, framework implementations tend to focus on "placing the ticks in the boxes" without creating a deeper understanding of the underlying principles, leading to cargo-cult adoptions and low effectiveness. While frameworks try to be a one-size-fits-all solution, every framework implementation needs to be contextualized. This is why comparing different implementations of the same framework is difficult to do. Frameworks are chosen and implemented without a clear organizational vision and understanding of their impact.
We at Org Topologies™ want to end "framework thinking", by providing radical clarity with:
-
a simple and unambiguous visualization technique
-
a generic organizational design language
-
a clear vector toward high adaptivity
Articles on Framework Mapping
bottom of page