Courage: The Root of All Agile
Why is it that a team can be skilled in fundamental agile practices, have access to agile tools and still not be able to achieve the benefits of agile, namely faster delivery, higher quality, lower cost and greater business value?
In my experience, the answer nearly always boils down to a failure to exercise Courage. Wikipedia defines courage as the ability to confront fear, pain, danger, uncertainty or intimidation. You might say, courage means to “do it scared”.
Courage is the common denominator that belies all brands of agile, be it SCRUM, FDD, Crystal, extreme programming and others. Moreover, if you take a look at the Agile Manifesto as espoused by the Agile Alliance and the Declaration of Interdependence developed by the founders of the Agile Project Leadership Network, you’ll see that courage is the silent servant of most of the esteemed practices described therein.
Got Courage at the Organizational Level?
The overarching reason that agile requires courage is that it usually involves bucking the project management status quo, which is typically deeply rooted in a Newtonian mindset rather than what I like to refer to as a Quantum mindset.
Notice in Table 1 that the two mindsets are mirror opposites:
Table 1: Newtonian and Quantum Mindsets
|
Newtonian Mindset
|
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Impartial observers from other planets would consider ours an utterly bizarre enclave if it were populated by birds, defined as flying animals, that nevertheless rarely or never actually flew. They would also be perplexed if they encountered in our seas, lakes, rivers and ponds, creatures defined as swimmers that never did any swimming. But they would be even more surprised to encounter a species defined as a thinking animal if, in fact, the creature very rarely indulged in actual thinking." - Steve Allen |




