I remember is as if it was yesterday. It was 2000 – 2001. I was working at Lucent (Bell Labs) at the time when the telecommunications bubble burst and I was laid off from my job. Along with thousands of others across the industry.
Lucent had a development center on the campus of NC State here in Raleigh, NC. There were ~300 folks that worked there and we were all let go.
But it was a protracted departure, as the process took about 3-months for everyone to pack up and leave the building in waves. I was one of the leaders who stayed until the very end and turned off the lights. Lucky me.
I had a lot of idle time and I started to write a book to fill that space. It wasn’t something I’d planned, but it was a topic that I had some passion around (and thoughts to share). The book became Software Endgames, which was eventually published by Dorset House in 2004.
Since then, I’ve self-published three books related to agile topics. One of them, Scrum Product Ownership, is in it’s 3’rd Edition.
People often ask me for advice around writing. Usually, it’s related to how to get started. Sometimes the discussion is around their ambition to write a book. While I don’t consider myself an expert in either space, I decided to share my learnings in this 3-part article series. I hope you find some value in it.