AGILE IN ACTION

Monday, 2 January 2006

The speed of thinking

Posted by Simon Baker

In his post Doing fast things or doing things fast , Jeffrey Phillips says "there’s a difference between efficiency and effectiveness, mostly in terms of intent". The difference between efficiency and effectiveness is one of the topics discussed in Tom DeMarco’ s book, Slack . In the book, Tom DeMarco quotes Tim Lister as saying " People under time pressure don’t think faster ".

Basically, when working with software, thinking takes as long as it takes and there’s nothing you can do to think more quickly. So if you want things to go faster you have to find other areas in which to accelerate. Tom DeMarco identifies the only options for making things go faster as eliminating wasted time, deferring non-critical work, and working late. If you’re using agile techniques you’ll be addressing some or all of these options already.

  • Eliminating wasted time : Tom DeMarco says that healthy ‘knowledge-workers’ don’t waste a lot of time anyway because they’re more likely to be frustrated by it. One of the rules of lean development is to eliminate all waste, including wasted time in the form of extra processes, unwanted features, task switching, waiting around, and motion or chasing around, perhaps seeking answers to questions.
  • Deferring non-critical work : Tom DeMarco says that healthy ‘knowledge-workers’ derive satisfaction from accomplishment and are therefore likely to work on tasks on the critical path. Extreme Programming uses an onsite customer and Scrum uses a product owner to prioritise the work by business value, and the development team selects an amount of work equivalent to their velocity from the highest business-value items.
  • Working late : Tom DeMarco says that, in the short-term, working late can boost productivity but in the longer term excessive hours cannot be sustained. When you work late for extended periods your personal life and your health are not the only things to suffer. More directly, your concentration levels, your ability to focus and think clearly, and your attention to detail deteriorate and ultimately degrade the quality of your work. This style of working rapidly becomes a negative spiral. Extreme Programming employs the primary practice of energized work , which states that you should work only as many hours as you can be productive and only as many hours as you can sustain.

Creative Commons Licence

Recent Posts

  1. Managing costs provides a false sense of security
  2. State of Agile survey for 2011 tells a familiar story
  3. (I can't get no) satisfaction, let alone customer delight
  4. Positive emotions and purpose
  5. People don't buy what you do, they buy why you do it
  6. Too busy chopping wood to sharpen the axe
  7. So you want a fresh apple
  8. Systems are seductive
  9. Crack cocaine problem-solving and complexity
  10. Beware the Coefficient of Fiction

Archives

  1. 2012 (4)
  2. 2011 (24)
  3. 2010 (31)
  4. 2009 (41)
  5. 2008 (69)
  6. 2007 (152)
  7. 2006 (128)
    1. December (16)
    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)
      1. Look after your product backlog
      2. 1-week iterations
      3. Root cause analysis using 5 Whys
      4. Agile In Action is now available at Artima
      5. Planning with the Horizon of Predictability
      6. The knowledge worker and the new organisation
      7. Setting Norms to help internalise Agile values
      8. Agile is ... Agile isn't ...
      9. It doesn't have to be about business value
      10. Task-switching is waste
      11. Flow, ideal time and the E-factor
      12. A Scrum Master is like a music conductor
      13. Slack != Waste
      14. Go on. You know you want to. Say 'Hello'
      15. Spike
      16. Why agile principles are important
      17. Pareto Principle
      18. My interaction style
      19. An 'aeroplane in flight' metaphor for agile tracking
      20. A Scrum Master is like a skilled helmsman
      21. Fun and games
      22. Innovation games from enthiosys
      23. Thomas Edison on 'Lean'
      24. The speed of thinking
  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)