Using Agile Testing Quadrants to Solve Quality Assurance Headaches: Part 1 of 2

This is part 1 of a 2-part series. The 1st part will discuss the culture and mindset around Agile, and how Agile Quadrants are used. Part 2 will discuss how to use the Agile Quadrant, the significance of Automation in Agile Quadrants and how to use Agile Quadrants to overcome Quality Assurance headaches.

Organizations aspire to deliver high-quality software at an accelerated rate that offers customer satisfaction and a competitive edge. Agile software development offers these attractive benefits to organizations, and this has led to its worldwide adoption. Despite its many inherent benefits, Agile transformation is still in primitive stages in most of the organizations who say they’re “doing Agile.” Adopting Agile “methodology” is effortless, but succeeding with it is challenging. Simply introducing a new Agile framework will not reap all the benefits of Agile adoption.

Developing the Mindset is Key

The biggest barrier to Agile adoption and transformation is the lack of functional responsibilities within an organization. For example,  some Developers with a traditional mindset feel that testing is the sole responsibility of the Testers. They always have excuses for not testing their code. They feel that writing unit tests takes a lot of effort and wastes time. So, they would rather spend time producing new code. They bypass unit testing and favor creating new features. And for those organizations that have been successful in creating strict expectations for Developer based testing; much is still lost or forgotten when it comes to responsibilities for system integration, user acceptance, and end-to-end testing. 

Bringing the shift in mindset and culture takes time and training.

Lack of understanding of Agile values and principles makes it even more challenging for the Agile teams to succeed with testing and Automation. Below are some of the questions that Agile teams face when it comes to adopting Agile: 

  • How to accelerate releases without compromising on quality?
  • Where does testing and Test Automation fit in the development lifecycle?
  • Who is responsible for quality?
  • What should be our testing strategy?
  • How to increase our Test Automation coverage?
  • What kinds of testing should we perform?
  • What tests should be automated?

In this article, we will deep dive into Agile testing quadrants and answer these questions in order to help you to overcome Agile testing and Automation challenges.

What is Agile?

Agile is NOT a methodology or a set of rules, guidelines, and practices. Agile is a mindset guided by the values in the Agile Manifesto and the 12 principles behind it. Unlike traditional development methodologies, Agile values:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

Agile development methods are iterative, incremental, and adaptive. Agile aims to satisfy the end-users early and Continuous Delivery of valuable software. Agile teams embrace changes, even in late development stages, to provide their customers with a competitive edge.  

Organizations that are transitioning to Agile struggle to understand how testing is integrated at every step in the development lifecycle and oftentimes the old, monolithic QA organization is abruptly disbanded or quickly re-organized to ensure the successful transition to an Agile based organization leaving very little hand-off of processes, people and tools to effectively deploy QA in Agile. As a result of the transition, QA Managers and QA Directors are often re-purposed within the organization to other job duties rendering them powerless to influence a QA blueprint within the constructs of Agile. 

As a response to this, the Agile communities have come to embrace testing quadrants to help ensure governance and enablement for QA practices across the teams and iterations. It assists Project Owners, Scrum Masters, and Value Stream Leaders to create an effective strategy to resolve QA needs at scale across teams, squads, and tribes.

Agile Testing Quadrants

Brian Marick (XP proponent and Co-Author of Agile Manifesto) classified software tests in the form of an Agile testing matrix. This taxonomy placed tests in 2 dimensions:

  1. Support programmers or critique the product
  2. Business or technology facing.

This approach was further developed by Lisa Crispin and Janet Gregory in their book Agile Testing.

The quadrants numbering has nothing to do with how the tests should be sequenced or prioritized. It’s an arbitrary numbering used to simplify describing the tests and their goals.

Below are the 4 quadrants and what they represent:

The tests on the left side of the quadrant focus on preventing defects, and the right side focuses on finding defects and discovering missing features. The tests on the top half are business-facing, and the bottom half is technology facing.

Q1  – Technology-facing tests that support the team

Quadrant 1 (Q1) comprises unit tests and component tests. These tests are usually automated and provide early and quick feedback. In Agile development, quality is a shared responsibility. One of the ways Developers contribute to quality is by writing automated unit/component tests. Unit/component tests support the team to build and change the application rapidly with confidence. Q1 focuses on internal code quality and is primarily the home of test-driven development (TDD).

Q2 – Business-facing tests that support the team

Quadrant 2 (Q2) comprises functional testing, story tests, prototypes & simulations, examples, etc. Most of the projects start in this quadrant. This quadrant focuses on business requirements and turning them into tests from the perspective of a business person. Q2 requires both manual and automated tests to be effective and often software that is highly interdependent systems integration testing could begin. Q2 focuses on eliciting the requirements and is primarily the home of Behavior Driven Development (BDD).

Q3 – Business-facing tests that critique the product

