InfoQ

News

Kaizen in Lean Software Development

Posted by Geoffrey Wiseman on Jul 25, 2007 07:30 AM

Community
Agile
Topics
Artifacts & Tools ,
Change
Tags
Continuous Improvement ,
Kaizen ,
Retrospectives ,
Lean

Lean methods employ Kaizen, or continuous improvement, to reduce waste and improve results on a regular, even daily, basis. On the leanagilescrum group, Alan asked:

[A]re there known techniques for facilitating kaizen activities within Lean/Agile software development?

Martin suggested:

To me, software Kaizen is more than looking for waste, it's looking for ways you can improve things all across the board.

I'm a hands-on developer, so I'm pretty code-quality focused. If you have a horrible untested/untestable legacy codebase, it's pretty easy to measure the improvements you can make by refactoring to testability/design patterns. I guess you can look at that as reducing the wasted time people scratch their heads and say "how's that supposed to work?"

I like to look things like number of classes under test, percentage of code coverage (although this is tricky by itself).

I strongly believe that if you don't have high quality code, you'll only be able to go so far with other Kaizen approaches.

Finally, Phillip responds with a detailed review of steps to follow before, after and during a Kaizen event, closing with:

The above described process should happen in less than a week. The spirit of Kaizen is to identify waste and eliminate it through process improvement, do so quickly involving the people actually doing the work, implement the change, support and monitor the change, then start all over again.

In a related blog post, Bruno Câmara analyzes the intersection between Scrum and Kaizen, suggesting that incremental improvements are made in the sprint retrospective, and that collecting and analyzing data is done daily with the burndown chart and project backlog. Broadening the scope somewhat, he suggests that that agile processes avoid waste through excess documentation, and that agile's small self-managed skilled teams push decision-making to the developers, as Kaizen intends.

For more information on Lean, Kaizen, Retrospectives and Continuous Improvement, read on at InfoQ.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
Throughput management by Steven Devijver Posted Jul 25, 2007 8:37 AM
Sprint Retrospectives Cycle to long for Kaizen by Stefan Roock Posted Jul 25, 2007 1:36 PM
Kaizen is process profiling by Alex Popescu Posted Jul 25, 2007 2:08 PM
The Kaizen Manifesto by Tom Scott Posted Jul 25, 2007 5:41 PM
Re: The Kaizen Manifesto by Alex Popescu Posted Jul 25, 2007 8:07 PM
Re: The Kaizen Manifesto by Phillip Cave Posted Jul 31, 2007 12:54 PM
  1. Back to top

    Throughput management

    Jul 25, 2007 8:37 AM by Steven Devijver

    I'm inspired by the theory of constraint: http://en.wikipedia.org/wiki/Theory_of_constraints And throughput accounting: http://en.wikipedia.org/wiki/Throughput_accounting For me in software development you have to pull result out. Typically, if you don't test some aspect of an application you can't be sure if it works as expected. Hence you have to pull results out of the development process by testing.

  2. Back to top

    Sprint Retrospectives Cycle to long for Kaizen

    Jul 25, 2007 1:36 PM by Stefan Roock

    Kaizen is about micro improvements. Sprint Retrospective Cycles are too long to remember all the micro problems und potential micro improvements. Creating an impediments backlog at the daily standups may help since the cycle is much shorter. http://jeffsutherland.com/scrum/2006/06/why-three-questions-in-daily-scrum.html

  3. Back to top

    Kaizen is process profiling

    Jul 25, 2007 2:08 PM by Alex Popescu

    If you read Phillip's steps and you are in software development field you will notice it is hugely similar to the app profiling activity: - observe and measure the app - try out different approaches - keep an eye on it So, imo in this case Kaizen sounds like a development process profiling. ./alex -- .w( the_mindstorm )p. ________________________ Alexandru Popescu Senior Software Eng. InfoQ TechLead&CoFounder

  4. Back to top

    The Kaizen Manifesto

    Jul 25, 2007 5:41 PM by Tom Scott

    Robert Hoekman has written the Kaizen Manifesto (http://www.kaizenmanifesto.org/) in which he suggests the principles of the kaizen manifesto are: 1. Make continuous improvements in every aspect of the business. 2. Actively pursue a superior, complete customer experience. 3. Continually improve designs, code, and processes. 4. Strive to increase agility (binshou) while reducing costs. 5. Use the Deming Cycle to minimize disruption from change. 6. Prevent errors (poka-yoke), in software and in business. 7. Respect people, leverage expertise, and trust staff. 8. Reward suggestions, improvements, and progress. 9. Always move forward. Although I'm not sure I buy into his critique vis-a-vis agile and Kaizen (see http://derivadow.com/2007/03/07/maintaining-agility-and-kaizen/)

  5. Back to top

    Re: The Kaizen Manifesto

    Jul 25, 2007 8:07 PM by Alex Popescu

    Robert Hoekman has written the Kaizen Manifesto
    Aren't these just normal rules that any sane company is supposed to use? bests, ./alex -- .w( the_mindstorm )p. ________________________ Alexandru Popescu Senior Software Eng. InfoQ TechLead&CoFounder

  6. Back to top

    Re: The Kaizen Manifesto

    Jul 31, 2007 12:54 PM by Phillip Cave

    Alex wrote: "Aren't these just normal rules that any sane company is supposed to use?" lol - yes, one would hope, however we(organizations of people) can get so bogged down with process that we forget that what we do is really about delivering value and supporting our front line workers to deliver on that value. We get so busy with "stuff" we forget to focus on analyzing and improving our "value stream" bests, ./alex -- .w( the_mindstorm )p. ________________________ Alexandru Popescu Senior Software Eng. InfoQ TechLead&CoFounder

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.