Lisa Crispin, a pioneer in agile testing, co-founder of the Agile Testing Fellowship, highlights the concept of Holistic Testing, which emphasizes testing throughout the entire software development lifecycle, not limited to the end of development or deployment.

Holistic Testing includes continuous testing, shared responsibility, data collection and monitoring, and integration with agile and DevOps practices, ensuring quality is built in from the beginning, rather than being an afterthought. It encourages a collaborative culture where all team members contribute to high-quality outcomes.

The Engineering Quality Podcast

The Engineering Quality Podcast - hosted by Alessandra Moreira, Royalee Martin, and Veronika Pliusnina. Testing focused panel discussions.

• https://www.engineeringqualitypodcast.com/
• https://music.youtube.com/playlist?list=PLqUuvcBX10HyISlL5fhvGJosizW8PD9rV

Episode Details

• Show Notes: https://podcasters.spotify.com/pod/show/engineering-quality/episodes/12-Holistic-Testing-with-Lisa-Crispin-e3duen4
• Published: 2026-01-21T01:50:53Z
• Duration: 00:38:02
• Author: Engineering Quality

Overview

The podcast explores the concept of holistic testing, advocating for an integrated approach where testing is an ongoing activity throughout the entire software development lifecycle rather than a final step before deployment. It highlights the evolution of testing practices and the need to embed testing into all stages of development and operations, emphasizing the importance of cross-team collaboration in maintaining software quality. Key ideas include establishing a shared understanding of requirements early on, prioritizing essential quality attributes, and leveraging continuous feedback and data to support informed decision-making.

The discussion also outlines practical strategies for implementing testing improvements, such as conducting small experiments, using real-time collaboration tools, and applying techniques like example mapping and risk storming. It underscores the value of involving all team members in quality conversations, fostering a shared sense of responsibility, and building strong relationships within teams to sustain long-term improvements in testing and overall software quality.

What If

• What if you start a 30-minute example mapping session before your next sprint planning?
  Concrete move: Use a whiteboard or digital tool to map user stories and business rules with your team.
  Why_now: It directly addresses the need for early requirement alignment (as emphasized in the text) and avoids misalignment with stakeholder expectations.
  Expected_upside: Reduces rework, improves clarity on user needs, and creates a shared understanding of quality attributes before development begins.

• What if you create a visual map of your deployment pipeline using sticky notes and flowcharts this week?
  Concrete move: Collaborate with your team to document every step from code commit to production, including testing stages and bottlenecks.
  Why_now: The text highlights pipeline mapping as critical for identifying testing gaps and inefficiencies.
  Expected_upside: Reveals blind spots in automation/manual testing, speeds up deployments, and improves reliability through targeted improvements.

• What if you schedule a one-on-one meeting with a developer from another team to discuss testing practices this week?
  Concrete move: Use a 30-minute conversation to explore their pain points and share tools like feature flagging or risk storming.
  Why_now: The text stresses building relationships and cross-team collaboration as key to advocating for holistic testing.
  Expected_upside: Gains advocates for shared testing responsibilities, fosters trust, and opens opportunities for influencing broader quality practices.

Takeaway

• Implement continuous testing across the entire DevOps pipeline by integrating automated and manual testing steps (e.g., unit tests, exploratory testing) at every stagedevelopment, deployment, and post-deployment monitoringto ensure quality is built in from the start.
• Run low-risk, 30-minute example mapping sessions during pre-iteration planning to clarify user stories and requirements with your team, fostering early alignment on quality attributes and reducing rework.
• Visually map your deployment pipeline using sticky notes or flowcharts to identify bottlenecks and testing gaps, then prioritize improvements with your team to enhance reliability and speed in software delivery.
• Start with small experiments (e.g., introducing a new tool or technique) to engage non-testing team members in quality discussions, using incremental successes to build momentum and shared ownership of testing practices.
• Build relationships by approaching individual developers or stakeholders for one-on-one conversations, sharing testing tools, or inviting them to collaborate on low-stakes experiments to gradually expand your influence and advocacy for holistic quality practices.