Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

The challenges of testers & developers working together in a cross-functional Agile team

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

One of the significant changes while moving to Agile teams is that testers and developers are now part of the same team.

This change introduces great advantages, as well as some challenges.

The immediate impact is that the testers participate in the Scrum ceremonies and get a better exposure to the product under development, its status, and its fragility. They can therefore detect better potential areas for defect finding, gain better sync for when they’ll get a drop for testing, and can better utilize their plans.

It sometimes looks more like this:

What we are missing is that as much as this seems like great progress, it focuses on the tester’s local optimum. The mindset is still of a siloed test team that needs to utilize the tester resources better, rather than how to achieve the team’s product delivery goals with high quality and in a timely fashion.

The Agile team is not really a team yet. It is a mixture of people from different disciplines but they are not compounded as a team yet. This results in many times in testers that feel weakened, having lost their power of defending the product quality and of determining how and what to test. They are being told by the SM or Team/Tech Lead how much to test, usually just to minimize test overhead. They are being asked to document less, not to open defects when not needed, to test something that is still in progress, and their test manager is no longer in the teams to back them up. They feel abandoned!

This is a crucial period. I repeatedly see it during implementations and Agile testing workshops I run. On the one hand, the testers crave that the team will understand them and their quality needs, and on the other hand, the testers also need to change their mindset so they won’t impede this change from happening.

This is the place where SMs, Agile leads, and the whole team need to take a shared responsibility for quality and see how they can work it out together as a team. They need to encourage the testers to voice their opinion during Scrum ceremonies and to focus the team on minimizing the gap between testers and developers and how they all contribute to testing.

Yes, it is intimidating for developers. They didn’t join the company to test…they are developers! It is time to understand that the team should focus on their shared goals. Developers should get to know the tested system better, focus on unit testing, strengthen the automation testing, and assist with any setup or test planning that can make a better flow.

On the other hand, it is also intimidating to the testers. They need to change their mindset. They don’t trust the developers to do testing or to distinguish between a testing overhead and a risk. They don’t see the benefit of testing small batches of the product. It looks more like an inefficient plan of re-testing. They feel that if they won’t report, then no one will recognize their work. It is time for the testers to realize they have much more value to offer than to detect defects – they need to prevent them from the get-go, and they need to represent the user. They need to collaborate with the PO and the developers to identify problem areas before coding. They need to become test architects, guide the team, and promote these early and small batches to ensure they hold an end-to-end solution and are in the right direction. They should identify automation requirements and address them and gain trust in automation and in the team.

Adopting an Agile testing mindset and practices should make this movement and bring you to a higher scrum level:

A mindset change takes time. Moving testers into the agile teams is not a mechanical movement. It requires trust, collaboration, learning, the adoption of new practices and experiments, and persistence.

This is why we advise developers, SMs, managers, and team leads also to join our Agile testing workshop. Ultimately, it is not only about the testers but about testing. Yes, it requires leadership to build quality into Agile teams.

What about your challenges?
We’d be happy to help you in this transition. Our Agile Testing workshop is a good starting point. Hope to see you there.

Subscribe for Email Updates:

Categories:

Tags:

Tips
Applying Agile Methodology
Nexus and Kanban
Agile Development
Lean Budgeting
Agile Community
Lean-Agile Software Development
Continuous Delivery
Professional Scrum Master
Lean-Agile Budgeting
Scrum With Kanban
Iterative Incremental Development
Agile Risk Management
Coaching Agile Teams
Built-In Quality
Introduction to Test Driven Development
Agile India
A Kanban System for Software Engineering
Tools
Nexus
QA
Software Development
EOS®
AgileSparks
PI Objectives
Professional Scrum with Kanban
Scaled Agile Framework
TDD
Scrum Master Role
AI
LAB
Agile Israel Events
Agile Mindset
Scrum Primer
Agile Israel
Product Ownership
Hybrid Work
WIP
Sprint Planning
An Appreciative Retrospective
Continuous Deployment
SAFe
lean agile change management
SAFe DevOps
Agile Project
Large Scale Scrum
LPM
Agile Release Management
Lean Software Development
Advanced Roadmaps
Implementing SAFe
Accelerate Value Delivery At Scale
Agile Contracts Best Practices
Agile Testing Practices
Agile Product Development
Engineering Practices
Kaizen Workshop
Perfection Game
SPC
Agile
Sprint Iteration
Agile and DevOps Journey
Business Agility
Risk Management on Agile Projects
Nexus vs SAFe
RSA
Effective Agile Retrospectives
Kanban Basics
Risk Management in Kanban
Rapid RTC
Acceptance Test-Driven Development
Agile in the Enterprise
Nexus and SAFe
POPM
Certified SAFe
Agile Assembly Architecture
Lean Agile Leadership
User stories
Story Slicing
ALM Tools
Implementation of Lean and Agile
Presentation
ATDD vs. BDD
Reading List
Games and Exercises
Release Train Engineer
Kaizen
Self-organization
Lean Agile Organization
RTE Role
Jira Cloud
The Kanban Method
Agile for Embedded Systems
Change Management
speed @ scale
Kanban Kickstart Example
Atlassian
Lean Agile
ScrumMaster Tales
Artificial Intelligence
Agile Project Management
Pomodoro Technique
Systems Thinking
Portfolio for Jira
Agile Techniques
Program Increment
System Integration Environments
ART Success
Introduction to ATDD
ARTs
System Team
Legacy Code
RTE
Achieve Business Agility
Releases Using Lean
GanttBan
Lean Agile Basics
AI Artificial Intelligence
Lean and Agile Techniques
SA
Software Development Estimation
Webinar
LeSS
Lean Startup
Scrum Master
Agile Delivery
Lean and Agile Principles and Practices
Atlaassian
Product Management
Jira Plans
Kanban
What Is Kanban
Limiting Work in Progress
Video
Managing Risk on Agile Projects
IT Operations
Daily Scrum
Sprint Retrospectives
Amdocs
The Agile Coach
Risk-aware Product Development
Slides
Test Driven Development
Agile Games and Exercises
Scrum.org
DevOps
Manage Budget Creation
Planning
Scrum and XP
Operational Value Stream
Continuous Improvement
Scrum
Scrum Guide
Agile Release Planning
NIT
Frameworks
Development Value Streams
chatgpt
Process Improvement
Entrepreneurial Operating System®
Kanban Game
Spotify
Enterprise DevOps
Value Streams
predictability
Agile Marketing
Agile Exercises
Lean Risk Management
SAFe Release Planning
System Archetypes
Lean Agile Management
Continuous Integration
speed at scale
Agility
Nexus Integration Team
Agile Basics
BDD
Scrum Values
Covid19
Agile Product Ownership
Quality Assurance
Jira admin
Agile Program
ROI
Agile Games
agileisrael
Agile Outsourcing
PI Planning
Professional Scrum Product Owner
Principles of Lean-Agile Leadership
Code
Legacy Enterprise
Managing Projects
Certification
ATDD
Continuous Planning
Kanban 101
Elastic Leadership
AgileSparks
Logo
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart