Scrum, SAFe, Kanban, Nexus, LeSS, XP… There are so many agile frameworks in existence, and each of them serves particular purposes. We trust highly in these frameworks for a multitude of reasons. Many individuals fall victim to the belief that simply using an agile framework makes us agile, but that unfortunately is not the case. This talk will look into the signs that a framework is not working, why it may not be working, and how to solve issues regarding frameworks utilizing Design Thinking. The immediate impulse can be to jump ship when having issues with a framework, but with some evaluation, objectivity and creativity new solutions can be found.

There is a stark difference between doing and being agile. Frameworks can assist us in being agile, but if we are not using them in an agile way then we are just going through the motions, pretending to work in a way in which we are not. We need to operate within our frameworks in an agile way, reacting to changes in our product, environment and expectations. Sometimes just following examples in the framework’s book is not enough, but in order to do that the source of the issue needs to be determined. Oftentimes, the framework is not the issue, it is how a part of the framework is being implemented.

Each framework comes with its own set of roles, artifacts, and rituals. Optimizing these and seeing how they best fit into our culture and environment is essential to properly utilize our framework, remain agile and ensure effectiveness. One way we can evaluate issues that arise within our framework and improve is by utilizing Design Thinking to ensure that people stay at the center of our solution and that we are considering multiple potential solutions.