regression-testing

Regression Testing

Business / By /

Regression testing is a vital software testing process that verifies existing functionalities after making code changes. It helps detect defects, ensures product stability, and maintains overall software quality. Automated and selective regression testing streamline the process, and tools like Selenium, TestNG, and JUnit enhance efficiency and accuracy.

Purpose of Regression Testing

The primary objectives of regression testing are as follows:

  • Detect Defects: One of the main purposes of regression testing is to identify and capture any new defects, errors, or issues that may have been inadvertently introduced into the software as a result of code changes or updates.
  • Ensure Stability: Regression testing verifies that existing features and functionalities of the software remain stable and unaffected by recent code modifications. It helps ensure that changes do not introduce unexpected issues that impact user experience.
  • Maintain Quality: By conducting regular regression testing, software development teams can maintain and improve the overall quality and reliability of the software product. This contributes to higher customer satisfaction and trust.

Execution Methods of Regression Testing

Regression testing can be performed using various execution methods:

  • Manual Regression Testing: This approach involves human testers meticulously checking each feature, functionality, or aspect of the software for regressions. While it can be time-consuming, manual testing allows testers to thoroughly explore the application.
  • Automated Regression Testing: Automation tools and test scripts are employed to execute repetitive test cases efficiently. Automated regression testing is particularly useful for quickly retesting a large number of scenarios after code changes.
  • Selective Regression Testing: Instead of retesting the entire software, selective regression testing focuses only on specific areas or features that are likely to be affected by recent code modifications. This approach optimizes testing efforts.

Frequency of Regression Testing

Regression testing can be performed at various intervals, depending on the software development process:

  • Continuous Integration: In modern software development practices like Continuous Integration/Continuous Deployment (CI/CD), regression tests are integrated into the development pipeline. Tests are executed automatically each time code changes are committed, ensuring that regressions are quickly identified and resolved.
  • On Release Basis: Regression tests are conducted before deploying a new version of the software to production. This helps ensure that the release candidate is stable and free from new defects.
  • On Fixed Schedule: In Agile development, regression testing may be conducted at regular intervals, such as after each sprint or iteration. This ensures that cumulative changes do not negatively impact the software’s stability.

Tools for Regression Testing

Regression testing can be significantly facilitated by various testing tools and frameworks:

  • Selenium: An open-source automation testing framework often used for web applications. Selenium allows testers to create and execute automated test scripts to ensure web application stability.
  • TestNG: A testing framework inspired by JUnit, TestNG is suitable for test configuration, grouping, and parallel execution. It is commonly used in Java-based projects for regression testing.
  • JUnit: JUnit is a popular Java testing framework primarily used for unit testing. However, it can also be utilized for regression testing when applicable.

Examples

  • E-commerce Website – Product Catalog:
    • Scenario: A new feature is added to the e-commerce website, allowing products to be categorized based on user preferences.
    • Regression Test: Ensure that existing product categories and search functionality still work correctly after the update.
  • Mobile Banking App – Transaction History:
    • Scenario: A mobile banking app is updated to include advanced search and filtering options for transaction history.
    • Regression Test: Verify that basic transaction history retrieval and display functions remain unaffected.
  • Social Media Platform – Profile Pictures:
    • Scenario: Users are now allowed to upload animated profile pictures on a social media platform.
    • Regression Test: Ensure that the ability to upload, view, and manage regular profile pictures is not broken.
  • Healthcare Software – Billing Module:
    • Scenario: The billing module of a healthcare software system undergoes enhancements to include additional insurance claim processing.
    • Regression Test: Validate that the core functionalities like patient billing and payment processing remain functional.
  • E-learning Platform – Course Enrollment:
    • Scenario: New features are introduced for course recommendations based on user interests on an e-learning platform.
    • Regression Test: Confirm that the core functions like course enrollment and access to course materials continue to work without errors.
  • Inventory Management Software – Reporting:
    • Scenario: A reporting feature is added to an inventory management software for more detailed sales analysis.
    • Regression Test: Ensure that the basic inventory management functions, such as product tracking and order processing, are unaffected.
  • Flight Booking Website – User Authentication:
    • Scenario: The flight booking website introduces a more secure authentication method.
    • Regression Test: Validate that the existing flight search and booking functions, which require user authentication, remain functional and secure.
  • Document Management System – File Uploads:
    • Scenario: Enhancements are made to the file upload feature of a document management system to handle larger file sizes.
    • Regression Test: Verify that other core functions, like document retrieval and sharing, still operate as expected.

