Thought provoking blog post from Mike Hadlow on the way Agile is often hijacked by non-technical managers with little talent.
Somehow, over the decade or so since the original agile manifesto, agile has come to mean ‘management agile’. It’s been captured by management consultants and distilled as a small set of non-technical rituals that emerged from the much larger, richer, but often deeply technical set of agile practices.
I agree with this from one of the many comments:
The most successful teams I have seen made use of “tech leads” who were engineers capable of running a project.



This book was pretty ordinary, which made me wonder how often you can accurately identify a rotten book within the first chapter? If you have a good prediction rate, you could save valuable reading time for better books. A give-away from this book was the amount of the story that was told via dialogue. Whole chapters without any narrative. And another flaw was the lack of emotional depth – much is made of a “Famous Day” that Kay and Simon spent together – so why not, you know, actually put it in the book. It needn’t even be at the start – tuck it in further down the book – but don’t leave it out completely! 