AGILE IN ACTION

Friday, 29 December 2006

Bit by bit or all at once?

Posted by Simon Baker

In his book The Fifth Discipline, Peter Senge says:

From a very early age, we are taught to break apart problems. This apparently makes complexity more manageable, but we pay a hidden price. We can no longer see the consequences of our actions; we lose our intrinsic sense of connection to a larger whole. When we try to ‘see the big picture’, we try to reassemble the fragments in our minds, to organize all the pieces. But, as physicist David Bohm says, the task is futile - similar to trying to reassemble the fragments of a broken mirror to see a true reflection. Thus, after a while we give up trying to see the whole altogether.

I think this difficulty emerges when a team tries to adopt only a few Extreme Programming practices at a time. It’s understandable why this approach is taken. Most people assimilate new things when they’re introduced gradually. Too much, all at once, and people can feel overwhelmed. In my experience, however, when you take this approach teams struggle to pull it all together. They compartmentalize the practices and do not realize the whole that is Extreme Programming. So, if I have a choice, I will always introduce everything in one go and then help people to bring it all together, everyday in all that they do. Certainly it’s a challenge for people to learn this way but it’s definitely not impossible. And when they succeed it’s a measure of their abilities.

Creative Commons Licence

Recent Posts

  1. Pursuing features increases total cost of ownership
  2. Organization complexity is a waste farm
  3. Managing costs provides a false sense of security
  4. State of Agile survey for 2011 tells a familiar story
  5. (I can't get no) satisfaction, let alone customer delight
  6. Positive emotions and purpose
  7. People don't buy what you do, they buy why you do it
  8. Too busy chopping wood to sharpen the axe
  9. So you want a fresh apple
  10. Systems are seductive

Archives

  1. 2012 (6)
  2. 2011 (24)
  3. 2010 (31)
  4. 2009 (41)
  5. 2008 (69)
  6. 2007 (152)
  7. 2006 (128)
    1. December (16)
      1. Bit by bit or all at once?
      2. Peacocks and penguins
      3. First incremental release of badjit
      4. Values, Practices & Principles
      5. On average
      6. Agile finances?
      7. ABC2006: Scaling agile
      8. XPDAY2006: Joshua Kerievsky's keynote speech
      9. XPDAY2006: The Toyota Way of Managing
      10. XPDAY2006: Experiments in Agile Estimation
      11. Ken Schwaber talks about agile quality
      12. XPDAY2006: Keeping the Furniture Police at Bay
      13. XPDAY2006: Are We Nearly There Yet?
      14. Running tested features
      15. Ultimate extreme feedback device
      16. Gus has got a wiki going
    2. November (26)
    3. October (7)
    4. September (11)
    5. August (7)
    6. July (7)
    7. June (4)
    8. May (4)
    9. April (4)
    10. March (4)
    11. February (14)
    12. January (24)
  8. 2005 (63)
  9. 2004 (2)

Tags

agile (43) big visible chart (15) conference (39) culture (18) extreme programming (21) leadership (18) lean (47) people (26) planning (17) retrospective (18) scrum (41) story (18) team (30) testing (18) xpday (19)