What if negative organizational consequences of scale eg silos, frustrating bureaucracy, etc. are actually a consequence of attempting to scale the size of an organization without also scaling the amount of tolerable variety (in practices, processes, etc.)? What if we should be doing more than just tolerating variety? What if increased space for (and decreased cost of) variety is a reason to scale, not a curious byproduct? This session provides an approach for incurring variety where it makes sense within the coherence of a longer-term vision.
Target Audience: Architects, Scrum Masters, Agile Coaches, Tech Leads, Managers
Prerequisites: Basic knowledge of Agile and DevOps