When talking with various individuals, leadership specifically, I’ve come to the conclusion that they really have no idea what Agile truly means. They will mumble about Scrum and mention how it will never work for them because of [insert reason here]. However, when you really start asking the powerful questions, the real problem is that Agile is not understood.
All too often, Scrum is used synonymously with Agile. That is incorrect thinking, as you start to stray away from what Agile truly represents. Scrum is an amazing (yes, I am biased) framework which aligns to the core values and principles espoused by Agile. That’s like saying a Kanban board is, by itself, Agile. It is simply a visualization tool, but when the Agile principles are applied, it absolutely becomes a powerful tool in the arsenal.
Although I hate putting the Agile Manifesto within my presentations, thinking that most organizations are past that phase in terms of their maturity, I’m starting to re-think that logic. Going back to the foundation of Agile is extremely important. Straying away from these building blocks has led people to incorrect thinking that various tools and processes are agile by default and if they implement the tool, they too are agile.
Let’s go back to the basics when working with companies that say they want to go Agile to ensure they understand the baggage that comes with that terminology. At times we like to over-complicate the matters at hand. Trust me when I say implementing of a framework such as Scrum needs no further complication.