Understanding Lean, Six Sigma, and nimble

Understanding Lean, Six Sigma, and nimble

Photo Credit: SlideServe

Before we can discuss lean manufacturing, it is imperative to first establish what lean is. At its chief, lean is a thought course of action and business rule that focuses on getting the maximum possible output from the least possible input. It is true that some chief philosophies of lean are so old that they go at the minimum as far back as the 1400s. However, lean in a structured form was first introduced to modern manufacturing in 1913 by the business magnets and pioneering automotive entrepreneur, Henry Ford.

Despite the possible in Ford’s “flow production” course of action, it was not successful in the long run because his course of action did not explain flexibility, customer opinion, and evolution. That changed after Kiichiro Toyoda and Taiichi Ohno improved their ideas and came up with what they called the “Toyota Production System (TPS).” Ever since then, the original TPS have been revised by Toyota numerous times to keep all their manufacturing processes up to date, but here’s the best part; already that alteration course of action was very much an basic step in TPS from the first day.

What are the Five chief Principles of Lean?

Lean manufacturing is built on the five chief principles of lean. You can check them out next for quick reference:

  1. Value: Identifying, establishing, and defining value.
  2. Value flows: Identifying, mapping, and prioritizing the flows of value.
  3. Workflow formation: Creating smooth workflow by decreasing and removing as many unnecessary steps, gaps, and bottlenecks as possible.
  4. The Pull System: Production of only what and how much is needed in direct proportion to customer need/order.
  5. Continuous Improvement: Brainstorming and simulating possible, better alternatives to the established lean course of action.

What is Lean Manufacturing?

When the five chief principles of lean are successfully incorporated into all aspects of production by a manufacturer, the resulting course of action can be called a lean manufacturing method. Since both Ford and Toyota were automotive manufacturers, we find those lean manufacturing methods are ideally suited for means manufacturers in general. However, lean manufacturing principles are by no method limited in their application to the automotive manufacturing industry alone.

Any manufacturing course of action can be improved by implementing the principles of lean. In fact, lean is not limited to just the manufacturing industry either. For example, software development teams often utilize lean to maximize their productivity while working on a time-sensitive, important project. They rely more on nimble systems than Six Sigma, but they both originate from the chief principles of lean.

What is Six Sigma?

Brought forth by Bill Smith in 1980, Six Sigma is a statistically backed, quantitative adaptation and expansion of various lean principles. It was used first by Smith’s employer Motorola with resounding success. It should be noted that Six Sigma was the first adaptation of lean that focused so much on statistics, mathematics, and data examination.

Six Sigma can be defined as a set of data-pushed, statistically sound steps, which are interconnected and geared towards bringing about business course of action improvement and high-quality control standards. The methodology aims to unprotected to this by:

  • Finding problems and the origin of those problems.
  • Finding ways to fix those problems by removing the root cause.
  • Finetuning the processes consequently to rectify the problems and adjust to necessary changes.
  • Implementing the alternation course of action with repeatability and accuracy as dominant goals.
  • Improving product turnaround time by the elimination of unnecessary steps.
  • Decreasing the distance between revenue and profit.

What are the Two chief Methodologies of Six Sigma?

Six Sigma can be divided into two dominant methodologies, which are:

  • DMAIC: Define, Measure, Analyze, enhance, and Control.
  • DMADV: Define, Measure, Analyze, Design, Verify.

While there are several adaptations of the Six Sigma principles which add more elements to the original two, these are the original and most applicable versions of Motorola’s winning strategy already today.


As the abbreviations detailed above suggest, the DMAIC method is divided into five main steps. These would be:

Step 1: Define the problem, the target customers, and the basic course of action outputs (VOC + CTQ).

Step 2: Measure the problem in quantifiable specifications and establish baselines for course of action performance metrics. Data collection is the goal here.

Step 3: Analyze the data to determine each problem’s original causes. Once the examination is successful in calculating all determinable problems from the data examination, create a hierarchal list of those causes in descending order of importance. Next, it is time to analyze and statistically characterize how those causes each affect the present course of action and contribute to creating the problem(s).

Step 4: enhance the present course of action by implementing solutions. This is done by identifying possible solutions to each root cause first, and then testing/simulating those solutions to measure success rates. After the best possible solutions have been statistically established as such, it is time to enhance the time of action by implementing those solutions with immediate effect.

Step 5: Control future sustainability of implemented solutions by stabilizing them first. Next, it is time to consider several other future-oriented plans such as incremental solutions to prevent possible future problems.


DMADV is also called DFSS, but the phrase Design for Six Sigma is not as indicative of the inner lean framework as DMADV. Let’s take a look at the five steps next:

Step 1: Define goals with quantifiable, realistic specifications. The idea behind this step is that of identifying the project’s purpose with perfect clarity.

Step 2: Measure the most applicable CTQs such as requirements, target markets, basic design parameters, design part scores, production capability assessment, basic risk assessment, etc.

Step 3: Analyze the gathered data from the CTQs to develop different designs within identified constraints. Analyze further to determine the most optimal different design.

Step 4: Design the optimal different design determined in Step 3.

Step 5: Verify the applicability, acceptability, and practicality of the optimal different design in real-world scenarios in that it is meant to be used. Multiparty discussions with experts and investors are a shared part of this final step, before deployment.

