Since the beginning of the 21st century, the software development industry has undergone a tremendous number of changes. Nowadays, if you aren’t familiar with Agile methodologies and words like Kanban and Scrum leave you puzzled, chances are you might hear, “Out of the profession!”
Many people now see Agile methodologies as some kind of panacea for all problems. It’s like, “Back in the day, everyone worked with Waterfall, so things were slow, expensive, and unpredictable.” And if you suddenly switch to modern agile methodologies, happiness will immediately follow. But there is no cure-all, and any methodology requires proper application. In my experience, I haven’t seen a single company that fully applies all aspects of agile methodologies, and that’s generally fine. Agile is more about approaches and practices that each team should try, experiment with, and find what works best for them. Of course, there are certain principles that need to be followed.
I also know several companies (fairly large ones) that became disillusioned with Agile after trying the wrong approach or implementing it incorrectly. Personally, I’m not an avid fan of every methodology, but I’ve worked extensively with Agile, tried different approaches with teams, and continuously read about implementation practices—regardless of the old saying, it’s better to learn from others’ experience.
And I must say, there aren’t that many good books on the subject. Many authors provide rather superficial descriptions of techniques, while some are more focused on selling themselves as trainers than on helping companies understand what to do and how to do it. I can say that even some official certifications from the Agile community provide very superficial knowledge, and people then flaunt an official certificate without any real experience or, at times, even a basic understanding of how to work with the methodology.
Read more
