Julio de Lima: How a QA engineer can help the PO get closer to the team

Being closer to the team, and the user are two important aspects of the PO work in a Scrum team. In this episode, we also about the QA engineer role in the relationship between the team and the PO.

The Great Product Owner: The User-centered PO

A great PO will help the team focus on the user, and understand what their needs are when they use the product. The PO helps the team understand, and focus on the interactions with the product, instead of the code or the technical details. 

The Bad Product Owner: How a QA engineer can help the PO get closer to the team

When PO’s work mostly on their own, and share little with the team beyond the basic specifications for User Stories, a gap emerges in the relationship and later in the understanding of the product. But in these cases, the QA engineer can help the PO get closer to the team, and we explore how in this segment.

Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Julio de Lima

Julio is a Principal QA Engineer working for Capco that believes in the Culture of QA. He has been sharing professional insights and experiences on a daily basis and has more than 4500 students in his 4 online courses. In 2020, he was elected the Brazilian Testing reference practitioner. 

You can link with Julio de Lima on LinkedIn and connect with Julio de Lima on Twitter.

Julio de Lima: Success for QA engineers and Scrum Masters

Julio is a Quality Assurance (QA) engineer, so we discuss what does it mean to be a successful QA engineer in a Scrum/Agile team. In this conversation, we talk about the need to help the whole team feel responsible for the quality of their deliverable. In other words, we talk about how to get the whole team to think like a QA engineer. 

We also talk about the focus on this episode: success as a Scrum Master. In this regard, Julio shares how Scrum Masters can work with QA engineers specifically, to help them improve, and work better with the rest of the team. In this segment, we also discuss some of the pitfalls of estimation.

Featured Retrospective Format for the Week: People, Process and Technology

Julio’s preferred formats revolve around the triad of improvement: people, processes, and technology. He describes how he usually organizes retrospectives around these three topics, and how teams reacted when he deviated from these 3 topics. 

Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches – Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experiences: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome! 

About Julio de Lima

Julio is a Principal QA Engineer working for Capco that believes in the Culture of QA. He has been sharing professional insights and experiences on a daily basis and has more than 4500 students in his 4 online courses. In 2020, he was elected the Brazilian Testing reference practitioner. 

You can link with Julio de Lima on LinkedIn and connect with Julio de Lima on Twitter.

Julio de Lima: The strikingly different role for QA leads in Agile organizations

As Julio’s career evolved, he started facing a waterfall anti-pattern: the status chaser. Julio’s superiors expected him to be intimately familiar with all the details of what was happening with every team, and every tester in his team. This led to an important personal change for Julio, a change that every QA lead needs to go through when working with Scrum/Agile teams. 

About Julio de Lima

Julio is a Principal QA Engineer working for Capco that believes in the Culture of QA. He has been sharing professional insights and experiences on a daily basis and has more than 4500 students in his 4 online courses. In 2020, he was elected the Brazilian Testing reference practitioner. 

You can link with Julio de Lima on LinkedIn and connect with Julio de Lima on Twitter.

Julio de Lima: “It’s not a bug, it’s a feature” – solving conflicts between testers and developers in Scrum teams

Sometimes the perspective of the tester can be different from the team’s perspective when it comes to a bug or defect. When that difference of perspective exists, a conflict might arise. In this episode, we talk about how to bring the testers and developers to a common understanding on how to improve quality and avoid conflicts that escalate and can destroy a team.

Featured Book of the Week: Agile Testing by Janet Gregory, Lisa Crispin

In Agile Testing: A Practical Guide for Testers and Agile Teams by Janet Gregory and Lisa Crispin, Julio found what he calls “the bible for Agile testing practitioners”. The book helped Julio understand how different the tester perspective needs to be when working in an Agile team. 

In this segment, we refer to the concept of exploratory testing, a critical concept for Agile testers. 

About Julio de Lima

Julio is a Principal QA Engineer working for Capco that believes in the Culture of QA. He has been sharing professional insights and experiences on a daily basis and has more than 4500 students in his 4 online courses. In 2020, he was elected the Brazilian Testing reference practitioner. 

