Pair Testing

Business / By /

Pair testing is a software testing technique that involves two individuals, typically a tester and a developer, working together to test a software application collaboratively. It promotes teamwork, knowledge sharing, and cross-functional collaboration to identify defects and ensure high software quality.

Unlike traditional testing methods where testing is performed by a single tester in isolation, pair testing promotes teamwork, knowledge sharing, and cross-functional collaboration between different roles within the development team. By pairing testers and developers, organizations can leverage diverse perspectives, skills, and expertise to identify defects, validate functionality, and ensure high software quality. Pair testing fosters communication, accelerates defect resolution, and promotes a culture of quality across the organization, ultimately leading to improved customer satisfaction and product reliability.

Key Components of Pair Testing

Collaborative Testing

Pair testing emphasizes collaborative testing efforts between testers and developers, encouraging shared ownership of quality and testing responsibilities. This involves working together to plan, execute, and review test cases, share feedback, and validate software functionality.

Knowledge Sharing

Pair testing facilitates knowledge sharing and skills transfer between testers and developers, enabling each team member to leverage their expertise and insights. Testers gain a deeper understanding of the application’s architecture, design, and implementation details, while developers learn about testing techniques, strategies, and best practices.

Real-Time Feedback

Pair testing provides real-time feedback on software defects, usability issues, and quality concerns, allowing testers and developers to address issues promptly. This immediate feedback loop accelerates defect resolution, reduces rework, and ensures that issues are addressed before they impact end users.

Continuous Improvement

Pair testing promotes continuous improvement by encouraging reflection, learning, and experimentation. Testers and developers collaborate to identify areas for improvement, refine testing processes, and explore new testing techniques and tools to enhance software quality and efficiency.

Strategies for Implementing Pair Testing

Pair Formation

Implementing pair testing involves forming pairs of testers and developers based on complementary skills, expertise, and domain knowledge. Pairing individuals with diverse backgrounds and perspectives fosters creativity, innovation, and effective problem-solving during testing activities.

Test Planning and Execution

Implementing pair testing includes jointly planning and executing test cases, scenarios, and test cycles. Testers and developers collaborate to define test objectives, identify test scenarios, and prioritize testing efforts based on risk, complexity, and business impact.

Exploratory Testing

Implementing pair testing encompasses exploratory testing sessions where testers and developers explore the software application together, uncovering defects, usability issues, and edge cases. This interactive and dynamic testing approach encourages creativity, spontaneity, and rapid feedback.

Knowledge Transfer

Implementing pair testing involves facilitating knowledge transfer and skills development between testers and developers. Testers share testing techniques, methodologies, and domain knowledge with developers, while developers provide insights into application architecture, design patterns, and implementation details.

Benefits of Pair Testing

Improved Collaboration

Pair testing fosters collaboration and teamwork between testers and developers, breaking down silos and promoting shared ownership of quality. It encourages open communication, mutual respect, and trust, leading to enhanced productivity and efficiency across the development team.

Accelerated Defect Resolution

Pair testing accelerates defect resolution by providing real-time feedback on software defects and quality issues. Testers and developers collaborate to identify, prioritize, and address issues promptly, minimizing the time and effort required to fix defects and ensuring faster time-to-market.

Enhanced Software Quality

Pair testing ensures high software quality by leveraging diverse perspectives, skills, and expertise to identify defects and validate functionality comprehensively. It promotes thorough testing coverage, early defect detection, and continuous improvement, resulting in reliable and robust software applications.

Knowledge Sharing and Skills Development

Pair testing facilitates knowledge sharing and skills development between testers and developers, enabling each team member to learn from the other’s expertise and insights. Testers gain a deeper understanding of the application’s architecture and design, while developers learn about testing techniques and best practices, leading to a more well-rounded and empowered development team.

Challenges of Pair Testing

Resource Availability

Pair testing may face challenges related to resource availability, particularly in organizations with limited staffing or competing priorities. Ensuring that testers and developers have sufficient time and availability to participate in pair testing sessions may require careful planning and coordination.

Communication and Collaboration

Pair testing requires effective communication and collaboration between testers and developers to be successful. Differences in communication styles, personalities, or domain knowledge may pose challenges to effective collaboration, requiring teams to establish clear communication channels and norms.

Skill and Experience Levels

Pair testing may encounter challenges related to differences in skill and experience levels between testers and developers. Ensuring that both team members have the necessary skills and expertise to contribute effectively to testing activities may require training, mentoring, or skills development initiatives.

Cultural Resistance

Pair testing may face cultural resistance from teams accustomed to traditional testing approaches or siloed development practices. Overcoming resistance to change and fostering a culture of collaboration and shared ownership may require leadership support, advocacy, and cultural transformation efforts.

Implications of Pair Testing

Collaborative Culture

Pair testing promotes a collaborative culture within the development team, where testers and developers work together to achieve common quality objectives and deliver high-quality software. It fosters trust, respect, and teamwork, creating a positive work environment where individuals feel empowered and valued.

Cross-Functional Skills

Pair testing encourages the development of cross-functional skills and competencies among testers and developers, enabling each team member to contribute effectively to testing activities. Testers gain insights into development practices, while developers learn about testing techniques, methodologies, and best practices, leading to a more well-rounded and versatile development team.

Efficient Defect Resolution

Pair testing accelerates defect resolution by providing real-time feedback on software defects and quality issues. Testers and developers collaborate to identify, prioritize, and address issues promptly, minimizing the time and effort required to fix defects and ensuring faster time-to-market.

Continuous Learning and Improvement

