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:

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