jishu-hozen

Jishu-Hozen

Jishu-Hozen, also known as Autonomous Maintenance, empowers operators to take responsibility for equipment maintenance. It is built on pillars like cleaning, lubrication, and inspection, ensuring increased reliability, improved safety, and cost efficiency. Challenges like operator training and cultural adaptation must be addressed for successful implementation. Use cases include project planning, organizational change, and product development.

Pillars of Jishu-Hozen

  • Cleaning: Regular cleaning and inspection of equipment are essential to prevent the accumulation of dirt, dust, and debris. This pillar emphasizes the importance of cleanliness to maintain equipment in optimal condition.
  • Lubrication: Lubrication is crucial for ensuring smooth operation and preventing friction-related failures. Properly applying the right lubricants at the right intervals is a key aspect of this pillar.
  • Tightening: Loose components can lead to equipment malfunction and inefficiencies. The tightening pillar focuses on checking and tightening any loose parts to maintain equipment integrity.
  • Inspection: Regular inspections play a vital role in identifying potential issues before they escalate into major problems. This pillar encourages operators to conduct inspections and address any anomalies promptly.
  • Standardization: The standardization pillar emphasizes the importance of establishing standard procedures for maintenance tasks and documenting them. Standardization ensures consistency and clarity in maintenance practices.

Benefits of Jishu-Hozen

Implementing Jishu-Hozen offers a range of benefits for organizations:

  • Increased Reliability: Jishu-Hozen enhances equipment reliability by addressing maintenance issues proactively. This reduces the frequency of breakdowns and unplanned downtime.
  • Improved Safety: Safer working conditions are a natural byproduct of Jishu-Hozen practices. Regular maintenance and inspections contribute to a safer environment for operators and maintenance personnel.
  • Cost Efficiency: By reducing breakdowns, extending equipment lifespan, and minimizing repair costs, Jishu-Hozen leads to significant cost savings over time.

Challenges in Implementing Jishu-Hozen

While the benefits of Jishu-Hozen are substantial, several challenges may arise during its implementation:

  • Operator Training: Ensuring that operators are adequately trained to perform maintenance tasks accurately is crucial. Training programs must be in place to equip operators with the necessary skills.
  • Cultural Adaptation: Shifting the organizational culture to embrace autonomous maintenance practices can be met with resistance. Overcoming cultural barriers is a key challenge.
  • Sustaining Commitment: Maintaining long-term commitment to Jishu-Hozen practices is essential. Sustaining enthusiasm and dedication among teams can be challenging over extended periods.

Use Cases of Jishu-Hozen

Jishu-Hozen can be applied in various contexts:

  • Project Planning: Jishu-Hozen principles can be used in project planning to align project goals and gain buy-in from team members. This ensures that maintenance considerations are integrated into project timelines and objectives.
  • Organizational Change: When an organization undergoes significant change, such as process reengineering or technological upgrades, Jishu-Hozen can be applied to manage change effectively and address concerns from employees.
  • Product Development: Implementing Jishu-Hozen during product development allows organizations to obtain input from various departments. This ensures that maintenance requirements are considered from the early stages of product design.

Examples

  • Manufacturing Plant Equipment Maintenance:
    • Scenario: In a manufacturing facility, production heavily relies on machinery and equipment.
    • Jishu-Hozen Application: Jishu-Hozen principles are implemented to ensure the smooth operation of machines. Operators are trained to perform routine cleaning, lubrication, and inspections on equipment. They follow standardized procedures to keep machines clean, well-lubricated, and free of debris. By taking responsibility for equipment maintenance, operators reduce unplanned downtime due to breakdowns, enhance equipment reliability, and contribute to increased production efficiency.
  • Automobile Manufacturing Assembly Line:
    • Scenario: An automobile assembly line requires high precision and efficiency.
    • Jishu-Hozen Application: Jishu-Hozen is integrated into the assembly line’s maintenance strategy. Assembly line operators are responsible for the cleanliness and lubrication of machinery and tools used in the production process. Regular inspections help identify wear and tear on components, and tightening of loose parts is performed as needed. This approach minimizes unexpected equipment failures, improves safety for workers, and maintains consistent production output.
  • Food Processing Facility Hygiene and Safety:
    • Scenario: A food processing plant prioritizes hygiene and safety in its operations.
    • Jishu-Hozen Application: Jishu-Hozen practices are adopted to maintain cleanliness and safety standards. Operators in food processing facilities are trained to perform regular cleaning and inspection tasks on equipment and workspaces. Lubrication of machinery parts is carried out as per guidelines to prevent contamination. Standardized procedures ensure that equipment is thoroughly cleaned and sanitized, reducing the risk of foodborne illnesses and ensuring compliance with safety regulations.
  • Hospital Medical Equipment Maintenance:
    • Scenario: A hospital relies on various medical devices and equipment for patient care.
    • Jishu-Hozen Application: Jishu-Hozen is applied to ensure the reliability and safety of medical equipment. Hospital staff, including nurses and technicians, are responsible for the routine maintenance of medical devices. They conduct regular cleaning, lubrication, and inspections of equipment such as ventilators, infusion pumps, and diagnostic machines. This proactive approach minimizes the risk of equipment failures during critical patient care, enhances patient safety, and reduces equipment downtime.
  • Office Building Elevator Maintenance:
    • Scenario: An office building with multiple floors requires reliable elevator operation.
    • Jishu-Hozen Application: Jishu-Hozen principles are utilized to ensure the smooth functioning of elevators. Building maintenance staff receive training to perform regular cleaning and lubrication tasks on elevator components. They also conduct inspections to identify and address issues such as worn-out cables or loose bolts. By proactively maintaining elevators, building management reduces the likelihood of elevator breakdowns, ensures tenant safety, and provides uninterrupted vertical transportation.

