8-wastes-of-lean

8 Wastes of Lean

The “8 Wastes of Lean” encompass eight categories of non-value-adding activities that lead to inefficiency. Categories like defects, overproduction, waiting, and more contribute to waste. By identifying and addressing these wastes, organizations can improve efficiency, product quality, and resource utilization.

These comprise:

  1. Defects: Flaws or errors requiring rework
  2. Overproduction: Producing more than needed
  3. Waiting: Delays causing idle time
  4. Non-Utilized Talent: Underutilization of employee skills
  5. Transportation: Unnecessary movement of goods
  6. Inventory: Excess materials or products
  7. Motion: Unnecessary physical movements
  8. Extra-Processing: Performing tasks beyond requirement

1. Overproduction

Definition: Overproduction refers to the production of goods or services in excess of what is needed to meet customer demand or internal requirements. It is often considered the most significant waste in Lean thinking because it can lead to other forms of waste downstream.

Examples:

  • Manufacturing more products than customers will purchase, resulting in excess inventory.
  • Printing more documents than required, leading to wasted paper and storage space.
  • Writing code for software features that are not needed or requested, increasing development time and complexity.

How to Address It:

  • Implement a pull production system where items are produced only when there is a demand.
  • Use Just-in-Time (JIT) manufacturing principles to align production with customer orders.
  • Monitor demand closely and adjust production accordingly.

2. Inventory

Definition: Inventory waste includes excessive storage of raw materials, work-in-progress (WIP), or finished goods. Excess inventory ties up capital and space and can lead to obsolescence or damage.

Examples:

  • Stockpiling excessive raw materials that may never be used.
  • Accumulating large quantities of unfinished products in a manufacturing process.
  • Maintaining high levels of finished goods inventory that may become outdated.

How to Address It:

  • Implement inventory control systems to track and manage stock levels.
  • Utilize Kanban systems or visual signals to trigger replenishment based on actual consumption.
  • Implement a first-in, first-out (FIFO) inventory rotation system.

3. Waiting

Definition: Waiting waste occurs when resources, including people or equipment, are idle due to delays in a process. This downtime can result in lost productivity and increased lead times.

Examples:

  • Employees waiting for materials or information to proceed with their tasks.
  • Machines sitting idle while waiting for the previous process to finish.
  • Customers waiting in line for service.

How to Address It:

  • Analyze processes to identify bottlenecks or areas of delay.
  • Streamline workflows to reduce waiting times.
  • Implement work balancing to distribute tasks evenly and eliminate idle time.

4. Motion

Definition: Motion waste relates to unnecessary movement or transportation of people, materials, or equipment. Excessive motion can lead to fatigue, increased risk of accidents, and reduced efficiency.

Examples:

  • Employees walking long distances to access tools or supplies.
  • Frequent material handling and transfers between workstations.
  • Repetitive and non-ergonomic movements during tasks.

How to Address It:

  • Reorganize workspaces for better layout and accessibility.
  • Implement 5S workplace organization principles to reduce unnecessary motion.
  • Invest in ergonomic equipment and tools to minimize physical strain.

5. Transportation

Definition: Transportation waste involves the unnecessary movement of materials or products from one location to another. This waste not only consumes time and resources but also increases the risk of damage or loss.

Examples:

  • Shipping raw materials from a distant supplier when local options are available.
  • Moving products between warehouses or distribution centers that are not strategically located.
  • Transferring files or documents physically instead of digitally.

How to Address It:

  • Optimize supply chain logistics to minimize transportation distances.
  • Consolidate shipments and deliveries to reduce the number of movements.
  • Use digital communication and document sharing to eliminate unnecessary physical transportation.

6. Overprocessing

Definition: Overprocessing waste occurs when more work or processing is performed on a product or service than is required by the customer or specified by quality standards. This can include extra steps, inspections, or features that do not add value.

Examples:

  • Performing redundant quality checks or inspections.
  • Including features in a product that customers do not need or want.
  • Excessive documentation or paperwork for simple processes.

How to Address It:

  • Conduct value stream mapping to identify non-value-added steps.
  • Standardize processes to eliminate unnecessary activities.
  • Focus on meeting customer requirements without adding unnecessary complexity.

7. Defects

Definition: Defects waste encompasses any errors, mistakes, or defects in a product or service that require rework, repair, or additional resources to correct. Defects waste can lead to customer dissatisfaction and increased costs.

Examples:

  • Manufacturing products with defects that require rework or scrap.
  • Errors in data entry or documentation that necessitate correction.
  • Mistakes in software code that result in bugs or glitches.

How to Address It:

  • Implement robust quality control processes and error prevention measures.
  • Conduct root cause analysis to identify the sources of defects and address them.
  • Focus on error-proofing techniques to prevent defects at the source.

8. Underutilized Employee Skills