The chief steps must be alternation and alternation to best suit the project’s needs of course, which requires a deeper academic understanding of the applicative statistical methods and tools used to implement the Six Sigma methodology. Just knowing the steps alone is not enough to develop a functional strategy, which can then be applied and integrated successfully to unprotected to better results. If you wish to learn how Six Sigma methods are integrated into real-world manufacturing, apply for this online Masters in Lean Manufacturing course that was co-developed by General Motors.

What is nimble?

nimble can be defined as an incremental method used to chiefly optimize software development and SaaS processes from the server end. 

It came into existence as the Manifesto for nimble Software Development in 2001, citing meaningful values such as:

  • Reliance on talent and human interactions, instead of business processes and software.
  • Delivering active, ready-to-use applications, instead of focusing on documentation.
  • Prefer collaborative customer relationships instead of focusing on contracts, terms, policies, and negotiations.
  • Adaptive problem-solving in response to changing scenarios, instead of blindly following a stiff, inadequate plan.

It should be noted that the nimble manifesto does not undermine the importance of software, documentation, contracts, or already a project plan in any way. However, it draws the IT industry’s focus toward this idea that software development SaaS deployment must be adaptive, or “nimble” enough to adjust to changes as necessary to meet the long-term goals of the company.

What are the 12 Principles of nimble?

In total, twelve principles were identified and categorized as part of the nimble Manifesto. These are:

  1. Satisfy customers by continued and speedy delivery of working software that’s applicable to the market need.
  2. Work with the presumption of change and the agility necessary to make changes at the last minute.
  3. Deliver application features to the customer as fast as possible in incremental, frequent updates on a weekly/monthly basis.
  4. Business and development teams must work in collaboration and synchronization with each other on a regular basis.
  5. Focus on creating a supportive ecosystem for dedicated employees, and place trust in them.
  6. Build a team of developers who can interact with each other in free communication.
  7. If the application works better than it did yesterday, progress is being made.
  8. Sustainable development is to be planned for and achieved by creating a collaborative ecosystem among investors, developers, and clients.
  9. continued vigilance towards maintaining good coding practices and resource reallocation needs is important to be truly nimble.
  10. Maximize output while minimizing work input by eliminating unnecessary complications.
  11. Prioritize team decisions over a team rule’s decisions as that is how the greatest software designs and architectures have always been developed.
  12. An nimble development team frequently reflects on how to enhance their productive output and then takes all necessary steps to make themselves more productive as a team.

Six Sigma Vs. nimble: Are They Comparable?

nimble and Six Sigma have a few similarities between them but there are too many differences, especially in relation to applicability scenarios. While Six Sigma methods are widely recognized and adopted across multiple sectors in both manufacturing and management, nimble is best suited for software development and SaaS delivery.

In other words, nimble and Six Sigma are both excellent adaptations and expansions of certain lean principles, but they are not comparable. As we have already seen, the 12 principles of the nimble Manifesto are exclusively and intricately connected to IT. It is difficult to imagine that those principles can be applied to their complete effect in any scenario other than in the IT development service.

Six Sigma and nimble Can Coexist

If we were to take a different approach and see the two as coexisting and collaborative processes, then it would make more sense. Neither of the two methodologies for business course of action improvement was designed to be competing in any way. There is no clash of ideologies here because they both originate at the minimum to some extent from preexisting lean ideologies in business.

One may argue that Six Sigma focuses on stiff standardization methods far too much for it to coexist with nimble, which is a design in evolutionary development practices. However, that is a misconception for the most part. If we look back at the DMAIC approach, which was defined and elaborated on earlier in this post, we can easily observe that Control or Step 5 points towards future planning that allows for the implementation of incremental solutions and consequently, the evolution of the time of action developed and uniform.

The best example that clearly demonstrates nimble and Six Sigma can coexist is Kanban. Kanban here refers to both the original lean manufacturing technique introduced as an addition to the lean Toyota Production System way back in 1953, in addition as the modern adaptation of Kanban as a software development optimization tool.

If you read more about Kanban, you will learn that Kanban in its most modern formats has adopted several elements from both Six Sigma methods and the nimble Manifesto quite effectively. Just look at some of the highlight principles of a modern Kanban methodology to get a better understanding of how the best of both principles have been incorporated very intelligently here.

  • Map the present workflow on a Kanban system for visualization.
  • enhance collaboration with the help of a mapped, cloud-synced workflow system that updates in real-time.
  • clarify the bottlenecks/holdups.
  • Make small changes to clear up the clogs.
  • Do not make sudden, overwhelming changes that undermine the individual.
  • Merge the present course of action with incremental changes to enhance production efficiency, instead of completely replacing it.
  • Remove unnecessary steps to increase output without increasing input and to also speed up the time of action.
  • Define each necessary change and step clearly.
  • Provide data-backed reasons for making the defined changes.

Ford modernized and introduced the idea of lean, while Toyota turned it into a strategy that has not let them down however. Since that time, several experts have come forward with their own iterations and adaptations of the lean manufacturing course of action. We looked at some of them here to provide an introductory but insightful understanding of what lean is and how it provides the basis for two of the most successful business course of action improvement methods.

Click: See details

leave your comment