Long before the Agile revolution for software development began, industry had learned that efficient production of goods required intense attention to quality, teamwork, and continuous improvement. These themes of Lean Manufacturing (which was further refined into the Toyota Production System) were never part of the original formulation of the Agile Manifesto, and are rarely mentioned as part of the traditional Agile/Scrum recipe for teams transforming to the new “Agile” mindset.

The reality is that the traditional Agile/Scrum recipe is actually a “dumbed down” version of the Toyota Production System, and makes it easier for organizations to grasp and start from. However, if organizations really want to achieve the goal of producing the software they need in a fashion that leads to High Performance Teams and Sustainable Engineering, they will need to understand the principles of Lean so they can incorporate them into their unique process. This session teaches the basics of Lean, and demonstrates how they apply to Agile development. 


Outline/Structure of the Talk

The session will be culled down from the Prezi that the Slideshare shows.  The organization of the session is as follows:

  • Frame the problems (5 minutes)
  • Discuss where Lean thinking fits into the Agile mindset (10 minutes)
  • For each of the 7 Lean Wastes, discuss what the waste is all about, how this waste affects software development, how Agile/Scrum approaches elimation of the waste, what Agile/Scrum misses, and ideas of what might help solve the problem (25 minutes)
  • Closing remarks (5 minutes)

Learning Outcome

  • Understanding why Agile/Scrum practices exist as they do helps us Be Agile, rather than just Do Agile
  • Figuring out what to do in cases that Agile/Scrum don’t address well in become easier when we think in terms of Lean goals
  • Learning how to address the concerns of late Agile adopters by explaining in Lean terms

Target Audience

Everyone who wants to understand why Agile/Scrum works as it does, and anyone who wants to improve the shortcomings of the standard approach

schedule Submitted 5 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Prasad
    By Prasad  ~  4 years ago
    reply Reply



    It will be of great learning to the community the experiences and outcome from the battle filed. The topic has lot of relevance, it will create an impact if include the practical aspects of a team that have undergone these changes


    • Howard Deiner
      By Howard Deiner  ~  4 years ago
      reply Reply

      Hi Prasad!

      I completely agree.  There is much of the talk that doesn't show in the slides.  For example, the 7 slides in the "Lean Principles Applied to Software Development" section labeled "What Does Agile/Scrum Miss?" all contain real life examples where I fill in experience based observations and issues.  Sorry that it doesn't appear in the sides posted.


      --  howard

  • Savita Pahuja
    By Savita Pahuja  ~  5 years ago
    reply Reply


    Thanks for the submission.

    I wonder the coverage of all those 107 slides in 45 minutes.

    If you have applied those lean practices in any of your project, could you please include your experience with the benefits achieved.


    • Howard Deiner
      By Howard Deiner  ~  5 years ago
      reply Reply

      Hi Savita!

      Thanks for the reminder that 107 slides that was used in a 90 minute session might not fit in a 45 minute session.  ;-)  I repeat, "The session will be culled down from the Prezi that the Slideshare shows."  The outline timings still stand.  I'll be cutting out a lot of the "fluffier" stuff, and devote most of the time to the "Lean Principles Applied to Software Development" section.  

      As to application, and experience studies, the stories that you are looking for are verbals that show up in the third and fourth slides in that "Lean Principles Applied" section.  I shy away from quoting specific percentage improvement numbers, as I feel those are misleading.  I do relate them back to specific experiencs and benefits observed.  As I review the material, I can say that, without exception, all seven "What Does Agile/Scrum Miss" slides relate to specific clients I've personally worked with.  OK.  Except the Vasa story, which I'm afraid I'll have to skip over for this session (it was put in to be of particular interest to software architects in the conference I presented that deck to).

      Thanks again for giving me an oppurtunity to explain myself.  Hope my response is helpful.