Key Highlights

  • Purpose: Regression testing verifies existing software functionalities after code changes to catch defects, ensure stability, and maintain software quality.
  • Methods:
    • Manual Regression Testing: Human testers meticulously check each feature for correctness.
    • Automated Regression Testing: Test scripts and tools automate repetitive tests efficiently.
    • Selective Regression Testing: Focus on specific areas likely impacted by changes.
  • Frequency:
    • Continuous Integration: Tests run frequently as code changes are integrated.
    • On Release Basis: Testing occurs before deploying the product to production.
    • On Fixed Schedule: Tests performed regularly, like after sprints or iterations.
  • Tools:
    • Selenium: Open-source framework for automating web application testing.
    • TestNG: Testing framework for test configuration and grouping.
    • JUnit: Java testing framework for unit testing.

Related Frameworks, Models, or ConceptsDescriptionWhen to Apply
Agile Testing– Agile Testing is an approach to software testing that aligns with Agile principles and methodologies. It emphasizes early and frequent testing throughout the development lifecycle, focusing on collaboration, feedback, and adaptability. Regression Testing is an integral part of Agile Testing, ensuring that changes to the software do not introduce unintended side effects or regressions in existing functionality. In Agile environments, Regression Testing is typically automated to support rapid and iterative development cycles.– During Agile development iterations, continuous integration processes, or software releases to validate changes, prevent regressions, and maintain product quality in dynamic and fast-paced development environments.
Test Automation– Test Automation involves using automated tools and scripts to execute test cases and verify software functionality. It helps accelerate testing processes, increase test coverage, and improve overall efficiency and reliability. Regression Testing is a common application of test automation, enabling testers to quickly re-run previously executed tests to validate that recent changes have not adversely impacted existing features or functionality. Automated Regression Testing is particularly beneficial for large and complex software systems with frequent updates or releases.– During regression testing cycles, software maintenance activities, or post-release validation to automate repetitive test cases, identify regressions, and ensure the stability and reliability of software applications.
Continuous Integration/Continuous Deployment (CI/CD)– Continuous Integration/Continuous Deployment is a software development practice that involves automatically integrating code changes into a shared repository and deploying them to production environments frequently and consistently. Regression Testing is an essential component of CI/CD pipelines, ensuring that code changes do not introduce defects or regressions in the application. Automated Regression Testing is often integrated into CI/CD workflows to validate changes rapidly and enable continuous delivery of high-quality software.– During CI/CD pipeline execution, software build and deployment processes, or release management activities to automate regression testing, validate code changes, and facilitate continuous delivery of software updates with confidence.
Test Driven Development (TDD)– Test Driven Development is a software development approach that emphasizes writing automated tests before implementing the corresponding code functionality. It involves creating small, focused test cases based on specific requirements or user stories and then writing code to fulfill those tests. Regression Testing is inherent in the TDD process, as developers continuously run existing test suites to ensure that newly implemented features do not break existing functionality. By practicing TDD, teams can detect and address regressions early in the development process, minimizing the risk of introducing defects.– During initial feature development, code refactoring activities, or incremental software enhancements to iteratively write and execute test cases, verify changes, and maintain code integrity and reliability.
Test Case Prioritization– Test Case Prioritization is a technique used to determine the order in which test cases should be executed based on their relative importance and potential impact on the software system. It helps optimize testing efforts by focusing on critical test scenarios first, thereby maximizing test coverage and minimizing time-to-detection for high-severity defects. Regression Testing can benefit from test case prioritization strategies, ensuring that critical regression test cases are executed promptly to identify regressions early and mitigate their impact on the software.– During regression testing cycles, resource-constrained testing scenarios, or time-sensitive release schedules to prioritize test execution based on risk, criticality, dependencies, or business priorities and accelerate defect detection and resolution.
Model-Based Testing– Model-Based Testing is an approach to software testing that uses models to represent system behavior, requirements, or user interactions. It involves deriving test cases automatically from these models and executing them to verify the correctness of the software under test. Regression Testing can leverage Model-Based Testing techniques to generate reusable test suites that capture the expected behavior of the system across different states and configurations. By maintaining and updating these models, teams can streamline regression testing efforts and ensure comprehensive coverage of critical scenarios.– During system modeling and requirements analysis phases, test case generation activities, or test suite maintenance processes to create, refine, and automate test models and scenarios for efficient and effective regression testing.
Risk-Based Testing– Risk-Based Testing is a testing strategy that focuses testing efforts on areas of the software that are most likely to contain defects or have the greatest impact on system quality. It involves identifying and prioritizing risks based on factors such as likelihood of occurrence, severity of impact, and business criticality, and then allocating testing resources accordingly. Regression Testing can adopt a risk-based approach to prioritize test coverage and identify critical regression test cases that address high-risk areas of the application. By targeting testing efforts where they are needed most, teams can optimize regression testing effectiveness and efficiency.– During regression testing planning, risk assessment activities, or software maintenance cycles to analyze and prioritize potential risks, allocate testing resources, and determine the optimal regression test coverage based on identified risks and their potential impact on system quality.
Mutation Testing– Mutation Testing is a software testing technique that involves introducing small, artificial changes (mutations) into the source code and then re-running the test suite to determine its effectiveness in detecting these changes. It aims to assess the quality of the test suite by measuring its ability to detect and identify mutant faults injected into the code. Regression Testing can benefit from Mutation Testing by augmenting traditional test coverage metrics with mutation score metrics, which provide insights into the effectiveness of the test suite in identifying regression defects.– During test suite evaluation, quality assurance processes, or continuous improvement initiatives to assess the adequacy and effectiveness of the regression test suite, identify gaps in test coverage, and enhance test case design and execution strategies based on mutation score analysis and feedback.
Test Environment Management– Test Environment Management involves configuring, provisioning, and maintaining testing environments to support software testing activities effectively. It encompasses activities such as environment setup, configuration management, data management, and environment monitoring. Regression Testing relies on stable and consistent test environments to ensure reliable and reproducible test results. Test Environment Management practices help minimize environment-related issues and dependencies that can impact regression testing outcomes. By establishing robust test environments and versioning control mechanisms, teams can streamline regression testing processes and improve test repeatability and reliability.– During test environment setup and configuration, test data provisioning, or test execution activities to manage and maintain test environments, address environment-related issues, and ensure the stability and consistency of testing infrastructure for successful regression testing execution.
Exploratory Testing– Exploratory Testing is an approach to software testing that emphasizes simultaneous learning, test design, and execution. It involves testers exploring the application under test dynamically, adapting test strategies based on evolving insights and observations, and identifying defects through real-time exploration. Regression Testing can benefit from Exploratory Testing by supplementing scripted regression test cases with exploratory test sessions, allowing testers to uncover regression defects that may not be captured by predefined test scenarios. By combining scripted and exploratory approaches, teams can enhance regression testing coverage and effectiveness.– During regression testing cycles, exploratory test sessions, or ad-hoc testing activities to complement scripted regression test cases, explore system behavior, and identify regression defects through dynamic and context-driven testing approaches that leverage tester intuition, creativity, and domain expertise.

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 Innovation, Agile Methodology, Lean Startup, Business Model Innovation, Project Management.

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

Main Guides:

Main Case Studies:

More Resources

Scroll to Top

Discover more from FourWeekMBA

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

Continue reading

FourWeekMBA