Writing the Least Amount of Software


Nice to hear Gojko in his Agile Adria presentation, “Make Impacts Not Software”, discuss “off roading” – a term I often use when discussing software projects.  Takeaways from the presentation:

  • Up front decisions prior to software creating can’t be fixed by software
  • Code coverage is not a measure of success
  • Design Thinking for business
  • Robert Brinkerhoff
  • Data to confirm the engine is working
  • Impact Mapping provides a map of success – connections are assumptions on the map.
  • The Learning Alliance: Systems Thinking in Human Resource Development
  • Effect Managing IT
  • How to Measure Anything: Finding the Value of Intangibles in Business

~ by mdavey on August 8, 2013.

One Response to “Writing the Least Amount of Software”

  1. Very interesting talk “Make Impacts Not Software” by Gojko Adzic. It gave me a number of things to think about. I have been in a number of organizations where change is made without any way to measure if the change had the desired impact. Often no real thought was even given to what the actual impact should be. Just a very fuzzy notion that there should be some “improvement”. I look forward to reading “How to Measure Anything: Finding the Value of ‘Intangibles’ in Business” by Douglas W. Hubbard.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: