A lot of people in the Agile community talk about ‘simplest’ as it’s a good thing.  I like simple better than complicated if all other things are equal, but all too often simple is simplistic, not a desirable thing. What makes for a ‘simpler’ framework or method? Some people suggest it is the size of the guide or number of things you must do. I would suggest it is better to think of it as, what is more understandable to people.

FLEX (FLow for Enterprise Transformation) is designed with understandability in mind. At its core, here is what FLEX focuses on.

1. How do people collaborate with each other
2. What do they agree to as to what they are to achieve

How to collaborate: The Guardrail System

We have developed the Guardrail System to guide transformations in the simplest approach that is effective. It is based on principles and basic agreements.

We agree to:

• Work on items that will have us realize the greatest amount of Business value across the enterprise
• Collaborate with each other in order to maximize the realization of Business value across the enterprise
• Ensure that all work will be made visible
• Take the necessary steps to sustain or increase predictability
• Keep the work throughout the value stream within our capacity
• Encourage everyone to strive for continuous improvement

Each of these will lead to other steps but these function as a start.

Agreeing to work on greatest amount of business value will lead to the use of Minimum Business Increments and even further (what are the items we want to invest in, what are our strategic initiatives for that, how do we get MBIs from them).

Agreeing to collaborate leads to consistent cadences and visions in order to implement business value.  It also requires the next agreement to make all work visible.

We of course want to be able to improve our predictability which is partially achieved by keeping work within our capacity.

And continuous improvement has us not only do ‘inspect and adapt’ but incorporate double-loop learning into the mix.

What to work on

The desired focus is on quick realization of business/customer value predictably, sustainably, and with high quality. If starting with people who can work on this directly, this is likely the place to start.  Teach people to use Minimum Business Increments (MBIs). Use collaboration to define features (first phase of Acceptance Test-Driven Development).

If starting with technology, then probably best to start with lowering the value stream impedance from as early in the value stream as you can. Still teach the concept of MBIs as technology can work with that. And, of course, use ATDD as well.