Jishu-Hozen (Autonomous Maintenance) Highlights:

  • Concept: Jishu-Hozen empowers operators to take responsibility for equipment maintenance.
  • Pillars: Cleaning, Lubrication, Tightening, Inspection, Standardization.
  • Benefits: Increased equipment reliability, improved safety, cost efficiency.
  • Challenges: Operator training, cultural adaptation, sustaining commitment.
  • Use Cases: Project Planning, Organizational Change, Product Development.

Related Frameworks, Models, or ConceptsDescriptionWhen to Apply
Autonomous Maintenance– Autonomous Maintenance, also known as Jishu-Hozen in Japanese, is a pillar of Total Productive Maintenance (TPM) focused on empowering frontline operators to take ownership of equipment care and maintenance. – It involves training operators to perform routine maintenance tasks, conduct inspections, and identify early signs of equipment deterioration or defects. – Autonomous Maintenance aims to prevent breakdowns, reduce downtime, and improve equipment reliability by instilling a culture of proactive equipment management and continuous improvement among frontline employees.– When organizations seek to empower frontline operators, enhance equipment reliability, and reduce dependence on maintenance personnel by implementing a structured approach to autonomous equipment maintenance. – Autonomous Maintenance engages employees in equipment care and performance monitoring, fostering a sense of ownership, accountability, and pride in maintaining their work environment and equipment. – It is applicable in manufacturing, facilities management, and process industries, where equipment uptime, reliability, and efficiency are critical for achieving production targets and operational excellence.
Total Productive Maintenance (TPM)– Total Productive Maintenance (TPM) is a comprehensive approach to equipment maintenance and asset management aimed at maximizing equipment effectiveness, uptime, and reliability. – It involves proactive maintenance practices, autonomous maintenance by frontline operators, and continuous improvement initiatives to prevent breakdowns, defects, and unplanned downtime. – TPM focuses on improving overall equipment effectiveness (OEE), reducing equipment failures, and optimizing maintenance processes through employee involvement, training, and performance monitoring.– When organizations seek to optimize equipment performance, reduce downtime, and enhance operational efficiency by implementing a proactive and preventive maintenance strategy. – Total Productive Maintenance (TPM) aligns maintenance activities with production goals, empowering frontline employees to take ownership of equipment care and performance, and driving a culture of continuous improvement and reliability. – It is applicable in manufacturing, utilities, and facilities management, where equipment reliability, uptime, and efficiency are critical for achieving production targets, cost control, and customer satisfaction.
Standardized Work– Standardized Work is a lean management practice that involves defining, documenting, and adhering to standardized procedures and work methods for performing tasks or operations. – It entails establishing best-known methods based on current knowledge, practices, and standards and ensuring consistency, reliability, and accountability in work processes. – Standardized Work serves as a baseline for continuous improvement, training, and performance management, enabling organizations to establish clear expectations, identify deviations, and drive process excellence.– When organizations aim to establish consistency, reliability, and accountability in work processes by standardizing work methods and procedures. – Standardized Work provides a framework for ensuring that tasks are performed consistently and efficiently, reducing variation, errors, and waste in production processes. – It is applicable in various industries, including manufacturing, healthcare, and service sectors, where process standardization and continuous improvement drive operational excellence, cost reduction, and customer satisfaction.
Focused Improvement (Kaizen)– Focused Improvement, also known as Kaizen in Japanese, is a continuous improvement methodology focused on identifying and eliminating waste, inefficiencies, and constraints in processes. – It involves engaging employees in problem-solving, root cause analysis, and improvement initiatives to drive incremental changes and performance enhancements. – Focused Improvement promotes a culture of continuous learning, experimentation, and innovation, empowering employees to challenge the status quo and seek opportunities for improvement in their work areas.– When organizations seek to drive incremental improvements, enhance efficiency, and foster a culture of continuous improvement and innovation among employees. – Focused Improvement (Kaizen) encourages frontline employees to identify problems, propose solutions, and implement changes that eliminate waste, improve quality, and streamline processes. – It is applicable in all areas of operations, including manufacturing, service delivery, and administrative processes, where small improvements contribute to overall productivity, quality, and customer satisfaction.
Root Cause Analysis (RCA)– Root Cause Analysis (RCA) is a problem-solving technique used to identify the underlying causes of problems, errors, or failures and develop corrective actions to prevent recurrence. – It involves systematically investigating events, symptoms, and contributing factors, analyzing data, and asking “why” repeatedly to uncover deeper layers of causality. – Root Cause Analysis helps organizations understand the systemic causes of problems and make targeted interventions to address underlying issues and prevent future occurrences.– When organizations encounter recurring problems, errors, or incidents that impact performance, quality, or safety and want to identify and address the root causes to prevent them from happening again. – Root Cause Analysis provides a structured approach to problem-solving, enabling organizations to identify contributing factors, prioritize corrective actions, and implement sustainable solutions that address the underlying causes of problems. – It is applicable in quality management, risk management, and continuous improvement initiatives, where understanding root causes and implementing preventive measures are essential for achieving operational excellence and minimizing risks.
5 Whys Analysis– The 5 Whys Analysis is a root cause analysis technique used to identify the underlying causes of a problem by asking “why” repeatedly to uncover deeper layers of causality. – It involves starting with the problem statement and asking “why” the problem occurred, then repeating the question for each subsequent answer until the root cause(s) are identified. – The 5 Whys Analysis helps teams understand the systemic causes of problems, rather than just addressing symptoms, and enables them to develop targeted solutions to prevent recurrence.– When organizations or teams encounter recurring problems, errors, or incidents and want to understand the underlying causes to prevent them from happening again. – The 5 Whys Analysis provides a simple and effective approach to root cause analysis, empowering teams to identify and address the fundamental reasons for problems rather than applying superficial fixes. – It is applicable in quality management, process improvement, and problem-solving, where understanding root causes and implementing corrective actions drive continuous improvement and risk mitigation.
PDCA Cycle (Plan-Do-Check-Act)– The PDCA Cycle, also known as the Deming Cycle or Shewhart Cycle, is a four-step iterative problem-solving and continuous improvement methodology. – It involves planning (identifying objectives and developing plans), doing (implementing plans and collecting data), checking (analyzing results and comparing them to expectations), and acting (making adjustments and implementing changes based on findings). – The PDCA Cycle provides a systematic approach to process improvement, enabling organizations to test hypotheses, learn from experience, and drive continuous learning and adaptation.– When organizations or teams want to improve processes, products, or services systematically by applying a structured problem-solving and improvement methodology. – The PDCA Cycle offers a framework for experimentation, learning, and adaptation, allowing organizations to identify root causes, test solutions, and implement changes in a controlled and iterative manner. – It is applicable in quality management, project management, and organizational development, where continuous improvement and innovation drive performance excellence and customer satisfaction.
Gemba Walks– Gemba Walks are a lean management practice that involves leaders or managers going to the place where work is done (the “gemba”) to observe operations, engage with employees, and gain firsthand insights into processes, problems, and opportunities. – It entails walking the shop floor, office, or work area to observe workflow, identify waste, and interact with frontline employees to understand their challenges and perspectives. – Gemba Walks promote leadership visibility, employee engagement, and continuous improvement by fostering open communication, problem-solving, and collaboration at the operational level.– When leaders or managers want to connect with frontline employees, understand operational challenges, and drive continuous improvement by observing work processes and engaging with employees directly. – Gemba Walks provide leaders with valuable insights into the day-to-day realities of operations, enabling them to identify opportunities for process optimization, employee development, and performance improvement. – It is applicable in lean organizations, quality management, and leadership development, where leader presence and engagement at the gemba drive cultural transformation and operational excellence.
Visual Management– Visual Management is a lean management practice that uses visual cues and tools to communicate information, monitor performance, and facilitate decision-making in the workplace. – It involves creating visual displays, charts, and metrics that provide real-time visibility into key processes, performance indicators, and improvement opportunities. – Visual Management enhances transparency, accountability, and problem-solving by making information accessible and understandable to employees and stakeholders.– When organizations seek to improve communication, engagement, and performance by using visual aids to convey information, track progress, and reinforce standards and expectations. – Visual Management promotes a culture of continuous improvement and accountability, empowering employees to identify issues, make informed decisions, and drive operational excellence. – It is applicable in various contexts, including manufacturing, service delivery, and project management, where visual communication and transparency enhance efficiency, quality, and teamwork.

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