When talking about Agile software development, I like using the analogy of tightrope walking. I think it’s a good metaphor to describe the challenges normally encountered when developing software and the inspect&adapt nature of Agile.

The similarities between the two worlds are many:

• Like software development, tightrope walking is difficult;
• Like software development, tightrope walking is dangerous;
• Like software development, tightrope walking cannot be easily predicted;
• Like software development, tightrope walking requires courage;

I could continue.

Ask a tightrope walker to estimate how long it’s going to take her to get from one side to the other of the rope, ask her to establish a detailed plan predicting all her steps, and demand that she sticks to that plan. At the first unanticipated bird flying too close, a wind draft, or a swing of the rope, she will certainly fall.

Instead, let her take a few steps at a time so that she can inspect her new condition and adapt her balance; allow her to change her strategy if anything unexpected happens: the chances that she will get to the other side of the rope will be extremely high.