Definition: Underutilized employee skills waste occurs when employees’ skills, knowledge, or creativity are not fully leveraged or engaged in their roles. This waste can result in reduced morale and missed opportunities for improvement.

Examples:

  • Assigning employees to tasks that do not align with their expertise.
  • Failing to tap into employees’ problem-solving abilities or innovative ideas.
  • Not providing opportunities for skill development and growth.

How to Address It:

  • Match employees’ skills and interests with appropriate tasks and responsibilities.
  • Encourage and empower employees to participate in process improvement initiatives.
  • Invest in training and development programs to enhance employee skills and capabilities.

Conclusion

The 8 Wastes of Lean provide a structured framework for identifying and eliminating inefficiencies and non-value-added activities in processes across various industries. By recognizing and addressing these wastes, organizations can streamline operations, reduce costs, enhance product and service quality, and ultimately deliver greater value to customers and stakeholders. Lean practitioners continuously strive to identify and eliminate these wastes as part of their ongoing pursuit of operational excellence and continuous improvement.

Key Highlights of the 8 Wastes of Lean:

  • Defects: Addressing flaws or errors early prevents rework and enhances product quality.
  • Overproduction: Producing more than demand leads to excess inventory and waste.
  • Waiting: Delays in processes result in idle time and decreased efficiency.
  • Non-Utilized Talent: Unlocking employee skills boosts productivity and job satisfaction.
  • Transportation: Minimizing unnecessary movement reduces time and cost.
  • Inventory: Maintaining optimal inventory levels prevents overstocking and waste.
  • Motion: Eliminating unnecessary physical movement enhances workflow.
  • Extra-Processing: Avoiding tasks beyond requirements saves time and resources.
