Transcript
Vasco (0:04)
Hey there Agile adventurer, just a quick question.
Host (0:07)
What if for the price of a.
Vasco (0:09)
Fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame war free and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's this Scrum Master Toolbox membership. And it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership. That's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast.
Host (1:11)
Hello everybody. Welcome to our TGIF and Product Owner episode this Week with Sara DiGregorio. Hey Sara, welcome back. That is lovely way to greet everybody. Happy Friday everybody. And we're talking about product owners of course, great product owners. We're going to explore all about that. But before do share with us potentially the worst product or anti pattern you've witnessed in your career.
Sara Di Gregorio (1:38)
Well, I think that the anti pattern, the most harmful product owner anti pattern is when they believe that they don't need to interact with the team because sometimes they feel very comfortable in their subject so they assume they know everything and the team has only to execute what they ask for. In this mindset I think that the product owner might write detailed user stories alone, keep interesting discussions with developers and work with developers only when they think it's important to include them. But for me this is the opposite. For me we have to work in opposite way. So if I encounter this situation, for me the first step is to create space for the dialogue. To be honest, I think that we can start a training with the product owner. So we have to make them understand how important is to collaborate and cooperate with the team and then make them automatically including the team because they have to understand how impacting is. Include the team during their conversation from the beginning of the feature study.
Host (3:29)
What I what I often talk about with proctors when it comes to that specific idea of helping them understand why it's important to involve the team is this idea that product owners can come up with product and business innovation, but only the team can come up with the technical side of innovation. Because they understand the technology limitations and possibilities and they can bring that into the conversation. And product owners typically can't because they're not looking at the code every day. They're not looking and dealing with what technology can do. But that's my approach.
