What’s the best way to champion quality in sprints without overstepping?
The Art of Championing Quality in Sprints—Without Overstepping
Imagine this: You're in a sprint planning meeting, and the team is buzzing with excitement over a new feature. Development tasks are being assigned, timelines are being discussed, and just as you're about to raise a concern about test coverage, you hesitate. You don’t want to be that person—the one who slows things down or seems overly critical. Sound familiar?
As a Software Development Engineer in Test (SDET), your role is to advocate for quality, but it’s a delicate balance. Push too hard, and you risk alienating your team. Stay too quiet, and you might watch preventable bugs slip through the cracks. So, how do you champion quality in sprints without overstepping?
Why Quality Advocacy Matters
Quality isn’t just a testing concern—it’s a team-wide responsibility. In an era of CI/CD and rapid releases, shifting left on quality ensures:
The challenge? Many teams still treat testing as an afterthought, and SDETs often struggle to be heard without being perceived as blockers.
Walking the Fine Line: How to Influence Without Overstepping
Here’s how you can embed quality into your team’s DNA—without ruffling feathers.
1. Frame Quality as an Enabler, Not a Gatekeeper
One of the biggest misconceptions about quality is that it slows development down. Reframe the conversation: testing isn’t about stopping progress—it’s about accelerating it by preventing costly rework later.
? Example: Instead of saying, “We can’t release this without full test coverage,” try, “A quick smoke test here could help us avoid post-release fires.”
2. Integrate Testing Into Sprint Planning
Quality advocacy starts before the first line of code is written. Join backlog grooming sessions and planning meetings—not just to review test cases, but to influence how features are designed.
? Example: When a new API is discussed, suggest writing testable contracts upfront. This makes it easier to verify correctness later.
3. Make Data-Driven Arguments
Subjective opinions about quality can feel like personal preferences. Instead, leverage data to support your recommendations.
? Example: “In our last release, 40% of critical bugs were due to missing edge case testing. Let’s refine our definition of ‘done’ to include these cases.”
4. Automate Wisely—And Collaboratively
Test automation should be a shared responsibility, not just an SDET’s task. Work with developers to integrate automated tests into the pipeline in a way that benefits everyone.
? Example: Instead of saying, “QA will handle automation later,” propose, “Let’s pair on writing a unit test so it’s part of the definition of done.”
5. Celebrate Small Wins and Build Allies
Quality advocacy isn’t just about catching bugs—it’s about creating a culture where everyone cares about excellence. Recognize and appreciate when developers write tests, fix flaky ones, or improve code coverage.
? Example: A quick Slack shoutout—“Huge kudos to [Dev’s Name] for catching that race condition early with a test case! Saved us a ton of debugging later!”
The Bottom Line: Influence, Don’t Impose
SDETs are in a unique position to bridge the gap between development and testing. The key to championing quality is collaboration, not confrontation. By embedding quality discussions early, using data to drive decisions, and celebrating progress, you can become a trusted partner rather than a bottleneck.
How do you advocate for quality in your sprints? Have you faced resistance? Let’s discuss in the comments!