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:

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