In a traditional software development culture, development and QA teams often work independently of each other. As project teams transform from traditional workflows to Agile or DevOps, it can be challenging to get independent Dev and QA teams to collaborate. Not only does each team use different tools, but there can be this sense that code is rushed and thrown over the wall for bugs to be cleaned up in testing. At the very least, this can cause tension between teams, and ultimately, the customer suffers. How do you eliminate this tension, get everyone to adopt new processes, improve teamwork, and focus on delivering value to customers? During the webinar, we will speak with an expert panel to discuss these issues, why improving teamwork matters, and steps you can take to improve teamwork and focus on customers. In this webinar, we will discuss: Why should QA and Dev work together in the first place? What hurdles must be overcome to improve how QA and Dev improve collaboration? What successes and outcomes has the panel experienced as a result of improving teamwork? Specific action steps and small changes you can put in place right way.

1. Getting Dev and QA
to Work Better Together

2. Panelists
Mike Butrym
Independent
Quality Consultant
Jim Holmes
Executive
Consultants
Sanjay Zalavadia
VP of Client
Services
Pillar Technology Zephyr

4. ServiceRocket
- Founded in Sydney, Australia 2001
- Palo Alto, CA HQ since 2010
- 200+ employees across 4 global offices:
Palo Alto, Sydney, Santiago Kuala
Lumpur

5. WE ARE
Apply NOW!
servicerocket.com/careers

6. Agenda
● Topic: How to get dev and QA to work better together. And Why!
● Panel discussion
● Take questions throughout the webinar
● Key takeaways
○ Payoff for Improving teamwork between Dev and QA.
○ As much, or more, about process and communication and culture and teamwork, as it is about tools.
○ Actions you can take today to start making improvements.

7. Dev and QA
Questions You May Ask Yourself
Is testing seen as a bottleneck?
Is bug resolution process too difficult/long/problematic/stressful?
Is testing happening in a vacuum?
Or otherwise does testing happen after dev is complete (as an afterthought).
Are testers expected to assure quality?

9. Why Should Dev and QA Work
Together in First Place?
Increases value to the business.
Shortens feedback cycle.
Improves value delivered to production.

10. How can testers who don’t code possibly help developers?
Personality differences (Grumpy testers and devs).
Differing understanding of requirements/stories/implementation.
What Hurdles Are There to
Overcome?

11. Better mitigation of risk.
Immediate feedback loop on weak requirements, acceptance criteria, bugs, etc.
Terrific knowledge transfer.
Reduced timeframes.
What Are Some
Successes/Outcomes

12. Three Amigos: I can do a half-day workshop and have a team showing value THAT
SAME WEEK
15 minute hand-off discussion/meetings between Dev and QA.
QA progress reporting:
To the right audience (stakeholders, project manager, business owner, etc).
Know the difference between data and insights.
Make reporting visual and transparent.
Small Actions We can Take
Today?

14. Q&A
Mike Butrym
Independent
Quality Consultant
Jim Holmes
Executive
Consultants
Sanjay Zalavadia
VP of Client
Services
Pillar Technology Zephyr

15. getzephyr.comservicerocket.com