Visit Citebite Deep link provided by Citebite
Close this shade
Source:  http://www.infoq.com/articles/lean-muda-muri-mura

InfoQ

Article

The Three M's - The Lean Triad

Posted by Roman Pichler on Feb 27, 2008 01:58 AM

Community
Agile
Topics
Delivering Value,
Methodologies
Tags
Continuous Improvement,
Lean,
Complementary Practices

The discussion of applying lean principles to software development has largely focused on identifying and eliminating waste (in Japanese: muda). Lean Thinking equally aims to remove overburden (Japanese: muri) and unnecessary variation (Japanese: mura). Muda, muri and mura are called "the three M's." Together they form a dissonant triad. All three M's must be eliminated to create a sustainable lean process. This article discusses the relationship between the three M's and argues that the elimination of overburden should be the first step for software development organizations in order to create a lean process.

RelatedVendorContent

Agile Metrics Tracking and Mingle Podcast + Transcript

Agile Tool Evaluation Guide

The Agile Business Analyst: Skills and Techniques needed for Agile

IBM software architect eKit: Grady Booch podcast, whitepapers, articles

Gamma's Jazz platform's first implementation: Rational Team Concert (Trial Download)

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.

Waste

Waste, in lean thinking, is defined as: all activities that do not add value from a customer perspective and that can be removed. Examples are overproduction and over-processing, work-in-process or inventory, defects, hand-over and task switching, waiting and unused employee creativity.

Value-creating activities enhance the product from a customer perspective. A good question to ask is: "Would I be happy to pay for this activity as the customer?" If the answer is yes, it is likely to be a value-creating activity. Examples are discovering and understanding customer needs and writing code. Additionally, activities such as prototyping that create the relevant knowledge to develop the software system are also valuable as the late Allen C. Ward points out. Any activities that do not create value and cannot be eliminated under the current conditions are called "non-value added" activities. Examples are configuration management and project planning activities.

The Agile Manifesto acknowledges the importance of focusing on value-creating activities in software development when it states that working software is more important than comprehensive documentation. By eliminating waste we are able to create better products, faster.

Overburden

So what's wrong with focusing, first and foremost, on seeing and eliminating waste? Even though most traditional development organizations carry out few activities that truly add value, the right approach is often to attack a different disease first: overburden. As long as people work crazy hours, and as long as projects and teams are overwhelmed by the amount of work, the removal of waste alone is ineffective. Waste is likely to creep back in unless we limit the amount of work to the capacity and capabilities of the organization. Let's assume you try to eliminate defects but the project still suffers from overburden. Chances are that quality problems reappear since the project members still feel pressured and are overworked. In fact, overburden is a major source of waste such as work-in-process, waiting and delays, task-switching and defects.

Limiting demand to capacity and capabilities is exactly what Scrum and Extreme Programming do. By empowering the team to select a realistic amount of work for a given iteration, overburden is stopped and systematically avoided. A sustainable pace is achieved. Additionally, Scrum and XP create a pull process and a steady cadence where the team essentially pulls requirements from the product backlog and transforms them into product increments on a regular basis.

One of the benefits of a pull process is that in addition to avoiding overburden, it also makes waste and other problems visible. With excessive inventory buffers gone, problems now surface quickly. Scrum recognizes the importance of recognizing and removing problems and impediments. Its daily Scrum meeting serves to systematically identify problems.

Variation

A pull process with a steady cadence creates visibility of unnecessary variation, such as differences in the size and granularity of requirements put forward to the team in the iteration planning meeting, or the use of different build scripts. Other examples of unnecessary variation are using different development tools, applying development practices such as test-first and refactoring inconsistently, as well as not following coding standards. Variation creates waste such as defective software, over-processing and rework. Standards and norms eliminate variation.

Not all variation in software development is bad, though! For instance, formulating requirements at different levels of detail in the product backlog can avoid overproduction, over-processing and rework. Creating prototypes to explore different technology and design options is a form of necessary variation that creates the relevant knowledge to make the right architecture and technology decisions. Notice that is more economical to invest in organized experimentation early on rather than to bet on one grand but possibly unproven design idea only to partly rewrite the software system later on.

Summary

To establish a lean process, the traditional development system must be fundamentally changed and the right process must be established. For software development organizations this is best achieved by applying a pull process with a steady cadence as created by Scrum and XP. This is a form of radical improvement also called kaikaku in Japanese. Once the new way of working has been established, waste and variation must be systematically eliminated. The process is hence incrementally and continuously improved, which is also known as continuous improvement or kaizen in Japanese. Reflexion and continuous improvement is facilitated by regular retrospectives. In sum, establish the right process first by removing overburden. Then empower and encourage the teams to eliminate waste and unnecessary variation relentlessly.

