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:

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