Letting Go of 'Pure' Agile
I probably need to stop paying so much attention to my LinkedIn feed. It inevitably frustrates me. On the other hand, I channel the frustration into articles like this one. This time, as is often the case to be honest, my frustration comes from proponents of Agile who are focused on the pure ideals of what Agile was originally intended to be. Note that I didn’t write “what Agile is” because that's evolved, while some of the purists have not.
One exchange went something like “I can’t believe how many people claim that Kanban is an Agile methodology, next time someone says that to you, make sure to tell them that they’re wrong.” Which generated responses like “I know, it’s crazy, the next thing you know they’ll be claiming that Lean is an Agile methodology!” Now, the information conveyed isn’t wrong — Lean started in manufacturing long before the Agile Manifesto was written, and Kanban was originally a way to visualize the flow of work within Lean manufacturing environments.
My issue is that most people aren’t going to worry about the nuances of how these approaches started, what they were originally designed for, and whether they are part of ‘pure’ Agile. They’re just going to read that Lean and Kanban aren’t Agile and interpret that they are inappropriate for an organization that is looking to become more Agile. Which couldn’t be further from the truth.
Please log in or sign up below to read the rest of the article.