The practicality of Agile is embedded within the world of complexity (from a Cynefin standpoint). As such, we have to assume that everything is subject to change; what worked for us today might not be the case tomorrow. As such it's incredibly important to understand the relationship between cause and effect with everything we do so that we can understand what continuous improvement looks like within our complex environments. Some examples include:

  • "If we reduce the number of user stories in our epics, does that also reduce the cycle time of said epic?"
  • "What is the biggest influencer of customer lead time? Is it the time spent in the backlog?"
  • "What are the biggest bottlenecks in our delivery? Is there a particular stage (e.g. releasing) that causes the most delay?

When we understand the tradeoffs of our delivery and product approach we can start to tailor our frameworks, mindsets and even culture around something that doesn't fit an off-the-shelf implementation strategy (e.g. SAFe), but rather build something that is fit for our own purpose and works for us.

If you'd like to know how this visualisation could be implemented in your organisation, feel free to contact me!