Literature

  • Jeffrey K Liker: The Toyota Way. McGraw-Hill. 2003.
  • James M. Morgan, Jeffrey K. Liker: The Toyota Product Development System: Integrating People, Process and Technology. Productivity Press. 2006.
  • Mary and Tom Poppendieck: Implementing Lean Software Development: From Concept to Cash. Addison-Wesley. 2006.
  • Donald G. Reinertsen: Managing the Design Factory. A Product Developer's Toolkit. Free Press. 1997.
  • Allen C. Ward: Lean Product and Process Development. Lean Enterprise Institute. 2007.
  • James P. Womack, Daniel T. Jones: Lean Thinking. Touchstone Books. 1996.

About the Author

Roman Pichler of Pichler Consulting Limited, -works as an independent consultant, trainer and coach. Roman's clients value his rich and diverse experience ranging from helping start-ups as well as large global companies to apply Lean Thinking and Scrum. He is the author of the book "Scrum - Agiles Projektmanagement richtig einsetzen" (dpunkt 2007).

8 comments

Reply

Lean triad and japanese words. by Alexander Bronshtein Posted Feb 29, 2008 11:15 AM
Re: Lean triad and japanese words. by Roman Pichler Posted Mar 1, 2008 1:44 PM
3 M's and more by Vikas Hazrati Posted Feb 29, 2008 12:15 PM
Re: Uneveness leads to overburdening leads to not eliminating waste by Richard Henderson Posted Mar 5, 2008 6:20 AM
Re: Uneveness leads to overburdening leads to not eliminating waste by Estetik Cerrahi Posted Jul 22, 2008 1:11 PM
  1. Back to top

    Lean triad and japanese words.

    Feb 29, 2008 11:15 AM by Alexander Bronshtein

    Do japanese words muda, muri, mura, etc. add any value or context to this article? Are they used to prove or illustrate any point? Are not they the waist? Do they create a variationfrom the "standard" article language? On the same note: Is value solely defined by the customer perspective? Would customer always agree to pay for activity that wold not benefit him in the short term? What is about the value in the case of conflict of interests between short term needs of customer A, sustainability of your organization and future needs of the future customer B? Is it always easy to see immediatly if variation could bring a value? How new innovative standards could take of from the ground if we ban variations from the existing standards? Does overburden has no rationale at all? Could (should?) overburden be always avoided?

  2. Back to top

    3 M's and more

    Feb 29, 2008 12:15 PM by Vikas Hazrati

    On similar lines we tried to use the Toyota lean concepts in working with a distributed team. The project was a huge sucess. More details here --> Agile Offshoring : It’s hard work but it works! on how we worked to make the project a success. http://vikashazrati.wordpress.com

  3. Back to top

    Re: Lean triad and japanese words.

    Mar 1, 2008 1:44 PM by Roman Pichler

    Alexander, Since lean thinking originated in Japan, I use the original Japanese terms in addition to their English translations – like most other Western authors do. This avoids ambiguity that can arise when words are translated. As explained in the article, I consider software development activities as valuable if they create relevant knowledge or add value from a customer perspective. Once a lean process has been established, unnecessary variation is systematically eliminated by applying continuous improvement. Watch out for two things: First, create pull or flow and then stabilize the new system before you try to standardize. Second, empower and encourage the doers (developers, testers etc.) to improve their work. I consider overburden a curse. It is plain wrong. You may gain short term wins but you sacrifice a better and brighter future. Roman

  4. Thought it's worth pointing to Jim Womack's e-letter that describes how mura creates muri that undercuts efforts to remove muda.

  5. Hi Jason, Thanks for the link – I had completely forgotten about this e-letter :-) I would still argue that in software development, the first thing you should do is to remove overburden by establishing a pull process. This will cause problems and variation to surface. Once the new process has been stabilized, tackle variation by practicing continuous improvement and standardizing the work. You may also find Jim Womack’s e-letter on cadence helpful: http://www.leanuk.org/articles/jim_eletter_200801.pdf. It talks about creating a levelled workflow (heijunka) across the organization. I have found that even though upstream processes such as strategy and portfolio management often need to be improved too, software development is usually the right place to start. Only once we know how much work the development teams can pull and consume, the upstream processes can be adequately adjusted so that value flows smoothly through the entire system. Best regards, Roman

  6. I agree. Muri first. then Mura, then Muda. that is the wisdom handed down from the original thinkers of the toyota way. A little explanation may help here. Overburden is only one symptom of Muri. Possibly the most obvious. But the word really means "irrational". Until rationality is introduced, i.e. an empirical approach, based on fact and logic, expressed through standards, then there is no foundation for future improvement. So eliminating muri is the essential first step. This link might help here: http://www.chcanys.org/clientuploads/downloads/Clinical_resources/Leadership%20Articles/Toyotaleanproduction.pdf Thanks Richard Henderson

  7. yes you are right I agree. Muri first. then Mura, then Muda. that is the wisdom handed down from the original thinkers of the toyota way. A little explanation may help here. Overburden is only one symptom of Muri. Possibly the most obvious. But the word really means "irrational". Until rationality is introduced, i.e. an empirical approach, based on fact and logic, expressed through standards, then there is no foundation for future improvement. So eliminating muri is the essential first step. This link might help here: http://www.chcanys.org/clientuploads/downloads/Clinical_resources/Leadership%20Articles/Toyotaleanproduction.pdf Thanks Richard Henderson evden eve nakliyat evden eve nakliyat evden eve nakliyat

  8. Estetik Burun Estetiği Plastik cerrahi Plastik cerrah Estetik cerrahi Göğüs Estetiği Burun estetik Estetik burun evkur bayanlar Plastik cerrah burun estetiği estetik Göğüs büyütme Göğüs estetiği Göğüs dikleştirme Kulak estetiği Karın estetiği Göz kapağı esteği Yağ aldırma estetiği Kol germe Çene estetiği Yüz estetiği yanak estetiği jinekomasti Yağ Enjeksiyonları Yüz estetiği Yanak kaldırma yanak estetiği Alın Germe estetiği Yüz Germe Kaş Kaldırma Estetik Cerrahi Tedavinin Prensibi saç ekimi erkeklerde saç dökülmesi Saç Ekim Yöntemleri Dikişsiz saç ekimi ameliyatsız saç ekim yöntemleri Migren Migren Migren Ameliyatının Riskleri Göbek Estetiği Popo Estetiği Çin malı ucuz botox ve kollajenlere ve sıvı silikona dikkat Cilt Yenileme Güneşli günlerde cilt lekelerine dikkat Hastaların en çok sorduğu sorular Estetik ameliyatı öncesi ve sonrası İyileşme Dönemi Süresi Nasıl Geçirilmelidir Doğal Botox Botox Estetik Botox Estetik dikiş Liposuction cilt lekeleri Estetik burun ameliyatından sonra bazen burun düşmesi olurmu İdeal Kaş Şekli Nasıl Olmalı Kötü bir burun ameliyatı nasıl belli olur Süper modellerin yüzleri: Hepsinde ortak olan özellikler neler Estetik Video Burun estetiği hangi durumlarda yapılır Burun estetiği ameliyatı nasıl yapılıyor Hangi burun şeklinin daha iyi duracağına nasıl karar verilir Burun estetiği ameliyatından sonra hasta neler yaşar Burun estetiği zor bir ameliyat mı Botox preis Burun estetiğinin başarısız olduğu nasıl anlaşılır Plastik cerrah Burun estetiği ile ne tür düzeltmeler yapılabilir Burun estetiğinin sonucundan memnun kalınmazsa ne yapılabilir Burun estetiği ameliyatından sonra tampon konması şart mı Burun estetiğinin başarısında hangi faktörler önemlidir Meme büyütme yaptıran biri çocuk emzirebilir mi Göğüsleri büyütmek için ameliyat dışında yöntemler var mı Meme büyütme ameliyatından sonra iz kalır mı Meme büyütme ameliyatında meme nasıl büyütülür Meme büyütme ameliyatı hangi durumlarda yapılır Meme büyütmede kullanılan silikonun zararları var mı Meme büyütme zor bir ameliyat mı Meme büyütme sonrasında memede hissizlik olur mu Meme büyütme ameliyatından sonra hasta neler yaşar Meme büyütme ameliyatında sonuç beğenilmezse ne yapılabilir Meme küçültme ameliyatı sırasında hasta neler yaşar Meme küçültme ameliyatı hangi durumlarda yapılır Göğüsleri küçültmek için operasyon haricinde yöntemler var mı? Meme küçültme ameliyatında hangi teknikler uygulanır Meme küçültme yaptıran biri çocuk emzirebilir mi? Meme küçültme ameliyatı sonrasında memede hissizlik olur mu? Meme küçültme ameliyatı öncesinde hazırlık gerekiyor mu? Meme küçültme riskli bir ameliyat mı? Meme küçültme ameliyatından sonra iz kalır mı? Meme küçültme ameliyatından sonra meme yeniden büyüyebilir mi? Meme küçültme ameliyatını herkes yaptırabilir mi? Meme küçültme sonrasında hasta günlük hayatına ne zaman dönebilir? Liposuction ile vücudun hangi bölgelerinden yağ alınabilir? Liposuction nedir? Liposuction ameliyatı esnasında hasta neler yaşar? Liposuction'dan sonra tekrar yağlanma veya sarkma olur mu? Liposuction bir zayıflama yöntemi midir? Liposuction ameliyatında hangi teknikler kullanılır? Liposuction riskli bir ameliyat mı? Liposuction sonrasında iz veya deformasyon kalır mı? Liposuction operasyonu sonrasında neler yaşanır? Liposuction ameliyatını mutlaka plastik cerrah mı yapmalı? Plastic Surgery (English) Plastic Surgery of Nose (Rhinoplasty) Hair seeding without sewing Whom the operation of migraine is convenient for Skin Rejuvenate The principal of surgical treatment What determines the price of botox The wrong opinions about Botox that I heard the most Botox Applications Belly tightening surgery (Abdominoplasty) Endoscopic forehead streching and temporal lifting operation Eyebrows lifting endoscopic and hanger techniques Classical face streching surgery Belly tightening surgery (abdominoplaty) The ladle ear surgery (otoplasty) Arm Lift Surgery (brachioplasty) Breast Reduction Surgery (reduction mammaplasty) Breast augmentation surgery breast lifting astic surgery of breast lifting Cheek and eyebrow lifting surgeries Endos copic middle face surgery Endoscopic middle face surgery cheek lifting Jaw and cheekbone prosthesis Liposuction (fat extracting surgery) The breast growth of the men (gynecomastia) The eyelids (blepharoplasty) Plastic surgery of eyelids (blepharoplasty) Hip shaping The surgical treatment of alopecia Plastic Surgery (Germany) Nasenkorrektur (Rhinoplastik) Haare Anpflanzen ohne Nähen Für wen ist ein migrän operation geeignet Das Prinzip der chirurgische Behandlung Botox preise was bestimmt die botox preis Die Informationen über Botox Die Botox Anwendungen Die Bauchspannung Operation(Abdominoplasty) Hüfte Gestaltung Operationen Die Augenbraue Korrigierung(Hoch heben) Die Haarverpflanzung Methode Stirnspannung und die Schläfe hochheben Operationen(Front Lift) Klassiche Gesichtspannung Operation(Facelift) Hänge Ärmen(Arm Lift) Das Kinn Operation Liposuction (Fettabsaugen Operation) Das Kinn und der Backenknochen Protesie Die Brustvergrösserung bei den Männern(Gynecomastia) Endoskopic gesichtchirurgie das augenlid (Blepharoplasty) Die wange und wange hoccheben Operation Das Augenlid Operation(Blepharoplasty) Endoskopic wange hochheben

