AGILE IN ACTION

Sunday, 17 December 2006

Values, Practices & Principles

Posted by Gus Power

‘What’s the difference?!’

It seems that there’s a lot of confusion about these terms of late.

Values . These are the ideals that a group of people embrace. They can be positive or negative - e.g. empowerment or control. These values are implicit in the personality or culture of a company. Values are often emotive - they represent driving forces behind people.

Principles . Although the word stems from the Latin for leader or emperor, in this context we’re talking about it as a general law or essence - e.g. principles of modern physics

Practices . The easiest one to grasp - a set of repeatable actions you perform. Practice the flute. Practice loyalty. Practice developing software by driving with tests. OK, that one’s easy.

So how do these terms tie together? A practice works in a given context due to an underlying principle or principles. For example, the practice of employing small easy-to-adjust tooling machinery in place of one large cumbersome automated device is more productive for a manufacturing line with varying output requirements. The underlying principle is basically to ‘smooth the value stream’ - reducing bottlenecks to enable flow. Continuous integration is a software development practice that is backed by the same principle. For an individual to adopt a practice they must see that the practice works in the field and understand the principle(s) behind it.

How are values related? Practices produce effects that support one or more values.If a development organisation values the ability to meet their customers needs (rather than make the customer fit their needs as so often happens), then a practice such as TDD will support that value as it keeps the cost of change low over time (the principles, to name but a few: once and once only, simplest thing that works). This is where Agile/XP teams often run into difficulty with organisational structure - many of the practices support values that are not necessarily consistent with those of the organisation (empowerment being a key example). Worse still, a company may have no common values (perhaps due to a lack of common vision or leadership) or different elements of a company may hold conflicting values.


Creative Commons Licence

Recent Posts

  1. System failure is inevitable so design for a fast recovery
  2. Delight comes as a surprise in unexpected places
  3. Help create business agility. Bake quality in
  4. Governance - Friend or Foe?
  5. 70% Forum
  6. Measuring purpose. Measuring customer delight
  7. Stop pushing features and start delighting users
  8. Lost without a goal
  9. Emotion creates the common language
  10. Five sneaky ways to kill an initiative

Archives

  1. 2012 (16)
  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 (40) culture (18) extreme programming (21) leadership (18) lean (47) people (26) planning (17) retrospective (18) scrum (41) story (19) team (30) testing (19) xpday (19)