For years, we’ve heard that only collocated teams can use agile approaches. This disregards the roughly 50% of agile teams who already are distributed or dispersed and their successes or failures. Instead of assuming agile teams can only be collocated, what if we wrote a book to help distributed and dispersed teams see options for their agile success?

As we co-wrote the book, we realized we were living the same principles as distributed and dispersed agile teams do. We worked in short timeboxes and reflected often. We chose to write together, rather than separately. (We did choose to create images separately so we could then discuss them together.)

We created at least two communication paths as backup for our primary path so we always had a way to talk with each other (google docs, Zoom, and text message). We learned the power of a streak, to continue writing every day (or as close to it as we could) to finish paragraphs, sections, and chapters. We learned how to use the tools and when to evolve the tools we used. We looked like an agile team, with continuous integration, continuous delivery (to each other), and continual reflection and refinement.

We also learned several key phrases that helped us learn when we worked well and not so well together. Some of these phrases are:

* “You have to say more about that” (signaling it might be clear to one of us, but concerned a type of reader may not understand)
* “When I’m not so tired, I’m pretty human” or “the writer did not show up today” (reflect our readiness to work and where we might lean on the other person)
* Mind if I tweak that? (to switch pairing)
* “I found where you are” and “Let me click to where you are” (when we needed to synchronize where we were working – in a Google doc)
* “I’m okay with that” (reviewing work)
* Comments, highlights and XX marks the spot for more work

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.