Related FrameworksDescriptionWhen to Apply
Value Stream Mapping (VSM)– Value Stream Mapping (VSM) is a visual tool used in Lean manufacturing to analyze, design, and improve the flow of materials and information required to bring a product or service to a customer. It involves mapping the current state and desired future state of the entire value stream, identifying waste, bottlenecks, and opportunities for improvement. VSM helps organizations visualize and understand the end-to-end process, enabling them to streamline operations, reduce lead times, and enhance overall efficiency.– When analyzing and improving processes, workflows, or value streams to identify and eliminate waste, inefficiencies, and bottlenecks. – In situations where visualizing the end-to-end process and understanding how value is created and delivered to customers is essential for process optimization and continuous improvement efforts.
5S Methodology– The 5S Methodology is a systematic approach used to organize, standardize, and maintain a clean and efficient work environment. It consists of five principles: Sort, Set in Order, Shine, Standardize, and Sustain. 5S aims to improve workplace organization, safety, and productivity by eliminating clutter, optimizing workflows, and promoting discipline and teamwork. By implementing 5S, organizations can create a visual workplace where everything has a designated place, waste is minimized, and efficiency is maximized.– When organizing workspaces, optimizing workflows, or implementing cleanliness and safety initiatives to eliminate waste and improve productivity. – In environments where maintaining a clean, organized, and efficient workplace is essential for enhancing operational performance and employee satisfaction.
Kaizen (Continuous Improvement)– Kaizen, which means “continuous improvement” in Japanese, is a philosophy and methodology focused on making incremental and continuous improvements to processes, products, or services. It involves empowering employees at all levels to identify problems, suggest solutions, and implement changes systematically. Kaizen emphasizes small, incremental changes over time, rather than large-scale transformations, to achieve continuous improvement and foster a culture of learning and innovation. By embracing Kaizen, organizations can unlock the potential of their workforce, improve quality, and drive sustainable growth.– When fostering a culture of continuous improvement, encouraging employee involvement, and implementing small, incremental changes to eliminate waste and optimize processes. – In environments where empowering employees to identify and solve problems, experiment with new ideas, and drive improvements is essential for achieving operational excellence and maintaining a competitive edge.
PDCA Cycle (Plan-Do-Check-Act)– The PDCA Cycle, also known as the Deming Cycle or Plan-Do-Check-Act Cycle, is a problem-solving and continuous improvement methodology. It consists of four stages: Plan (identify a problem and plan a change), Do (implement the change on a small scale), Check (evaluate the results and compare them to the expected outcomes), and Act (standardize the successful changes and implement them on a larger scale). The PDCA Cycle provides a structured approach to problem-solving, experimentation, and learning, enabling organizations to address issues systematically, drive improvements, and achieve sustainable results.– When addressing problems, implementing changes, or driving continuous improvement initiatives to eliminate waste and enhance operational efficiency. – In situations where a structured problem-solving methodology is needed to identify root causes, test solutions, and monitor results systematically.
Total Productive Maintenance (TPM)– Total Productive Maintenance (TPM) is a comprehensive approach to equipment maintenance and improvement that aims to maximize the effectiveness of production assets. TPM focuses on proactive maintenance, employee involvement, and continuous improvement to achieve zero breakdowns, zero defects, and zero accidents. It involves various practices, such as autonomous maintenance, planned maintenance, and focused improvement activities. By implementing TPM, organizations can reduce downtime, improve equipment reliability, and optimize overall equipment effectiveness (OEE).– When optimizing equipment reliability, minimizing downtime, or improving overall equipment effectiveness (OEE) to eliminate waste and enhance productivity. – In environments where proactive maintenance practices and employee involvement are essential for achieving operational excellence and maximizing the return on investment in production assets.
Standard Work– Standard Work is a Lean manufacturing principle that involves establishing documented and standardized procedures for performing tasks or processes. It defines the best-known sequence of steps, methods, and performance expectations based on current best practices and employee input. Standard Work aims to eliminate variation, reduce waste, and ensure consistent quality and efficiency in operations. By establishing and following standard work procedures, organizations can improve productivity, reduce errors, and create a foundation for continuous improvement.– When establishing best practices, reducing variation, or improving consistency and efficiency in performing tasks or processes to eliminate waste and enhance productivity. – In situations where standardizing work procedures and performance expectations is essential for achieving consistent quality, reducing errors, and facilitating continuous improvement efforts.
Single-Minute Exchange of Die (SMED)– Single-Minute Exchange of Die (SMED) is a Lean manufacturing technique used to reduce setup or changeover times in production processes. It involves analyzing and streamlining the steps required to switch from producing one product to another. By separating internal setup activities from external setup activities, simplifying tasks, and converting setup tasks to be performed while the equipment is running, SMED aims to minimize downtime and increase flexibility in production. SMED enables organizations to respond quickly to changing customer demands, reduce inventory levels, and improve overall equipment effectiveness (OEE).– When reducing setup or changeover times, increasing production flexibility, or improving overall equipment effectiveness (OEE) to eliminate waste and enhance operational efficiency. – In environments where quick setup changes and production flexibility are essential for responding to changing customer demands and market conditions effectively.
Andon System– The Andon System is a visual management tool used in Lean manufacturing to signal production status, quality issues, or process abnormalities in real-time. It typically consists of visual indicators, such as lights or displays, located at workstations or production lines. When an issue occurs, workers can activate the Andon System to stop production, alert supervisors, and initiate problem-solving efforts. The Andon System promotes transparency, accountability, and rapid response to problems, enabling organizations to address issues promptly and prevent defects or disruptions from reaching customers.– When monitoring production status, detecting quality issues, or responding to process abnormalities in real-time to prevent defects and disruptions. – In situations where promoting transparency, accountability, and rapid problem-solving is essential for achieving operational excellence and maintaining product quality and customer satisfaction.
Jidoka (Autonomation)– Jidoka, or autonomation, is a Lean manufacturing principle that combines automation with human intelligence to create self-monitoring and self-regulating production systems. It involves empowering machines and operators to detect abnormalities, stop production, and alert personnel when an issue occurs. Jidoka aims to build quality into the production process, prevent defects, and ensure that problems are addressed at the source. By implementing Jidoka, organizations can achieve higher quality, reduce waste, and improve efficiency and responsiveness in production.– When integrating automation with human intelligence to build quality into the production process and prevent defects from reaching customers. – In environments where empowering machines and operators to detect abnormalities and stop production autonomously is essential for achieving operational excellence and ensuring product quality and reliability.
Kanban System– The Kanban System is a visual scheduling method used in Lean manufacturing to control and manage workflow. It involves using visual cues, such as cards or boards, to signal the need for production or replenishment of items at each stage of the process. Kanban enables organizations to balance supply with demand, minimize inventory levels, and optimize production flow. By implementing Kanban, organizations can improve efficiency, reduce lead times, and enhance responsiveness to customer needs. Kanban also facilitates continuous improvement by highlighting bottlenecks and inefficiencies in the production process.– When controlling and managing workflow, balancing supply with demand, or optimizing production flow to minimize waste and improve efficiency. – In situations where visualizing workflow, reducing inventory levels, and enhancing responsiveness to customer demands are essential for achieving operational excellence and maintaining competitiveness.
Gemba Walk– Gemba Walk is a Lean management practice that involves leaders or managers going to the “gemba,” or the place where work is done, to observe operations, engage with employees, and identify opportunities for improvement firsthand. It emphasizes the importance of direct observation, active listening, and frontline engagement in understanding processes, identifying waste, and driving continuous improvement. Gemba Walks enable leaders to gain insights into daily operations, foster collaboration, and support employee development and problem-solving efforts.– When gaining insights into daily operations, engaging with employees, and identifying opportunities for improvement firsthand to drive continuous improvement initiatives. – In environments where fostering a culture of transparency, collaboration, and continuous improvement is essential for achieving operational excellence and organizational success.

