Agile Ways of Working
A Path to Transformation Beyond Technology
In recent years, I have had the opportunity to help several non-tech teams adapt to Agile ways of working. This journey often begins with a shift in the mindset rather than the adoption of a specific framework like Scrum, Kanban, or any other framework to name it. My focus has always been on understanding the underlying principles of Agile, rather than simply following a prescribed methodology. This approach is important because it highlights the difference between “being Agile” and “doing Agile.”
“Doing Agile” refers to the act of following Agile practices and using Agile tools without a deep understanding of the underlying principles. It’s about checking the boxes — holding daily, using JIRA, breaking work into sprints — without fully grasping why these practices exist or how they contribute to a team’s success. This surface-level approach can lead to frustration, as teams find themselves weighed down by what feels like additional administrative overhead. Without understanding the “why” behind Agile practices, these teams might struggle to see the real value, leading to scepticism and resistance to change.
In contrast, “being Agile” is about Agile mindset and adapting practices to fit the unique needs of the team. It’s about embracing the principles that drive Agile — such as…
