« December 2005 »
S M T W T F S
1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31


Monday, 12 December 2005
When to be Agile
Topic: Agile management

In Balancing Agility and Discipline: A Guide for the Perplexed, authors Barry Boehm and Richard Turner suggest the following guidelines for choosing an adaptive or a predictive approach to any given project:

Agile home ground Plan-driven home ground
  • Low criticality
  • Senior developers
  • High requirements change
  • Small number of developers
  • Culture that thrives on chaos
  • High criticality
  • Junior developers
  • Low requirements change
  • Large number of developers
  • Culture that demands order

Since the book was published, Agile development practices have evolved considerably. As they have been adopted and adapted as enterprise practices, the criteria for choosing adaptive vs predictive development have changed. I think an updated list of guidelines might read as follows:

Adaptive (Agile) Predictive (Waterfall)
  • Low urgency and low uncertainty
  • Repeating process
  • Not new product development
  • Traditional, process-oriented staff
  • Low level of direct customer participation

Please see the article When to be Agile for a more detailed presentation of these ideas.


Posted by Dave Nicolette at 12:01 AM EST
Post Comment | Permalink

View Latest Entries