Why We Need Adaptive Frameworks

Most frameworks are adopted in one way.  Scrum has immutable roles, rules, events and artifacts so any start will attempt to have those. While you may vary things inside of it, this makes it somewhat of a static framework. SAFe’s implementation roadmap is the same regardless of the organization using it, taking a bottom level up approach since that is supposedly simpler. Neither take a look at where the organization is with the exception of some minor adjustments within the framework.

Taking this approach has the following disadvantages I’ve mentioned before:

  • there is a tendency to focus too much on the framework at initial training – leaving less time on what the organization really needs to learn.
  • when challenges arise people tend to look at the framework for answers, when a basic understanding of Flow and Lean would suffice
  • the framework often doesn’t fit the organization adopting it well for any number of reasons and often does not fit the company’s culture

The result is that they only fit a certain number of organizations and those are typically the ones where teams are easy to form. A framework that adapts to the organization adopting it is critical. This increases adoption speed and value achieved while avoiding resistance.

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.