You can link with Julio de Lima on LinkedIn and connect with Julio de Lima on Twitter.

Julio de Lima: The QA perspective on the way Agile teams work 

This week’s guest – Julio de Lima – is a quality and testing engineer that shares his views on Agile teams. The testing/quality perspective is critical for Scrum teams. In this episode, we talk about how test engineers can sometimes try to do everything themselves and prevent the team from taking ownership of the quality work. Julio shares his lessons learned and how he learned to help the whole team feel responsible for the quality of their work. 

In this episode, we talk about Acceptance Test-Driven Development, a holistic quality approach that can involve the whole team.

About Julio de Lima

Julio is a Principal QA Engineer working for Capco that believes in the Culture of QA. He has been sharing professional insights and experiences on a daily basis and has more than 4500 students in his 4 online courses. In 2020, he was elected the Brazilian Testing reference practitioner. 

You can link with Julio de Lima on LinkedIn and connect with Julio de Lima on Twitter.

BONUS: Leena N interview – Continuous Delivery for Scrum teams, Part 7

From her early start with Extreme Programming to learning how to integrate testing with Continous Delivery, we explore Leena’s story and describe some of the most important lessons she collected about adopting CD/CI.

Read on to learn what were Leena’s main lessons, as well as the main challenges teams face when adopting CD/CI.

Continue reading BONUS: Leena N interview – Continuous Delivery for Scrum teams, Part 7

BONUS: Wouter Lagerweij interview – Continuous Delivery for Scrum teams, Part 5

Wouter started his Continuous Delivery journey as an Extreme Programmer in his first years of engineering experience. He shares the story of how, as a team, they sat together with the operations department to learn how they developed their software. Thanks to that, they radically changed their build system to export the kind of packages that operations needed. A brilliant story that also illustrates the adage: “Your first customer is the next step in the process!”

Read more to learn why testing is such a key skill and technical area when adopting Continuous Delivery.

Continue reading BONUS: Wouter Lagerweij interview – Continuous Delivery for Scrum teams, Part 5

BONUS: Chris O’Dell interview – Continuous Delivery for Scrum teams, Part 5

Chris started her Continuous Delivery in a small agency, nurturing a build server that nobody cared for. That gave her an insight that is not very common: taking care of the build server was a very practical way to help and care for the team’s success. It was a practical tool that the team needed, but no one was looking after. It was a concrete way to help people. 

Read more to find out how trust plays a key role in Continuous Delivery adoption, and to read Chris’ recipe to get your team started with CD.

Continue reading BONUS: Chris O’Dell interview – Continuous Delivery for Scrum teams, Part 5

BONUS: Manuel Pais interview – Continuous Delivery for Scrum teams, Part 4

How do we get started with Continuous Delivery? Manuel suggests that we run a Value Stream Mapping session with all the teams involved in the release process to learn about the “current state” of the release process. 

We also review the most common challenges and blocks for teams that are starting to adopt Continuous Delivery. 

Read on to learn about the different motivations businesses have to adopt Continuous Delivery, and Manuel’s 3 steps from bi-weekly release to Continuous Delivery.

Continue reading BONUS: Manuel Pais interview – Continuous Delivery for Scrum teams, Part 4

BONUS: Morten Herman interview – Continuous Delivery for Scrum teams, Part 3

Morten’s adoption story starts with a team at eBay Denmark. The team had started working in a more continuous mode, but there was a lot of “release friction” as Morten calls it. You are probably familiar with that friction: it takes a long time to release; the site needed to be “closed” for every release; the team would need to come in at night during the weekend, etc. 

That’s the reality for many teams. No surprise they prefer to release less often. In this segment, we explore that story, and also the steps the team took to go from “high friction” to “no friction”. 

Read more to find out how Dev and Ops are different and why that matters when adopting Continous Delivery.

Continue reading BONUS: Morten Herman interview – Continuous Delivery for Scrum teams, Part 3