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:

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