seiso

Seiso

Seiso, part of the 5S methodology, involves cleaning and inspection to ensure a clean, organized workspace. It enhances efficiency, safety, and equipment performance while facing challenges of sustainability and resource allocation. It’s applied in various sectors like manufacturing and healthcare.

Introduction/Definition

Seiso (清掃) is a Japanese term that translates to “cleaning” or “cleanliness” in English. However, its meaning transcends the surface-level act of cleaning. Seiso represents a holistic approach to cleanliness and organization, emphasizing the importance of thorough cleaning, maintenance, and organization to create a harmonious and efficient environment. It is deeply ingrained in Japanese culture and is often practiced in workplaces, homes, and public spaces.

What is Seiso?

Seiso, a Japanese term meaning “clean” or “shine,” is the third step in the 5S methodology. It focuses on maintaining a clean and tidy workplace by thoroughly cleaning all work areas, equipment, and tools. Seiso goes beyond just cleanliness; it aims to create an environment where cleanliness is maintained as part of the daily routine and ingrained in the organizational culture.

Key Characteristics of Seiso

  • Thorough Cleaning: Involves deep cleaning of the workplace to remove dirt, dust, and debris.
  • Inspection: Uses cleaning as an opportunity to inspect equipment and identify potential issues.
  • Routine Maintenance: Integrates cleaning into the daily routine to ensure ongoing cleanliness.
  • Employee Involvement: Engages all employees in maintaining cleanliness.

Importance of Understanding Seiso

Understanding and implementing Seiso is crucial for improving workplace safety, enhancing productivity, and fostering a culture of discipline and pride in the workplace.

Improved Workplace Safety

  • Hazard Reduction: Eliminates potential hazards caused by dirt, dust, and clutter.
  • Accident Prevention: Reduces the risk of accidents and injuries through a clean environment.

Enhanced Productivity

  • Efficient Operations: Ensures equipment and tools are in good working condition, reducing downtime.
  • Organized Workspace: Promotes an organized and efficient workspace, allowing employees to work more effectively.

Fostering Discipline

  • Routine Practices: Encourages disciplined routine cleaning and maintenance.
  • Employee Pride: Instills a sense of pride and ownership among employees in maintaining their work areas.

Components of Seiso

Seiso involves several key components that contribute to its effectiveness in maintaining cleanliness and organization in the workplace.

1. Thorough Cleaning

  • Deep Cleaning: Conducts deep cleaning of all work areas, including floors, equipment, and tools.
  • Surface Cleaning: Regular cleaning of surfaces to remove dust, dirt, and debris.

2. Inspection and Maintenance

  • Equipment Inspection: Inspects equipment during the cleaning process to identify wear and tear or potential issues.
  • Preventive Maintenance: Performs preventive maintenance to keep equipment in optimal condition.

3. Daily Cleaning Routines

  • Routine Tasks: Establishes daily cleaning routines to ensure ongoing cleanliness.
  • Assigned Responsibilities: Assigns specific cleaning tasks to employees to maintain accountability.

4. Cleaning Supplies and Equipment

  • Adequate Supplies: Ensures the availability of adequate cleaning supplies and equipment.
  • Proper Tools: Provides the proper tools and materials needed for effective cleaning.

5. Employee Training

  • Cleaning Techniques: Trains employees on proper cleaning techniques and procedures.
  • Safety Training: Educates employees on safety practices related to cleaning and maintenance.

Implementation Methods for Seiso

Several methods can be used to implement Seiso effectively, each offering different strategies and tools.

1. Cleaning Schedules

  • Daily Schedules: Establishes daily cleaning schedules for regular maintenance.
  • Deep Cleaning: Schedules periodic deep cleaning sessions to address thorough cleaning needs.

2. Cleaning Checklists

  • Task Lists: Develops detailed checklists for cleaning tasks to ensure thoroughness.
  • Inspection Points: Includes inspection points in checklists to identify potential issues.

