Contrary to a common assumption, the creation of my book “Scrum – A Pocket Guide” (2013) was anything but a long-lived hope, ambition or dream. As I shared with Joe (Jochen) Krebs on his Agile.FM podcast, it was an accidental and unplanned endeavor.
By the end of January 2013 I was not only entering my last period of work at a large consulting company, I was also asked by Dutch publishing house Van Haren to review a manuscript of a book about Scrum.
That turned out more difficult than expected. I gave it a few attempts but each time I ended up not finishing the manuscript completely or fluently. I found myself changing and updating the content way too much. And -most of all- I found myself not recognizing and not liking much of what I was reading. I felt bad about it. I felt even worse for being unable to turn my findings into positive, constructive feedback that would be helpful for both the (unknown) author and the publisher.
After a few weeks of mentally running around in circles I decided to skip a detailed reading, but go through the manuscript once more and list my biggest findings. At the bottom of the still impressive list, my most important remark to the editor was to not mention my name as a reviewer in case it was decided to move forward with the publication.
Soon I received news that the publication was cancelled. It turned out that most reviewers were not too impressed. The publisher shared that they still saw value in a book about Scrum and asked how I envisioned a possible involvement. A quick consultation round within my network, including Ken Schwaber, helped me set aside the doubts whether I could write a book myself and got me into grabbing the opportunity.
I was completely unsure of what I was getting myself into, but I felt somewhat comforted by the idea that I had 2 full months to work on it (April-May 2013), the time between ending my work at the consulting company and starting my partnership with Ken at Scrum.org.
I additionally found comfort in the fact that I had already published quite some articles and blog notes on Scrum. I assumed that I could easily assemble them into a book. How I was wrong! As soon as I had brought my previous publications together, the real work started, taking much, much more time than I ever could have anticipated. That time went into writing and rewriting, eliminating, simplifying, improving flow and cohesion, stepping back, waiting and getting back to it, aiming at barely enough descriptions to trigger the reader’s imagination. My first working title was “The path of Scrum (A comprehensive travel companion)“. That changed into „Scrum Pocket Guide (A smart travel companion)“ and ended up as “Scrum – A Pocket Guide (A Smart Travel Companion)”.
At the heart of my book are the (mandatory) rules of Scrum, from a deep understanding of the purpose of the rules, the main principles underlying Scrum and the Scrum Values. The essential rules are clearly distinguished from (possible) tactics to apply the rules. Some historical perspective to the becoming of Scrum (and Agile) is added, while I end the book reflecting on the future state of Scrum, the challenges that lie ahead of us. I consider “discovery” and “journey” the ultimate key words in the way I wanted to present the Scrum framework. Scrum is the compass that guides people and organizations on their journey of discovery in the land of complex challenges. Adopting and employing Scrum is in itself however also a journey of discovery. Hence the subtitle of my pocket guide to Scrum, “A Smart Travel Companion,” and the picture on the initial cover.
When visiting the Scrum.org office in Burlington-Boston in June 2013 I shared my final manuscript with Ken, and Ken kindly agreed to write a foreword, which he delivered in August (find it below).
Finally, in November 2013 I was able to announce that my book was released to the world, and available in all major formats (hard copy, Kindle, PDF, eBook, ePub) and via all main channels worldwide. If you have trouble finding my book, ask Google.
And my personal amazing journey as an author continued, with many unanticipated consequences of the accidental creation of my pocket guide to Scrum:
- In the spring of 2016 I created a Dutch translation of my book as “Scrum Wegwijzer“.
- In the fall of 2016, at the occasion of the 4th reprint, the cover of the English version got updated and I recorded a 3-minutes introduction of Scrum.
- In 2017 (spring) Peter Götz and Uwe Schirmer created a German translation as “Scrum Taschenbuch“.
- All that time, my book remained in the best-seller list of my publisher, Van Haren (the Netherlands).
- In 2018 I have created a second edition of my book. This time around it was a deliberate evolution rather than an accidental creation.
- In 2018 several people approached me to create translations of my book. Stay tuned for more news.
It is quite amazing and humbling that the result of my accidental work in 2013, after 5+ years, is more alive than ever. I hope you open up my book again now in a while, to find information that is most valuable to where you are on your journey at that time.
independent Scrum Caretaker
(Thank you, Higher View, for your professional expertise in video creations)
The foreword to “Scrum – A Pocket Guide” by Ken Schwaber, Scrum co-creator:
An outstanding accomplishment that simmers with intelligence.
Scrum – A Pocket Guide is an extraordinarily competent book. Gunther has described everything about Scrum in well-formed, clearly written descriptions that flow with insight, understanding, and perception. Yet, you are never struck by these attributes. You simply benefit from them, later thinking, “That was really, really helpful. I found what I needed to know, readily understood what I wanted, and wasn’t bothered by irrelevancies.”
I have struggled to write this foreword. I feel the foreword should be as well-written as the book it describes. In this case, that is hard. Read Gunther’s book. Read it in part, or read it in whole. You will be satisfied.
Scrum is simple, but complete and competent in addressing complex problems. Gunther’s pocket guide is complete and competent in addressing understanding a simple framework for addressing complex problems, Scrum.