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:

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