Books
Written to Change the Conversation
Not another manual. Not another certification companion. Books that name what most Agile literature carefully avoids.
Why I Write
The Reason These Books Exist
After more than twenty years inside enterprise IT – as a developer, project manager, and eventually Senior Scrum Master – I kept running into the same problem. The frameworks were good. The certifications were everywhere. But something was missing between the printed theory and what actually happened in the room on a Monday morning.
Most Agile literature is careful. It avoids naming the dysfunction that is sitting right in front of you. It describes the ideal state without explaining why organisations so reliably fail to reach it. I wanted to write the books I had been looking for and never found: direct, honest, and grounded in what real teams actually experience.
Not certification companions. Not motivational posters in paperback form. Books that name things, ask uncomfortable questions, and treat the reader as someone who already knows something is off – and wants to understand why.
Agile Checksum
Why the system fails even when the rituals seem correct.
After ten years across banks, telecoms, energy providers, and software houses — always close enough to see what is really happening — one pattern keeps repeating: the board is up, the ceremonies run, the language is fluent. And nothing actually changes. This book names the gap.