InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Sowing Organic Change

Posted by Deborah Hartmann Preuss on Jun 08, 2006

Sections
Process & Practices
Topics
Agile in the Enterprise ,
Agile ,
Change
Tags
Coaching and Mentoring ,
Retrospectives ,
Kaizen ,
Facilitation
Kevin Rutherford is an Agile Coach in the UK, and one of the people behind Carnival of the Agilists, a monthly digest of notable Agile postings. Last week he wrote, on his own SilkAndSpinach blog:
"Through bitter experience I've come to recognise that change works best when it isn't inposed, and when it is allowed to occur over a period of time."
The tools he uses to foster more organic change include:
  • Current Reality Tree,
  • Simulations and
  • Hansei-kaizen.
The latter is a set of Japanese terms, used in the lean manufacturing arena. But by any name they are also key practices upon which Agile's empirical processes are built: relentless reflection (hansei) and continuous improvement (kaizen). This pattern is repeated in various ways in Agile methods - from micro (TDD unit testing) to macro (project retrospectives), and everywhere in between. Unfortunately, he hasn't provided a link for further reading on this thinking tool, but it's found throughout the agile literature - watch for terms like "reflection", "retrospective", "inspect-and-adapt', and, less originally, "learning". It even extends to management: Joshu Kerievsky of Industrial Logic teaches organizations to use management tests as yet another opportunity for incremental learning.
  • This article is part of a featured topic series on Agile
More info? by Michael Furtak Posted
Re: More info? by Deborah Hartmann Posted
  1. Back to top

    More info?

    by Michael Furtak

    This is interesting, but very light on information for those who are not that familiar with all aspects of the Agile process.

    What is a "Reality Tree"?
    What are involved in these "Simulations"?

  2. Back to top

    Re: More info?

    by Deborah Hartmann

    Hi Michael.
    Agile coaches (and other kinds of teachers)are always creating new simulations... they're often proprietary tools of the trade, but sometimes they get published. Good sources are Bill Wake, Jean Tabaka who taught how to run this simulation at Agile2005 and those who attended would have her materials. The Lean and TOC schools have spawned a number of simulations - I'll use a simple one at Agile2006, but you can see a more complex one for teams.
    And you can follow the CRT link from the blog above to the focusedperformance.com site which teaches about CRT.
    (Hope these links work... :-)
    deb

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.