Recent Posts

  1. Old norms from Training Within Industry get a dust-off
  2. Acceptance tests ain't noise pollution
  3. Boards for a more user-focused discovery-oriented approach
  4. Sketchnotes made during one of our training sessions
  5. PDCA-powered learning
  6. If you're estimating, know why you're estimating
  7. Driving continuous improvement with PDCA and measurements
  8. You should probably watch this, if you haven't already
  9. HTTP Caching in Grails at GGUG
  10. Dealing with organizational complexity goes in the 'too hard' box

Archives

  1. 2010
    1. September
    2. August
    3. April
    4. March
    5. February
    6. January
  2. 2009
    1. December
    2. November
    3. October
    4. September
    5. August
    6. July
    7. May
    8. April
    9. March
    10. February
    11. January
  3. 2008
    1. December
    2. November
    3. October
    4. September
    5. August
    6. July
    7. June
    8. May
    9. April
    10. March
    11. February
    12. January
  4. 2007
    1. December
    2. November
    3. October
    4. September
    5. August
    6. July
    7. June
    8. May
    9. April
    10. March
    11. February
    12. January
  5. 2006
    1. December
    2. November
    3. October
    4. September
    5. August
    6. July
    7. June
    8. May
    9. April
    10. March
    11. February
    12. January
  6. 2005
    1. December
    2. November
    3. October
    4. August
    5. July
    6. June
    7. May
  7. 2004
    1. November
    2. October

Tags

accountability (3) adaptation (6) adaptive planning (7) agile (124) agile alliance (3) agile business conference (10) agile manifesto (5) agile planning (7) agile principles (9) agile values (10) agile2008 (11) apln (3) extreme programming (36) lean (35) scrum (49)

Thursday, 10 August 2006

Modelling and models

The value is in the modelling and not in the model. You model to explore and understand something better. The value is what you learn from the modelling experience. The model is a side-effect of the modelling and not the result. Don't waste energy trying to keep it in-synch with the source code as you move forward.


Tags: agile , modelling
Posted by Simon Baker - Permalink

Feeds

Creative Commons Licence

Agile in Action

preload call-us-on.png preload chat-over-coffee-on.png preload coffee-cup-on.png preload guspower-avatar.png preload simonbaker-avatar.png preload email-on.png preload meet-the-crew-on.png preload about-on.png preload bits-on.png preload blog-on.png preload coaching-on.png preload consulting-on.png preload crew-on.png preload home-on.png preload software-on.png preload other-talks-on.png preload phone-on.png preload previous-talks-on.png preload boost-icon-on.png preload jumpstart-icon-on.png preload liftoff-icon-on.png preload powerup-icon-on.png preload skype-on.png preload speech-bubbles-on.png preload creative-commons-on.png preload slides-on.png preload video-on.png