<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=266211600481844&amp;ev=PageView&amp;noscript=1">

DevOps & Testing

A Few Mistakes You're Probably Making with Your Scrum Quality Assurance Testing: Tech Club Podcast

by Dennis Junk
on December 14, 2016

Quality Assurance testing in scrum software developmentMany agile software development teams have a peculiarly waterfall approach to testing. But, as Aptera’s Quality Assurance Practice Leader Rob Sandoz points out, “Testing also has to be agile.” Does that simply mean automating your tests? If so, what do you even need QA for in the first place? A lot, it turns out. 

James and I invited Rob back for another Tech Club interview this week, because 1) we have a lot of questions about the role of QA in scrum software development ourselves, and 2) our first interview with Rob turned out to be our most listened-to episode to date. This time around, Rob’s discussing common misconceptions about testing and agile development.  

Rob lends some clarity to issues including:

  • Why companies end up doing waterfall testing for supposedly agile projects
  • What it means to test the actual value of software features
  • Why it’s so important to take on the mindset of the end-user
  • At what stage of the development process testing should come into play
  • What steps you’d go through to test something like a login box
  • Why having too much of a delay between development and testing leads to much bigger problems
  • How a QA specialist thinks of Test-Driven Development
  • What the relationship is between meeting functional requirements and delivering business value
  • Why you don’t want to be a “feature factory”
  • What most teams do wrong when it comes to testing in a continuous deployment scenario
  • Why it’s critical to “test early, test often”
  • What role demos play in quality assurance and how it leads into user acceptance testing
  • Where automation comes in and whether you should try to automate all your testing
  • What some of the limitations of automated testing are
  • How regression testing works and when you apply it
  • When and why automation code should be treated like production code
  • Why QA specialists shouldn’t worry too much about losing their jobs to automation
  • What The Tower of QA is and why it’s a terrible way of thinking about testing
  • Who writes the code for automated tests
  • Which QA misconception drives Rob the craziest

Rob is always looking for ways to improve our own processes here at Aptera, so he does a really good job of keeping up with all the latest developments in the industry. To be honest, either James or I could probably have just said, “Misconceptions about testing in scrum projects: go”—and Rob could have easily provided insightful commentary for the 25 minutes allotted to him. (Feel free to let us know if you would prefer that approach in future episodes.)

Send further questions, comments, complaints, or suggestions to us at: techclub@apterainc.com. And thanks for listening.

Other trending posts like this:

Why QA Is Such a Fundamental Part of Agile Software Development: Tech Club Podcast

What It's Like Being a Client for Agile Custom Software Development Projects: Tech Club Podcast

Test-Driven Development and the Importance of Clean Code in Scrum Projects: Tech Club Podcast

Should Custom Software Developers Be Generalists or a Specialists?

How to be a sucessful Scrum and Devops Team

Digital Marketing Assessment
Dennis Junk
I'm Aptera's Content Strategist. I've been writing about tech and marketing for 5 years and have certifications from HubSpot and The Content Marketing Institute. A big science and literature geek, I taught college rhetoric and composition while I was still busy going to school for way too long, earning bachelor's degrees in anthropology and psychology, along with a master's in British and American literature. Look me up on LinkedIn.
You may also like:
A Results-Driven Digital Agency www.apterainc.com