DOING AGILE VS BEING AGILE
“Doing Agile” and “Being Agile” represent two distinct approaches to Agile methodology.
“Doing Agile” involves mechanically implementing Agile practices and processes, such as daily stand-ups, sprint planning, and using Agile tools. It’s focused on the formalities of Agile without necessarily embracing its core values.
On the other hand, “Being Agile” is about adopting an Agile mindset and embodying the principles of collaboration, flexibility, continuous improvement, and customer focus in every aspect of work.
The key differences between “doing agile” and “being agile” are rooted in mindset, practices, and cultural adoption:
1) Mindset vs. Practice:
Doing Agile: Focuses on the implementation of Agile practices and processes, such as holding daily stand-ups, following Scrum ceremonies, and using Agile tools. It’s about adhering to the mechanical aspects of Agile methodologies.
Being Agile: Involves adopting an Agile mindset and embodying Agile principles such as collaboration, flexibility, continuous improvement, and customer focus. It’s about embracing the underlying philosophy and values of Agile in everyday work.
2) Cultural Adoption:
Doing Agile: Teams may go through the motions of Agile practices without fully understanding or embracing the values behind them. This can lead to superficial adoption where processes are followed without achieving true agility.
Being Agile: The entire organization or team cultivates a culture that supports Agile values. This includes fostering trust, encouraging experimentation, embracing change, and prioritizing customer needs.
3) Focus on Outcomes vs. Outputs:
Doing Agile: Emphasizes completing specific Agile rituals and producing outputs, such as user stories, sprints, and burn-down charts. Success is often measured by adherence to the process.
Being Agile: Emphasizes delivering value and achieving desired outcomes. Success is measured by the ability to respond to change, deliver valuable products, and satisfy customer needs.
4) Flexibility and Adaptation:
Doing Agile: Teams might follow Agile practices rigidly, which can lead to inflexibility when processes need to adapt to new situations or challenges.
Being Agile: Teams are flexible and adaptive, using Agile practices as guidelines rather than strict rules. They are open to evolving their processes based on feedback and changing circumstances.
5) Collaboration and Communication:
Doing Agile: Collaboration may be enforced through prescribed Agile ceremonies and tools, but it might not translate into genuine, effective teamwork.
Being Agile: Collaboration and communication are ingrained in the team’s way of working. There is a strong emphasis on face-to-face interactions, collective ownership, and team empowerment.
In essence, “doing agile” focuses on the mechanics and processes of Agile, while “being agile” is about adopting the Agile mindset and values, leading to a more profound and effective implementation of Agile principles.
