Pod Insights The Agile Daily Standup - AgileDad Five Most Forgotten Parts From The Scrum Guide About this episode Five Most Forgotten Parts From The Scrum GuideScrum. Love it or hate it. There doesn’t appear to be much in between. I like the framework, although I don’t think it is perfect. At the same time, I understand the developers who hate it from the bottom of their hearts. Strangely enough though, they have different problems with Scrum than I have. And zooming in, their problems often are not about Scrum in the first place. They shed light on how Scrum can be misapplied in many ways. Today I will list the 5 most forgotten, misunderstood or misapplied parts of the Scrum Guide. I will also tell how they are misapplied and their actual intention. 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:16 Speaker 00 And then there was Scrum. Love it or hate it, there doesn't appear to be much in between. I truly like the framework, although I don't think in any way, shape or form it's perfect. But at the same time, I understand the developers who hate it from the bottom of their hearts. Strangely enough, though, they have different problems with Scrum that I have. Zooming in on their problems, it's often not about Scrum at all in the first place. They, they tend to shed light on how Agile is misapplied in many ways. So let me explain to you where I'm trying to go with this. I believe that most people don't recognize that Scrum is a framework for Agile delivery. So it's an Agile delivery framework.
0:58 Speaker 00 And they don't realize that you need to focus on other things as well. Things like initiation and ideation, discovery, how we're going to get to where we're going and then release finally. So there's a lot of things that Scrum doesn't necessarily hyper-focus on. So the question becomes, what are some of the most forgotten pieces
1:20 Speaker 00 from the Scrum guide that people could implement to help their Scrum implementation run more smoothly? So let's give you like the top five. So here we go. Number one, Scrum's focus is on creating valuable products. So Scrum is a delivery framework. It's, Scrum teams create value by delivering product increments regularly. It's just the way it is. The ultimate purpose of Scrum is to maximize the value of the product. And I think that's the piece that people miss. This is why Scrum has a product owner and it's accountable for maximizing the value to product. A product backlog, which is an ordered, organized list of what needs to be done to improve a product or to create a new product. And a product goal, identifying the future state of a product.
2:06 Speaker 00 So interestingly, if you compare this to SAFE, SAFE also claims to include Scrum. However, SAFE has team backlogs instead of product backlogs and no product goal. So it's really interesting because lots of times in my training, I talk about the importance of being able to filter by and seeing a team backlog. The purpose behind a team backlog is also something that's misunderstood. The team backlog helps limit whip. It helps prevent overburdening a team with too many things in flight. So if you can get to that point, you're, you're, you're in a much better place. All right, let's go to number two. The Scrum values are absolutely crucial. Use the Force. Most people don't remember the Scrum values, but if you remember the Force from Star Wars,
2:49 Speaker 00 you have focus, openness, respect, commitment, and extreme courage. Those are the five values of Scrum. So to be successful at Scrum, teams can't function in organizations that favor the top-down approach. Or if they have a really hierarchical, hierarchical structure.
3:08 Speaker 00 Or if they favor politics and they're geared towards individualism. These organizations blame the bringer of bad news and don't see the benefit of the creative teamwork. So Scrum can only work in an environment of trust. Because only when people trust each other will they be able to be transparent. To discuss unexpected setbacks, have healthy conflicts, access to potential of everyone with optimized collaboration. You gotta have that whole communication piece in there. Embracing the Scrum values helps you build trust. Having and showing respect, committing to the team goals, being open and honest about challenges, and showing courage to work on difficult issues helps you focus on mutual goals. All right, let's go to number three.
3:52 Speaker 00 Number three, the sprint goal is a sprint commitment, not the selected items that are being done in a sprint. So a lot of people think the sprint goal is, I'm going to complete the six items. That's not the sprint goal. Completing and delivering all the items selected during sprint planning is is part of your job. It's this is why developers often work overtime to try to make the sprint, but that's not true. That's not where we're going. Developers committing to achieving a sprint goal is something different. The consequence of committing to a sprint goal is that the sprint backlog with the selected product backlog items is adaptable. Whenever developers think they can
4:34 Speaker 00 optimize the chances of achieving a sprint goal differently, they can add, remove, or re-prioritize tasks as they see fit to make it to the end goal. All right, let's go to number four. Developers own the sprint backlog. Oh, my goodness. I am so glad I'm talking about this. The developers determine how they do the work to achieve the sprint goal. It's just the way it is. They own the sprint backlog. The product owner owns the product backlog. The sprint team owns the sprint backlog. I say that all the time. But people just, when they change the name of developers, people got lost somehow and don't understand. I hear so many people say the Scrum Master owns the sprint backlog, and that's not true.
5:16 Speaker 00 Scrum Masters, anyone outside the team, have no business trying to change the sprint backlog. Adding or changing items into plans can affect the way the developers deliver. They can offer insights and make recommendations, but the developers get the final decision because they're doing the work. They're self-managing, self-directed, and they should be the ones with the final decision. And finally, number five, delivering multiple increments per sprint. I've seen people hate Scrum because they claim teams can only deliver a single potentially shippable increment at the end of every sprint after approval at the sprint review. This is why they hate the framework, and it's it's definitely justified. Scrum does allow multiple deliveries in a single sprint. Why not?
6:00 Speaker 00 If a team can deliver multiple times a day, that's great in most cases. You just need to understand the ecosystem that you're working in and the culture and adaptability of change for your target audience to make sure that you're not overwhelming or underwhelming what's going on. So the sprint starts, the sprint, every sprint starts with finding a sprint goal. We wish to show how our product is technically feasible. The sprint ends with a review and the stakeholders look at that goal and say, did we meet the goal? We will show that our product is technically feasible and discuss stakeholder feedback and other learnings. Sprints exist because teams work in complex environments, and they can't always predict exactly what's going to happen. So they need to take small incremental
6:41 Speaker 00 steps, verify the steps, and then take those learnings into their next sprint. So I could go on with hundreds of these, but I think that's probably going to do it for now. I think that the keys that people don't get, I mean, over the years, I've come to some conclusions. Scrum is by far not the only approach that's misunderstood or misapplied.
7:07 Speaker 00 Safe? There's so many things that people misapply.
7:12 Speaker 00 Next, we saw a bandwagon effect where organizations started to work with Scrum because everyone else is doing it, so we need to do it. And this is not only a bad reason, but also an indicator that organizations didn't necessarily redefine PR, if you will. The Scrum Guide is geared towards the role of the Scrum team, but largely ignores the role of leadership and stakeholders.
7:33 Speaker 00 This is kind of a mistake because leadership and stakeholders are crucial for the success of the team. But this is the whole reason why at Agile Dad, we created an Agile Leadership Playbook, so that people could see that it does need to have both, and that people need to understand. I think probably the summary, the most important piece, is that Scrum requires a learning culture. Many organizations don't have a learning culture, and they don't want to change, and they get stuck in what they're doing. And they want to have an excuse to blame something for when things fail, but they don't want to talk about what caused their things to go well. And I think that if you look at Scrum as this ecosystem of moving parts that all work towards a common sprint goal, that's going to help you really achieve what you're trying to do. That's going to do it. I hope you enjoyed this episode. If you have
8:18 Speaker 00 a topic you want us to discuss, learn more at agiledad.com, where we could, we'd love to hear from you, and you, and you over here. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care.
Previous Dependencies Destroy Agility and Predictability Next Is the Party Over For Scrum Masters and Agile Coaches? Page updated November 7, 2026 · transcript and summary are machine-generated