In the early part of the decade Nicholas Cage starred in the movie “Gone in 60 Seconds,” something about stealing cars very rapidly. In the mid-1980’s colleague Ken Orr wrote “The 1-Minute Methodology,” that uncovered the secret to speed—disconnect input from output. If you can steal a car in 60 seconds or execute a methodology in a minute, why not learn to be agile in 90 seconds? I get tired of articles like “The 3 things you must know to be agile,” or “Five easy steps to agile implementation,” or “The secrets of agility unleashed,” or “Agile Mastery in Minutes.” Software development is hard. Agile may be a better way to approach software development, but Read more
Posts Tagged 'adapting'
Agile methods are geared to managing uncertainty – uncertainty related to “ends” (customer objectives and features), and uncertainty related to “means” (technology and people). One way in which agile approaches deal with uncertainty is frequent re-planning based on progress to date and new information gathered during development iterations. The positive aspect of agile methods is that they encourage dealing with the uncertainty early in a project and focus on working software. Unfortunately, these very aspects of agile methods can also have negative outcomes – sloppy planning, and reactive thinking. All agile projects combine aspects of anticipation (planning) and adaptation (revisions based on reflections). Too great an emphasis on adaptation (we can always fix or refactor Read more