Welcome to another episode of Automation Explanation, an Agile Thought Podcast, where you will learn about quality through automated testing and its place in modern software development.

This week, your hosts, Antwan Maddox and Greg Burdick are celebrating Halloween with the audience by sharing the scariest automation stories.

Key Takeaways

• Dealing with the organization's expectations about the developers’ role
• • Some organizations expect the development Team to test the changes and provide feedback before the changes move forward to production, But it is not the best practice for developers to test their own code, developers in fact need to think outside of the box.
  • Developers realize general observations in order to detect errors and asses risk.
  • Quality analysts are providing the scenarios but not testing them.
• .Whose job is quality? Is it the quality engineer’s, the quality analysts’,  or is it the responsibility of the entire Team to ensure quality?
• • The entire Team is responsible for sharing their observations over the project.
  • When a Team closes a specific sprint, that outcome is the result of the effort of an entire Team. Everyone worked together to provide support to the customer and to follow the correct procedures in order to do so.
• There is a bias towards functionality over vulnerability.
• • You don’t want to rush functionality, it can exhaust the Team.
  • It is important to figure out the reason why the Team is not delivering effectively or timely.
• What are the effects of not following best practices?
• • Manual testers are crucially important.
  • Documenting is extremely valuable and will be used for several purposes. You need to know what and how to document, following a Team agreement. 
  • In order to pass an audit, documentation is vital!
• The Automation Team needs to provide the value of their role to the customer for them to see how they are getting the return of their investment.
• • Don’t hesitate to share your work with the customer, that is the way for the automation Team to show its value to the customer.
  • Automation can become invisible unless you are actively telling the story.

.

.

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!