Pair testing fosters a culture of continuous learning and improvement within the development team, where individuals are encouraged to experiment with new testing techniques, tools, and approaches. It provides opportunities for reflection, feedback, and skills development, empowering team members to enhance their expertise and contribute to the overall success of the project.

Conclusion

  • Pair testing is a collaborative software testing technique that involves two individuals, typically a tester and a developer, working together to test a software application collaboratively.
  • Key components of pair testing include collaborative testing, knowledge sharing, real-time feedback, and continuous improvement.
  • Strategies for implementing pair testing include pair formation, test planning and execution, exploratory testing, and knowledge transfer.
  • Pair testing offers benefits such as improved collaboration, accelerated defect resolution, enhanced software quality, and knowledge sharing and skills development.
  • However, it also faces challenges such as resource availability, communication and collaboration, skill and experience levels, and cultural resistance.
  • Implementing pair testing has implications for collaborative culture, cross-functional skills, efficient defect resolution, and continuous learning and improvement, shaping efforts to deliver high-quality software and foster a positive and productive work environment within the development team.
Related Frameworks, Models, or ConceptsDescriptionWhen to Apply
Automated Testing– Automated Testing involves using software tools to execute pre-scripted tests on a software application or system. It aims to increase test efficiency, repeatability, and coverage by automating repetitive testing tasks. Automated Testing helps identify defects quickly and ensure consistent test results across different environments.– When organizations want to streamline the testing process, increase test coverage, and accelerate testing cycles. – Applicable during the development phase to detect defects early and ensure software quality before release.
Continuous Integration (CI)– Continuous Integration (CI) is a software development practice where developers regularly integrate code changes into a shared repository. Each integration triggers automated builds and tests to detect integration errors and ensure code quality. CI helps identify defects early, maintain code stability, and facilitate collaboration among team members.– When organizations want to ensure code quality, detect integration issues, and accelerate software delivery cycles. – Applicable throughout the development process to promote frequent code integration and automated testing.
Continuous Delivery (CD)– Continuous Delivery (CD) is an extension of Continuous Integration where code changes are automatically built, tested, and deployed to production environments. CD aims to minimize manual intervention and enable rapid, reliable software releases. It helps ensure that software updates can be delivered to users quickly and with confidence.– When organizations want to automate software deployment and delivery processes, reduce deployment risks, and increase release frequency. – Applicable in DevOps or Agile environments to achieve shorter release cycles and improve software delivery efficiency.
Test-Driven Development (TDD)– Test-Driven Development (TDD) is a software development approach where tests are written before writing the code. Developers write automated tests that define desired system behavior and then implement code to pass those tests. TDD helps improve code quality, design clarity, and test coverage while promoting iterative development.– When organizations want to ensure code reliability, maintainability, and testability from the outset of development. – Applicable during the coding phase to drive development through automated tests and validate system behavior incrementally.
Behavior-Driven Development (BDD)– Behavior-Driven Development (BDD) is a software development methodology that focuses on defining system behavior through examples written in a human-readable format. BDD scenarios describe system behavior from the user’s perspective and serve as automated acceptance criteria. BDD helps align development efforts with business requirements and improve communication among stakeholders.– When organizations want to ensure that software development efforts align with business objectives and user needs. – Applicable in Agile environments to facilitate collaboration between development teams, product owners, and business stakeholders.
Exploratory Testing– Exploratory Testing is an informal testing approach where testers explore the software application without predefined test cases. Testers use their domain knowledge, intuition, and creativity to uncover defects, usability issues, and edge cases. Exploratory Testing helps discover unexpected behavior and complements scripted testing approaches.– When organizations want to uncover defects that may be missed by scripted tests or explore the software’s behavior in unanticipated ways. – Applicable during the testing phase to supplement traditional testing approaches and improve test coverage.
Model-Based Testing– Model-Based Testing is a testing technique where test cases are derived from models that represent system behavior, requirements, or specifications. Models can include state diagrams, flowcharts, or formal specifications. Model-Based Testing helps ensure test coverage, traceability, and consistency in testing efforts.– When organizations want to improve test coverage, reduce test case creation time, and ensure alignment between tests and system requirements. – Applicable in systems with complex behavior or interactions that can be modeled effectively.
Acceptance Test-Driven Development (ATDD)– Acceptance Test-Driven Development (ATDD) is a collaborative approach where developers, testers, and business stakeholders define acceptance criteria before implementation. Acceptance criteria are expressed as automated tests that verify the system’s behavior from a user’s perspective. ATDD helps ensure that development efforts meet customer expectations and business goals.– When organizations want to align development efforts with customer needs and business objectives. – Applicable in Agile environments to facilitate collaboration between development teams and business stakeholders.
Pair Testing– Pair Testing is a testing technique where two team members collaborate to execute test cases, share knowledge, and identify defects collaboratively. One team member performs the tests while the other observes, provides feedback, and documents issues. Pair Testing helps improve test coverage, knowledge transfer, and testing effectiveness.– When organizations want to leverage collective knowledge and skills to improve testing outcomes and accelerate defect identification. – Applicable during the testing phase to encourage collaboration and knowledge sharing among team members.
Shift-Left Testing– Shift-Left Testing is a testing approach where testing activities are performed earlier in the software development lifecycle, typically during the requirements or design phase. Shift-Left Testing aims to identify defects early, reduce rework costs, and improve overall software quality. It emphasizes proactive quality assurance practices and continuous feedback loops.– When organizations want to detect defects early in the development process, improve collaboration between development and testing teams, and reduce defect resolution time. – Applicable throughout the software development lifecycle to promote early defect detection and prevention.

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

Discover more from FourWeekMBA

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

Continue reading

Scroll to Top
FourWeekMBA