Exclusive Content

Mock Roles Not Object States

Nat Pryce and Steve Freeman talk about TDD using Mock Objects. Mock Objects improves the software design and makes the code more easier to maintain and adapt to changing requirements.

Gregor Hohpe on Conversation Patterns

In this interview, recorded at QCon London, Google's Gregor Hohpe talks about his new work on conversation patterns and the role conversations play in real-world communication scenarios.

Succeeding With Agile: A Guide To Transitioning

Mike Cohn talks about the transitioning process towards an agile organization, why the process is inherently difficult, and what it takes to see self-organization emerging.

Secure Programming with Static Analysis

Creating secure code requires more than just good intentions. Static source code analysis can be used to uncover the kinds of errors that lead directly to vulnerabilities. Brian Chess shows you how.

Developing Portlets using JSF, Ajax, and Seam (Part 1 of 3)

This article covers setting up a new project using JBoss Portlet Container and JBoss Portlet Bridge, configuring a JSF app to use JBoss Portlet Bridge, and JBoss Portlet Bridge capabilities.

John Lam About IronRuby

John Lam, Program Manager on the Dynamic Language Runtime team at Microsoft, talks about IronRuby, what it means to .NET supporters and how it has been received by the Ruby community.

Jerry Cuomo on Virtualization, Cloud Computing and WebSphere Virtual Enterprise

In this interview, Jerry Cuomo talks about Virtualization and Cloud Computing and what IBM is doing in this area with WebSphere Virtual Enterprise to help virtualize middleware and application stack.

Silverlight and Java Interoperability

Robert Bell, Microsoft, introduces interoperability scenarios for using Silverlight from Java and provides architectural guidance using sample code snippets.