An ignored piece of the ecosystem

A key tenet of Lean-thinking is that we must adopt systems thinking and acknowledge that most of the errors we encounter are due to the system. For example, consider how the geographic arrangement of dev and testers affect their work.

How to create good ecosystems is critical. How the ecosystem provides guidance to the people doing the work is often ignored. In the software world, seeing the work being done is difficult. Creating visibility of the workflow itself is critical.

What are the right transition steps to go from say an epic to a feature? How do we get consistency in this and other actions across an organization without requiring a one-size-fits all approach? A tool can readily accomplish this if it is designed to reflect the process being used and that this process is a reflection of what people consider to be the best way of working.

This requires a mindset shift combined with flexibility of the tool. The challenge is not in the tool’s flexibility but in the people using the tool understanding lean workflow & setting the tool properly.

A criteria for such a tool is that their first recommended step is to understand the value stream of the organization using the tool. This is the correct focus.

Leave a Reply

Your email address will not be published. Required fields are marked *