3. Visual Management

  • Visual Cues: Uses visual cues such as color coding and labels to identify cleaning areas and tools.
  • Cleanliness Standards: Displays cleanliness standards and expectations in visible locations.

4. Employee Involvement

  • Team Efforts: Encourages team efforts and collaboration in maintaining cleanliness.
  • Ownership: Promotes ownership of specific areas to ensure individual accountability.

5. Regular Audits and Inspections

  • Routine Audits: Conducts regular audits and inspections to ensure adherence to Seiso standards.
  • Feedback Mechanisms: Establishes mechanisms for providing feedback and addressing issues.

Benefits of Seiso

Implementing Seiso offers numerous benefits, including increased safety, enhanced productivity, and a positive work environment.

Increased Safety

  • Hazard Reduction: Reduces hazards such as slips, trips, and falls by maintaining a clean workspace.
  • Early Detection: Identifies potential issues early through regular inspection during cleaning.

Enhanced Productivity

  • Efficient Operations: Keeps equipment and tools in good working condition, reducing downtime.
  • Organized Workspace: Promotes an organized and efficient workspace, allowing employees to work more effectively.

Positive Work Environment

  • Employee Morale: Boosts employee morale by creating a clean and pleasant work environment.
  • Professional Image: Enhances the company’s professional image for visitors and clients.

Cost Savings

  • Maintenance Costs: Reduces maintenance costs by keeping equipment in optimal condition.
  • Accident Costs: Lowers costs associated with workplace accidents and injuries.

Challenges of Seiso

Despite its benefits, implementing Seiso presents several challenges that need to be managed for successful implementation.

Sustaining Motivation

  • Employee Engagement: Maintaining employee engagement and motivation for regular cleaning tasks.
  • Routine Fatigue: Overcoming fatigue or complacency with routine practices.

Resource Allocation

  • Adequate Supplies: Ensuring the availability of adequate cleaning supplies and equipment.
  • Time Management: Allocating sufficient time for thorough cleaning without disrupting operations.

Consistency

  • Standardization: Ensuring consistent application of Seiso standards across all areas.
  • Regular Audits: Conducting regular audits to maintain consistency and identify improvement opportunities.

Training and Education

  • Continuous Training: Providing continuous education and training to reinforce Seiso principles.
  • Skill Development: Ensuring employees have the skills and knowledge to perform cleaning tasks effectively.

Best Practices for Seiso

Implementing best practices can help effectively manage and overcome challenges, maximizing the benefits of Seiso.

Engage Employees

  • Involvement: Actively involve employees in Seiso activities and decision-making processes.
  • Feedback: Encourage and value employee feedback to enhance practices.

Provide Continuous Training

  • Regular Training: Offer regular training sessions to reinforce Seiso principles.
  • Skill Development: Focus on developing skills necessary to perform cleaning and maintenance tasks.

Conduct Regular Audits

  • Routine Checks: Conduct routine checks and audits to ensure adherence to Seiso standards.
  • Action Plans: Develop and implement action plans based on audit findings.

Use Visual Management

  • Visual Controls: Implement visual controls to reinforce and monitor Seiso practices.
  • Clear Signage: Use clear and consistent signage to guide employees and maintain organization.

Foster a Culture of Continuous Improvement

  • Kaizen Mindset: Promote a Kaizen mindset focused on continuous improvement.
  • Employee Suggestions: Encourage employees to contribute ideas for improving workplace cleanliness and organization.

Recognize and Reward

  • Incentives: Implement incentive programs to reward adherence to Seiso practices.
  • Recognition: Regularly recognize and celebrate achievements in maintaining high standards.

Leadership Commitment

  • Management Involvement: Ensure active involvement and support from management.
  • Role Modeling: Leaders should model the behaviors and practices they expect from employees.

Future Trends in Seiso

Several trends are likely to shape the future of Seiso and its applications in workplace organization and efficiency.

Digital Transformation

  • Digital Tools: Increasing use of digital tools and software to monitor and sustain Seiso practices.
  • Data Analytics: Leveraging data analytics to identify trends and optimize practices.