Quadrant 3 (Q3) comprises Exploratory Testing, scenarios, usability testing (UAT), Alpha/Beta testing, heavy system integration testing, etc. Q3 focuses on providing feedback to Q1 and Q2. These tests are now often automated and rely on simple to use no-code/low-code tools to enable non-technical teams to provide key user insight and defect reporting with repetition.

Q4 – Technology-facing tests that critique the product

Quadrant 4 (Q4) comprises Performance/Load Testing, Security Testing, and other non-functional tests. Tests in Q4 ensure that the application under test meets the non-functional requirements. Q4 is majorly tool-driven,often automated, and most importantly, usually cross-functional.

There are no hard and fast rules about which tests belong in which quadrant but rather agile leaders who own the responsibilities for managing Q3/Q4 and/or systems teams as found in SAFe (Scaled Agile Framework), to ensure this function is properly resourced, trained and enabled to support ongoing iterative process of quality infusion within each release.

Summary

This concludes part 1 of Using Agile Testing Quadrants to solve Quality Assurance headaches. As companies continue to transform themselves into highly Agile development organizations, it’s imperative that a shift in mindset is key in terms of knowing there will be fallout of quality assurance responsibilities unless careful considerations are taken in advance. Taking time to train, and educate your staff on Agile values and principles, and organizational structure will help with a successful implementation. Agile Testing Quadrants are a resource to help ensure effective coverage of risk improvement and QA governance across various project and cross functional teams. Part 2 will discuss how to use the importances of Agile Testing Quadrant, the pitfalls of disconnected teams, and solutions you can use to ensure reducing risk, increasing coverage, and overcoming headaches brought on by Agile transformations.

Clayton Simmons
Clayton Simmons has 10+ years in Enterprise Services Business. Clayton ran Cognizant’s Digital Assurance Practice in 2012 and lead an organization focused solely on testing digital enterprise digital solutions for both Mobile and IoT. He successfully rolled out Customer Experience (CX) Test offering which revolutionized the approach to the perceived quality quotient against traditional functional validation of so many other testing services at that time.

The Related Post

Video narrated by MICHAEL HACKETT – Certified ScrumMaster This is Part Three of a Four Part Video on “New Roles for Traditional Testers in Agile Development” Michael shares his thoughts on “A Primer – New Roles for Traditional Testers in Agile”   LogiGear Corporation  LogiGear Corporation LogiGear Corporation provides global solutions for software testing, and ...
The No-Nonsense Guide for How to Write Smarter and Low Maintenance Test Cases Test design is a phrase that is often used when planning testing and test efforts, but I do not believe it is well understood. Also, opinions vary widely about the importance of test design ranging from irrelevant to the crucial ingredient for ...
As CTO of Xebia and highly experienced in offshore testing in India, Guido articulates his methods in addressing common challenges faced by the in-house and offshore teams. He weighs heavily on strategic tactics as well as key cultural aspects to execute efficient and effective Agile methods. 1. I work at a US-based company and we ...
One of the challenges with building an application these days is the number of dependencies that application will actually have on other applications. Ideally in order to know how that application will actually perform, application developers would be able to test their application against the application it depends on running in production. The odds of ...
Author of The Agile Warrior, Rasmusson answers questions from LogiGear’s testing staff about test automation in agile projects.
Distinguishing these terms from each other can be rather confusing. In an attempt to go back to the basics, Nadine Schaeffer explains in detail the benefits and the necessity of using realistic situations.
LogiGear Magazine – November 2010
Agile is a philosophy focused on delivering constant value to customers incrementally and frequently, based on communication and feedback. These two ingredients are vital to a successful Agile recipe. Agile is no longer a buzzword or an unknown territory in the industry. Agile has progressed leaps and bounds the last few years and has matured to ...
Video narrated by MICHAEL HACKETT – Certified ScrumMaster This is Part Two of a Four Part Video on “New Roles for Traditional Testers in Agile Development” Michael shares his thoughts on “A Primer – New Roles for Traditional Testers in Agile”  LogiGear Corporation LogiGear Corporation LogiGear Corporation provides global solutions for software testing, and offers ...
Over the years many Agile proponents have come out strongly against offshoring some of the development team, and in particular against having a remote testing team. We made use of not one, but two separate outsourcing providers located in two distant locations. While we had many challenges, what we found was that by starting with ...
Agile Automation Michael Hackett – Senior Vice President – LogiGear Corporation Michael Hackett Michael is a co-founder of LogiGear Corporation, and has over two decades of experience in software engineering in banking, securities, healthcare and consumer electronics. Michael is a Certified Scrum Master and has co-authored two books on software testing. Testing Applications on the ...
Continuous Improvement and Short Feedback loops (think: Test Driven Development; Sprint Demo/Review; …) are at the core of any Agile process. Without a structured improvement process it can be difficult for teams to improve and without improvement we stagnate. For methods like Scrum, XP and et al., Retrospectives are that tool.

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe