kamishibai

Kamishibai (Visual Management)

Kamishibai (Visual Management) is a visual technique used to manage and improve processes through regular audits. It involves components like Kamishibai cards and boards, and follows a process of task selection, audit execution, and corrective action. Implementing Kamishibai offers benefits such as process visibility, continuous improvement, and team engagement, but it also comes with challenges like resistance and information overload. Its use cases range from production line management to project management and service delivery improvement. Key roles in Kamishibai include team leaders, frontline workers, and process owners.

Components of Kamishibai

  • Kamishibai Cards: Kamishibai cards are physical cards containing specific tasks and audit items. These cards serve as visual cues for task management and process auditing.
  • Kamishibai Board: A Kamishibai board is a visual display that showcases the status of tasks, audit results, and other relevant information. It serves as a central point for monitoring and managing tasks.

The Kamishibai Process

  • Task Selection: The first step in the Kamishibai process involves choosing tasks for audit. This selection is based on factors such as task importance, impact on organizational goals, and relevance to process improvement.
  • Audit Execution: Regular audits are conducted using Kamishibai cards. Each card represents a specific task or process element to be audited. The cards are pulled from the Kamishibai board and used as a checklist during the audit.
  • Corrective Action: Based on the audit results, corrective actions are taken to address identified issues or deviations. These actions are aimed at improving processes and ensuring alignment with organizational objectives.

Benefits of Kamishibai

Implementing Kamishibai offers several notable benefits to organizations:

  • Process Visibility: Kamishibai provides improved visibility of processes and their performance. Visual indicators on the Kamishibai board allow teams to assess task status at a glance.
  • Continuous Improvement: Kamishibai fosters a culture of continuous improvement by identifying issues proactively and enabling teams to take corrective actions promptly.
  • Team Engagement: By involving frontline workers in task audits and improvement efforts, Kamishibai increases engagement and ownership among team members.

Challenges in Implementing Kamishibai

Despite its benefits, Kamishibai implementation can face several challenges:

  • Resistance: Overcoming resistance to change and the introduction of new ways of working can be a significant challenge in Kamishibai adoption.
  • Sustaining Effort: Ensuring consistent execution and maintenance of the Kamishibai system over the long term requires ongoing effort and commitment.
  • Information Overload: To avoid overwhelming Kamishibai cards with excessive data and information, organizations must strike a balance between detail and clarity.

Use Cases of Kamishibai

Kamishibai can be applied effectively in various scenarios:

  • Production Line Management: Kamishibai is used for task and quality checks in a production line, ensuring that operations run smoothly and efficiently.
  • Project Management: In project management, Kamishibai aids in monitoring task progress and allows for timely adjustments to project plans.
  • Service Delivery Improvement: Kamishibai can be implemented in service-oriented organizations to improve service delivery, enhance customer satisfaction, and ensure adherence to service standards.

Roles in Kamishibai

Several key roles are involved in the successful implementation of Kamishibai:

  • Team Leader: Team leaders are responsible for leading the Kamishibai process, conducting audits, and ensuring that corrective actions are taken when necessary.
  • Frontline Workers: Frontline workers perform Kamishibai tasks, follow audit procedures, and record results during the auditing process.
  • Process Owners: Process owners oversee the Kamishibai process, initiate corrective actions, and ensure that tasks align with organizational objectives.

Examples

  • Production Line Quality Control:
    • Scenario: In a manufacturing facility, a production line is responsible for assembling electronic devices.
    • Kamishibai Application: Kamishibai is implemented to ensure quality control. Kamishibai cards are created with specific audit items related to product assembly and quality checks. Team leaders and frontline workers regularly perform audits using these cards. When discrepancies or defects are identified during audits, corrective actions are initiated promptly. This approach improves product quality, reduces defects, and ensures that assembly processes are in compliance with quality standards.
  • Construction Project Progress Monitoring:
    • Scenario: A construction company is working on a complex building project with multiple tasks and deadlines.
    • Kamishibai Application: Kamishibai is used in project management to monitor task progress. Kamishibai cards outline various construction tasks and milestones. Project managers conduct regular audits using these cards to check task status and completion. If delays or issues are detected, corrective actions are taken, such as reallocating resources or adjusting timelines. Kamishibai helps ensure that construction projects stay on track, minimizing delays and cost overruns.
  • Healthcare Facility Patient Care:
    • Scenario: In a hospital, providing high-quality patient care is a top priority.
    • Kamishibai Application: Kamishibai is employed to enhance patient care processes. Kamishibai cards contain audit items related to patient care protocols, hygiene, and safety measures. Nursing supervisors and frontline staff perform regular audits, ensuring that care standards are met. Any discrepancies or non-compliance issues are addressed promptly through corrective actions. Kamishibai contributes to improved patient safety, quality of care, and adherence to best practices.
  • Customer Service Call Center:
    • Scenario: A customer service call center aims to improve customer satisfaction and call resolution times.
    • Kamishibai Application: Kamishibai is used to enhance service delivery. Kamishibai cards outline key call center tasks and performance metrics. Team leaders and call center agents perform audits to assess call quality, response times, and adherence to scripts. When issues are identified, corrective actions may include additional training, process adjustments, or coaching. Kamishibai helps maintain high service standards, leading to increased customer satisfaction and more efficient call handling.
  • Retail Store Inventory Management:
    • Scenario: A retail store chain wants to ensure efficient inventory management across its locations.
    • Kamishibai Application: Kamishibai is applied to monitor inventory levels. Kamishibai cards list inventory-related tasks, including restocking, inventory counts, and order placements. Store managers and employees conduct regular audits to assess inventory accuracy and identify any discrepancies. Corrective actions, such as adjusting order quantities or investigating stockouts, are taken based on audit results. Kamishibai contributes to optimized inventory management, reducing overstock and understock situations.

