Pod Insights The Agile Daily Standup - AgileDad Scrum Roles - Who Does What? About this episode Scrum, a popular framework within Agile project management, emphasizes collaboration, flexibility, and iterative progress. Central to its success are three key roles: the Product Owner, the Scrum Master, and the Scrum Team Members. Each role plays a crucial part in the Scrum process, ensuring that teams can deliver high-quality products effectively. How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 So someone sent over an article talking about Scrum roles, who does what? And it's talking about three key roles. What I can tell you is interesting about this is I actually appreciated the take that the author went through for these roles. So I did have an opportunity to read it through, so I want to share some of it with you. So let's, let's share some of this article with you. It says, "Scrum, a popular framework within the agile project management emphasizes collaboration, flexibility, and iterative progress. Central to a success are three key roles: the product owner, Scrum master, and Scrum team," which is the development team. "Each role plays a crucial part in the Scrum framework, ensuring that teams can deliver high-quality products effectively. Let's explore the roles in detail." Great, sounds like a good idea.
0:58 Speaker 00 So, right out of the gate, leading with some factual information, leading with some good information. So far, a good resource, good article. Let's continue. So I start with the product owner, and they call the product owner the visionary leader. I like that. The product owner is the visionary. So the product owner is pivotal in defining the product vision and prioritizing the work needed to achieve it. This role involves several key responsibilities. Number one, right out of the gate, managing a product backlog. The product backlog is dynamic list of features, enhancements, fixes, tasks, required to create a successful product. Let me stop there for a moment. In my world, and this just makes things a lot easier, so this is just a tip for those of you who are watching.
1:40 Speaker 00 In my world, I make everything a story. So I'm gonna say it again, everything is a story. You've got enabler stories, you've got enhancement stories, you've got defect stories, you've got new feature stories. So what I'm trying to say is if you make everything a story, then it just makes it easier because each of the stories have different types. And that way, it just makes it easier when it comes to story point allocation, it makes it easier when it comes to filtering. It just gives you a better, instead of breaking into, oh, this is an enhancement versus a fix versus a task. If you just call everything a story and then give it a type, it just makes it easier to organize the backlog. All right, let's continue. So... The product owner is responsible for creating and refining the backlog. Absolutely.
2:23 Speaker 00 They translate high-level product requirements into actionable stories, ensuring clarity and alignment with stakeholder expectations. Prioritizing items, they continually assess and prioritize backlog items based on factors such as strategic value, consumer value, and technical value. Oh my goodness, this person is my spirit animal. That's exactly what I teach, and I swear, I'm reading the article. And the next one is stakeholder engagement. They service the liaison between stakeholders and a scrum team, ensuring everyone's needs and expectations are understood and addressed. They are the master facilitator, baby. This person must have taken one of my classes. That's all I've got to say. I haven't read the name yet, but this is exactly what I teach in class.
3:08 Speaker 00 Exactly, verbatim, word for word. All right. They also define acceptance criteria. So the product owner also establishes acceptance criteria for each backlog item, which serves as a guideline for the team. Clear acceptance criteria helps ensure that the delivered product meets the intended specifications and requirements. Absolutely 100% correct again.
3:30 Speaker 00 It just feels right. While I'm reading this article, I'm grooving, right? This feels right. It is good. It is what my expectations are. And the only thing I might add there is they can use techniques like Gurkin, right? I'd make sure I bring that up, given when then. Because there's power in using that syntax, where it's more of a, how shall I put it? Natural language syntax? Than something that you're just, uh, yeah, what about this? What about that? It's more of a natural language. I think it's going to go a lot better that way. Okay, let's continue. All right. Making trade-offs. So in an ever-changing environment, the product owner must make tough decisions about scope, time, and people. This often involves balancing the needs of the business with technological feasibility, with stakeholder expectations, with consumer awareness.
4:14 Speaker 00 Yes, absolutely 100%. Scrum Master. Okay, I see one thing here that needs to be tweaked, but so far, overall, it's good. It says Scrum Master equals the Process Facilitator.
4:26 Speaker 00 Hmm, maybe. The Scrum Master plays a vital role in fostering an environment conducive to collaboration, learning, and continual improvement. I do agree with that. So some of their principles include facilitation of Scrum events. Okay, so the Scrum Master ensures that sprint planning, daily Scrum, in retrospectives are conducted effectively. They have a sprint review slash demo listed in here, but in my world, I like for the product owner to facilitate that one. We can talk more about that later. But they want to make sure to keep discussions focused and productive and keep things moving along. I agree. The next one says removing impediments. I'm going to pause there for a second as well. It say removing impediments that the team may not be able to remove themselves, right? Or an individual could remove themselves.
5:12 Speaker 00 So the reason why I say that is because it is the team's primary responsibility to focus on how to handle impediments when they come up, when they arise. I don't want to cripple the team by saying, "Oh, someone else can be responsible handling all your impediments." I want them to take, handle, and deal with impediments as they arise, if they can, right? So the rest of the impediments are the key duty of the Scrum Master to identify and help the team remove obstacles, right? Okay. So addressing team dynamics. If it's interpersonal conflicts that arrive, the Scrum Master should help mediate and resolve issues. Coordinating with external stakeholders. Once again, I feel like that falls more on a product owner's shoulders, but if the Scrum Master can help with that coordination, that would be great. Okay.
5:58 Speaker 00 So our first little, well, little hiccup, but it's not a bad one. Coaching the team. I definitely agree with this one. The Scrum Master acts as a coach or mentor, helping the team understand and adopt Agile framework and practices. They provide guidance on how do you Scrum more effectively and promote a culture of self-organization. All very, very good. Yes, all very good stuff. Okay, let's talk about the developers. Yes, the builders, if you will. And that's what they titled them, builders, awesome. So the development team comprises of professionals who collaboratively work on building the product or service increment. Their responsibilities include having a batch of cross-functional skills. They're expected to possess a variety of skills necessary for the team to develop, including
6:42 Speaker 00 design elements, development, testing, deployment. It's a cross-functional nature that makes it self-sufficient, natural.
6:51 Speaker 00 They commit to goals. So the team members are driven to commit to delivering a potentially shippable product increment at the end of every sprint. And they collaborate closely, ensuring that the goal and the sprint goals and the things they're building are all in line with one another and meet and satisfy the definition of done. Continue improvement. During, during retrospectives, teams discuss, hey, they reflect on their performance, identify what areas are aligned for improvement, which, and are encouraged to experiment with new ideas and processes to enhance their productivity and teamwork going forward. Okay. So I guess what I'm trying to say is overarching.
7:31 Speaker 00 This article does a good job of really giving people a full view of what these different, of what these different roles do. But unfortunately, it does go in after this point and talk a lot about a specific product or service that you can use to help you make all these things better. And you know, anytime somebody puts in a shameless plug for their own product or service, it makes me a little bit crazy. Right? So we're not going to go there. I'm not going to tell you who the, the product is or the company is. But what I can tell you is this person clearly has their header and roles and accountabilities. And what I can tell you also is that I'll never know whether it's somebody who went to my class or not, because they only listed the company name.
8:14 Speaker 00 So whoever the author was of this amazing article, I want to say thank you because you did a fantastic job and I hope that you enjoyed my class because I'm 99% you were there. That's going to do it. I hope you enjoyed this article. If you have a topic you want us to discuss, learnmoreatagiledad.com, I'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous There's No Course Correction In Agile - Mike Cohn Next How To Finally Beat Procrastination and Regain Energy Page updated November 7, 2026 · transcript and summary are machine-generated