Integration with Lean and Agile

  • Lean Methodologies: Further integration with lean methodologies to enhance efficiency and eliminate waste.
  • Agile Practices: Applying agile practices to make the Seiso process more flexible and adaptive.

Enhanced Training and Education

  • E-Learning: Expanding e-learning platforms to provide accessible and flexible training.
  • Virtual Reality: Utilizing virtual reality for immersive training experiences on Seiso practices.

Sustainability and Environmental Focus

  • Green Practices: Integrating sustainability and environmental considerations into Seiso practices.
  • Circular Economy: Emphasizing the circular economy by reusing and repurposing items where possible.

Global Standardization

  • International Standards: Developing and adopting international standards for Seiso and 5S practices.
  • Cross-Cultural Adaptation: Adapting Seiso principles to different cultural contexts for global applicability.

Use Cases and Examples

To better understand how Seiso is applied in practical scenarios, let’s explore some real-world use cases and examples:

1. Workplace Organization

In Japanese workplaces, Seiso is commonly practiced to maintain clean and efficient workspaces. Employees are responsible for cleaning their own workstations and shared areas.

Example: In an automotive manufacturing plant in Japan, employees regularly clean their workstations, tools, and machinery to prevent dust and debris buildup. This practice ensures the efficient operation of equipment and reduces the risk of defects.

2. Public Transportation

Japanese public transportation systems, including trains and buses, adhere to Seiso principles to provide a clean and comfortable experience for passengers.

Example: Japanese train stations have dedicated staff responsible for cleaning platforms, train cars, and station facilities throughout the day. This commitment to cleanliness contributes to a pleasant commuting experience.

3. Healthcare Settings

In Japanese healthcare facilities, Seiso practices are applied to ensure clean and sterile environments for patients and healthcare professionals.

Example: In a Japanese hospital, strict Seiso protocols are followed in surgical suites. This includes thorough cleaning and sterilization of surgical equipment and maintaining impeccable cleanliness to reduce the risk of infections.

4. Home Organization

Seiso extends to Japanese homes, where individuals practice regular cleaning and organization to create comfortable living spaces.

Example: In a typical Japanese home, daily cleaning routines include dusting, vacuuming, and tidying up. This not only keeps the home clean but also contributes to a sense of order and well-being.

5. Hospitality Industry

Japanese hotels and traditional ryokans adhere to Seiso principles to provide guests with clean and welcoming accommodations.

Example: In a traditional Japanese ryokan, guest rooms are meticulously cleaned and prepared before guests arrive. This attention to cleanliness and detail contributes to the overall guest experience.

6. Educational Settings

Seiso is applied in educational settings to create clean and organized learning environments for students.

Example: In a Japanese elementary school, students and teachers work together to maintain a clean and organized classroom. This practice instills a sense of responsibility and discipline in students.

Key Highlights of Seiso (Shine) in 5S Methodology:

  • Clean Workspace: Seiso emphasizes the importance of maintaining a clean and organized workspace free from dirt, debris, and clutter.
  • Regular Inspection: Routine inspections help identify defects, abnormalities, and hazards, allowing for prompt corrective actions.
  • Visual Appeal: The practice enhances the visual appeal of the workplace, creating a positive and inviting atmosphere.
  • Preventive Maintenance: Early detection of issues through inspection prevents equipment breakdowns and disruptions.
  • Safety Priority: Seiso contributes to a safer work environment by eliminating potential hazards and reducing the risk of accidents.
  • Efficiency Boost: Clean and organized tools and equipment lead to improved work efficiency and productivity.
  • Equipment Longevity: Proper maintenance extends the lifespan of equipment, reducing the need for frequent replacements.
  • Employee Morale: A clean and well-organized workspace boosts employee morale and engagement.
  • Commitment to Quality: Seiso demonstrates a commitment to quality standards and continuous improvement.
  • Sustainable Practices: Maintaining cleanliness and inspection practices over time ensures sustained benefits.

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:

Discover more from FourWeekMBA

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

Continue reading

Scroll to Top
FourWeekMBA