> Individuals and interactions over processes and tools
> Working software over comprehensive documentation
> Customer collaboration over contract negotiation
> Responding to change over following a plan
I would read it, but I am running late for my daily standup and haven’t finished updating JIRA yet to document my progress since yesterday’s standup.
To me the real message was "think for yourself and do what works best for you", and the organizations that actually do that typically don't need to be given directions and don't follow advice from productivity gurus. Toyota didn't read the Agile Manifesto and come up with their own solution to their own problems.
The people that fell in love with Agile where the most further from it, the message was vague enough that they would seek more concrete frameworks, which inevitably would put them out of the "think for yourself" zone.
The following paragraphs, what everyone misses, essentially say "but that is not enough, you also need..."
I'm not saying this is the outcome of an Agile approach, but sure seems common on the Scrum projects I work on.