Lean Principle #1 – Eliminate Waste

Lean Software Development Principles - Eliminate Waste.Lean software development advocates 7 lean principles, the first of which is Eliminate Waste‘.

Sounds obvious really. How many people came to work today to spend their time on waste? Some maybe! But not most. So what is waste, and how do you identify it?

Some waste is obvious. But other forms of waste are more difficult to spot or to solve. I’m sure in most organisations it’s sometimes very difficult to identify what is waste and what is not. Some processes or conventions might seem wasteful, but actually provide real value elsewhere in the organisation, or prevent other forms of waste from emerging later. Other activities may seem valuable, but actually do not really result in any real value.

As I mentioned in my opening post about the 7 Key Principles of Lean Software Development, lean development originated from lean manufacturing and the Toyota Production System in Japan. In these methods, they identified 3 general forms of waste, which they called in Japanese – ‘Muda‘ (meaning unproductive), ‘Mura‘ (unevenness, inconsistency) and ‘Muri‘ (over-burden, unreasonableness).

In doing this, they also identified 7 particular types of waste in manufacturing:

  1. Over-production
  2. Unnecessary transportation
  3. Inventory
  4. Motion
  5. Defects
  6. Over-processing
  7. Waiting

In lean software development, Tom and Mary Poppendieck translated these wastes into some things more specifically relevant to software development. For instance:

  • unnecessary code or functionality
  • starting more than can be completed
  • delay in the software development process
  • unclear or constantly changing requirements
  • bureaucracy
  • slow or ineffective communication
  • partially done work
  • defects and quality issues
  • task switching

A common agile development practice is the ‘retrospective’, which is the process of the team meeting after each short iteration to discuss what went well, what didn’t, and what could be done differently in the next iteration.

This iterative process of learning and continual improvement is an important part of identifying waste and eliminating it. In my experience this is one of the key benefits of agile software development.

Traditional software development and project management methods advocate a ‘lessons learnt’ process, but it generally takes place at the end of a project. By this time, things are forgotten, people have changed, the context has changed, and the team may be disbanding to move on to another project. As a result, the team may never really get a chance to put these learnings and changes into practice.

With agile development, these retrospectives enable the team to make small improvements regularly, and tackle changes in manageable, bite-sized pieces that can be actioned immediately.

Identifying and eliminating waste should not be a rare event conducted by process re-engineering consultants every few years. It should be a regular process, built into regular iterations, determined as much as possible by the team, and tackled in small, timely steps.

Making improvements little-but-often in this way creates a culture of continuous improvement – a learning environment – which for some organisations could potentially give you the edge over competitors.

So if you’re not doing it already, I urge you to hold regular retrospectives. This is one agile development practice I can heartily recommend. Try to foster lively but healthy debate, critical but constructive feedback, and try to drive out meaningful and actionable improvements that actually help you to frequently identify and, more importantly, eliminate waste.


7 Key Principles of Lean Software Development:

1. Eliminate Waste
2. Build Quality In
3. Create Knowledge
4. Defer Commitment
5. Deliver Fast
6. Respect People
7. Optimise The Whole


Photo by David Enker

3 Responses to “Lean Principle #1 – Eliminate Waste”

  1. Bruno says:

    1st time i've done Scrum on a project your 10 principles were my Baseline.

    I feel know that I will start using Lean following your 7 principles.

    Thanks for this excellent post !


  2. tedzzz says:

    Part 2 is great. Part 1 is a waste.
    While that is harsh, I use it to explore one point. When someone goes and points out waste in a software company or team, you quickly start hitting individuals. The meetings, docs, processes, code, etc are some one’s baby.

    Just as a majority of people see me attacking your integrity when I call your article waste, the same carries through to software companies when waste is pointed out.

    I wager 90% of a software company’s product & assets are the people or are direct tied to the people at the hip. The question then is how to you attack the waste, without attacking the individuals? I think people especially engineers often lack tact. It is thus important to educate one on how identify waste without calling it wastes when dealing with the owners of said waste… yes? This is not an easy task.

  3. tedzzz says:

    Part 2 is great. Part 1 is a waste.
    While that is harsh, I use it to explore one point. When someone goes and points out waste in a software company or team, you quickly start hitting individuals. The meetings, docs, processes, code, etc are some one’s baby.

    Just as a majority of people see me attacking your integrity when I call your article waste, the same carries through to software companies when waste is pointed out.

Leave a Reply

What is 10 + 3 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”