Connected Agile & Lean Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

AgileSHIFT

AgileSHIFT
AgileSHIFT is a framework that prepares individuals for transformational change by creating a culture of agility.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Program Management

agile-program-management
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Agile Leadership

agile-leadership
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles. 

Andon System

andon-system
The andon system alerts managerial, maintenance, or other staff of a production process problem. The alert itself can be activated manually with a button or pull cord, but it can also be activated automatically by production equipment. Most Andon boards utilize three colored lights similar to a traffic signal: green (no errors), yellow or amber (problem identified, or quality check needed), and red (production stopped due to unidentified issue).

Bimodal Portfolio Management

bimodal-portfolio-management
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.

Business Innovation Matrix

business-innovation
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Constructive Disruption

constructive-disruption
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

Gemba Walk

gemba-walk
A Gemba Walk is a fundamental component of lean management. It describes the personal observation of work to learn more about it. Gemba is a Japanese word that loosely translates as “the real place”, or in business, “the place where value is created”. The Gemba Walk as a concept was created by Taiichi Ohno, the father of the Toyota Production System of lean manufacturing. Ohno wanted to encourage management executives to leave their offices and see where the real work happened. This, he hoped, would build relationships between employees with vastly different skillsets and build trust.

GIST Planning

gist-planning
GIST Planning is a relatively easy and lightweight agile approach to product planning that favors autonomous working. GIST Planning is a lean and agile methodology that was created by former Google product manager Itamar Gilad. GIST Planning seeks to address this situation by creating lightweight plans that are responsive and adaptable to change. GIST Planning also improves team velocity, autonomy, and alignment by reducing the pervasive influence of management. It consists of four blocks: goals, ideas, step-projects, and tasks.

ICE Scoring

ice-scoring-model
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.

Innovation Funnel

innovation-funnel
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.

Innovation Matrix

types-of-innovation
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).

Innovation Theory

innovation-theory
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Minimum Viable Product

minimum-viable-product
As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.

Leaner MVP

leaner-mvp
A leaner MVP is the evolution of the MPV approach. Where the market risk is validated before anything else

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Jidoka

jidoka
Jidoka was first used in 1896 by Sakichi Toyoda, who invented a textile loom that would stop automatically when it encountered a defective thread. Jidoka is a Japanese term used in lean manufacturing. The term describes a scenario where machines cease operating without human intervention when a problem or defect is discovered.

PDCA Cycle

pdca-cycle
The PDCA (Plan-Do-Check-Act) cycle was first proposed by American physicist and engineer Walter A. Shewhart in the 1920s. The PDCA cycle is a continuous process and product improvement method and an essential component of the lean manufacturing philosophy.

Rational Unified Process

rational-unified-process
Rational unified process (RUP) is an agile software development methodology that breaks the project life cycle down into four distinct phases.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Retrospective Analysis

retrospective-analysis
Retrospective analyses are held after a project to determine what worked well and what did not. They are also conducted at the end of an iteration in Agile project management. Agile practitioners call these meetings retrospectives or retros. They are an effective way to check the pulse of a project team, reflect on the work performed to date, and reach a consensus on how to tackle the next sprint cycle. These are the five stages of a retrospective analysis for effective Agile project management: set the stage, gather the data, generate insights, decide on the next steps, and close the retrospective.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

SMED

smed
The SMED (single minute exchange of die) method is a lean production framework to reduce waste and increase production efficiency. The SMED method is a framework for reducing the time associated with completing an equipment changeover.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrumban

scrumban
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Six Sigma

six-sigma
Six Sigma is a data-driven approach and methodology for eliminating errors or defects in a product, service, or process. Six Sigma was developed by Motorola as a management approach based on quality fundamentals in the early 1980s. A decade later, it was popularized by General Electric who estimated that the methodology saved them $12 billion in the first five years of operation.

Stretch Objectives

stretch-objectives
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.

Toyota Production System

toyota-production-system
The Toyota Production System (TPS) is an early form of lean manufacturing created by auto-manufacturer Toyota. Created by the Toyota Motor Corporation in the 1940s and 50s, the Toyota Production System seeks to manufacture vehicles ordered by customers most quickly and efficiently possible.

Total Quality Management

total-quality-management
The Total Quality Management (TQM) framework is a technique based on the premise that employees continuously work on their ability to provide value to customers. Importantly, the word “total” means that all employees are involved in the process – regardless of whether they work in development, production, or fulfillment.

Waterfall

waterfall-model
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework. 

Read Also: Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Read Next: Agile Methodology, Lean Methodology, Agile Project Management, Scrum, Kanban, Six Sigma.

Main Guides:

Main Case Studies:

Scroll to Top

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

FourWeekMBA