9 Things Frameworks Should Do But Most Don’t

  1. Take a scientific approach and make the hypothesis that they are the best way to do what they are attempting to do. This encourages frameworks to evolve and improve and avoids dogma
  2. Provide a way to make reasonably accurate predictions whether a change will be beneficial.
  3. Be architected so they can accommodate the next three points
  4. Create a well-defined, customized starting point since no one size fits all.

  1. Provide options to avoid adopters having to reinvent the wheel without adding complexity.
  2. Be able to add new concepts to an approach without adding complexity. Frameworks based on simplicity cannot grow if they can’t do this. Other frameworks will get more complicated as they grow if they don’t do this.
  3. Have a simple model for Agile product management that works at all levels. This both states the smallest value that can be realized as well as all the items needed to realize it. Note, this is different from an MVP.
  4. Take a systems-thinking approach that includes how people will both react and misunderstand the framework.
  5. Effective, economical, distributed training. Knowing what to do is not sufficient; we must be able to convey what this is to other people.

And yes, FLEX does all of these.

Leave a Reply

Your email address will not be published.

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