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:

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