One of the issues that Product Managers commonly face when engaging with teams who claim to be, or who want to be, “Agile” is that most people have never really take the time to actually research the origins of the Agile movement, the principles upon which it is based, or even the histories of the specific practices that have grown from these principles. All too often, teams and companies begin their way down a transition to Agile practices as blindly as a bat fluttering out of its cave into the sunlight.
The fact is, there is a long and storied history to be found, and one of the best places to start is by reviewing the Agile Manifesto, which in many ways was the first coordinated effort to coalesce a variety of different approaches under a single set of guiding principles. After a few online conversations, I thought it might be useful to present a few common misinterpretations of the Agile principles and explain why they’re incorrect. To start with today, I’m going to dig on on the first two statements in the Agile Manifesto:
- Individuals and Interactions over Processes and Tools
- Working Software over Comprehensive Documentation