Kamishibai (Visual Management) Highlights:

  • Concept: Kamishibai is a visual management technique using cards and boards for process improvement through regular audits.
  • Components: Kamishibai Cards, Kamishibai Board.
  • Process: Task Selection, Audit Execution, Corrective Action.
  • Benefits: Enhances process visibility, fosters continuous improvement, increases team engagement.
  • Challenges: Overcoming resistance, sustaining effort, avoiding information overload.
  • Use Cases: Production Line Management, Project Management, Service Delivery Improvement.
  • Roles: Team Leader, Frontline Workers, Process Owners.

Related Frameworks, Models, or ConceptsDescriptionWhen to Apply
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.
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.
Kaizen Events– Kaizen Events, also known as Rapid Improvement Events or Workshops, are focused, time-bound initiatives aimed at solving specific problems, improving processes, or achieving targeted objectives within a short timeframe. – It involves cross-functional teams coming together for a concentrated period to analyze problems, brainstorm solutions, and implement changes using lean and continuous improvement principles. – Kaizen Events enable organizations to make significant improvements quickly, engage employees in problem-solving, and create momentum for ongoing improvement efforts.– When organizations need to address critical issues, implement process improvements, or achieve performance goals rapidly and effectively. – Kaizen Events provide a structured approach to problem-solving and improvement, allowing teams to focus their efforts, leverage collective expertise, and achieve tangible results within a short timeframe. – It is applicable in various contexts, including manufacturing, healthcare, and service industries, where rapid improvement and innovation are essential for competitiveness and sustainability.
Plan-Do-Check-Act (PDCA) Cycle– The Plan-Do-Check-Act (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.
A3 Problem-Solving– A3 Problem-Solving is a structured problem-solving methodology that uses the A3 Report format to document the problem-solving process, analysis, and action plan on a single sheet of paper (A3 size). – It involves defining the problem, analyzing root causes, generating solutions, and developing an action plan with clear goals, responsibilities, and timelines. – A3 Problem-Solving promotes collaboration, transparency, and accountability by providing a visual and standardized format for communicating and managing problem-solving efforts.– When organizations or teams encounter complex problems or opportunities that require systematic analysis, collaboration, and action to address effectively. – A3 Problem-Solving provides a concise and structured approach to problem-solving, enabling teams to clarify objectives, identify solutions, and implement changes in a clear and systematic manner. – It is applicable in various contexts, including lean management, quality improvement, and project management, where structured problem-solving and continuous improvement drive organizational effectiveness and innovation.
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.
Fishbone Diagram (Ishikawa Diagram)– The Fishbone Diagram, also known as the Ishikawa Diagram or Cause-and-Effect Diagram, is a visual tool used to identify and analyze the potential causes of a problem or effect. – It involves drawing a horizontal line representing the problem or effect and adding diagonal “bones” or branches representing different categories of potential causes (e.g., people, process, equipment, environment). – The Fishbone Diagram facilitates brainstorming and structured analysis of root causes, helping teams identify underlying factors and relationships contributing to the problem.– When organizations or teams want to understand the complex interactions and factors contributing to a problem or effect and identify potential root causes systematically. – The Fishbone Diagram provides a structured and visual approach to root cause analysis, enabling teams to explore multiple perspectives, generate hypotheses, and prioritize areas for investigation and improvement. – It is applicable in problem-solving, quality management, and risk analysis, where understanding causal relationships and addressing root causes are essential for effective problem resolution and prevention.
Value Stream Mapping (VSM)– Value Stream Mapping (VSM) is a lean management technique used to visualize, analyze, and improve the flow of materials and information across the entire value stream. – It involves creating visual maps or diagrams that depict the current state and future state of the value stream, identifying value-added and non-value-added activities, and prioritizing improvement opportunities. – Value Stream Mapping enables organizations to identify waste, bottlenecks, and inefficiencies in their processes, and develop action plans to streamline workflows, reduce lead times, and enhance overall value delivery to customers.– When organizations aim to identify and eliminate waste, streamline processes, and optimize value delivery across the entire value stream. – Value Stream Mapping (VSM) provides a systematic approach to process analysis and improvement, enabling organizations to identify opportunities for waste reduction, cycle time reduction, and quality improvement. – It is applicable in various industries, including manufacturing, service, and healthcare, where process optimization and value creation are essential for achieving competitive advantage and customer satisfaction.
Heijunka (Production Leveling)– Heijunka, or Production Leveling, is a lean manufacturing technique used to balance and smooth production across different product variants or demand fluctuations. – It involves scheduling production in small, frequent batches and leveling the mix and volume of products to match customer demand over time. – Heijunka reduces variability, eliminates overburden, and improves flow efficiency by aligning production with customer demand and avoiding peaks and valleys in workload and inventory levels.– When organizations aim to improve production efficiency, flexibility, and responsiveness by leveling production volumes and smoothing demand fluctuations. – Heijunka enables organizations to optimize resource utilization, minimize lead times, and respond quickly to changing customer demand while maintaining stable and predictable production processes. – It is applicable in manufacturing environments with high demand variability, mixed product lines, and limited production capacity, where balancing workload and inventory levels are essential for meeting customer requirements and maximizing operational efficiency.

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