When Sprint Goals Are Missing, The Consequences of a Task-Driven Product Owner | Ramya Shastri

Summary

Scrum Master Toolbox Podcast: Agile Storytelling from the Trenches
Episode: When Sprint Goals Are Missing, The Consequences of a Task-Driven Product Owner
Host: Vasco Duarte
Guest: Ramya Shastri
Release Date: December 6, 2024

---

Introduction

In this insightful episode of the Scrum Master Toolbox Podcast, host Vasco Duarte engages in a compelling conversation with Ramya Shastri, an experienced Agile Coach and Certified Scrum Master. The discussion centers around the pivotal role of Product Owners in Scrum implementations, particularly focusing on the ramifications of lacking sprint goals and the pitfalls of task-driven Product Owners.

Identifying Critical Anti-Patterns in Product Ownership

Ramya Shastri begins by highlighting a prevalent anti-pattern among Product Owners:

"One of the biggest anti-patterns I have faced is Product Owners who don't help teams understand the sprint goal."
(00:34)

She elaborates that such Product Owners inundate teams with a continuous stream of requirements without a clear sprint objective, leading to confusion and inefficiency. This lack of focus undermines the very foundation of Scrum, where sprint goals are essential for guiding the team's efforts.

Consequences of Missing Sprint Goals

Ramya draws parallels to everyday scenarios to emphasize the importance of sprint goals:

"Imagine you're on a weight loss journey without a target. If you set a goal to lose a specific amount of weight, your actions align towards that objective. Similarly, without a sprint goal, teams lack direction and purpose."
(03:07)

She warns that without sprint goals, teams may face:

• Context Switching: Constantly shifting focus due to erratic requirements.
• Burnout: Overloading team members with unmanageable tasks.
• Reduced Productivity: Inability to complete meaningful work, leading to stagnation.

Strategies to Reinforce the Importance of Sprint Goals

Vasco Duarte inquires about methods to instill the value of sprint goals in Product Owners. Ramya responds by sharing her approach using relatable analogies and practical examples:

"Using analogies like a weight loss journey helps Product Owners understand the necessity of having clear, aligned goals."
(03:07)

She advocates for:

1. Clear Definition of Sprint Goals: Ensuring that each sprint has a well-articulated objective that aligns with the overall product vision.
2. Discipline in Communication: Product Owners must effectively convey sprint goals and resist the urge to introduce unrelated tasks mid-sprint.
3. Team Alignment: Ensuring that all team members understand and are committed to the sprint goal, fostering a unified effort.

Spotlight on Excellent Product Owners

Transitioning to positive examples, Ramya shares her experiences with exceptional Product Owners:

"The best Product Owners I’ve worked with clearly understand their roles and protect their teams from overcommitment."
(06:19)

Key traits of these exemplary Product Owners include:

• Protectiveness of the Team: They act as shields, preventing external pressures from overwhelming the team.
• Effective Scope Management: Regularly check with the team before committing to additional work, ensuring feasibility and maintaining focus.
• Advocacy for the Team: Serve as the spokesperson in negotiations with stakeholders, asserting the team’s capacity and safeguarding against overloading.
• Value Maximization: Constantly strive to deliver maximum value to the customer by prioritizing effectively and aligning tasks with sprint goals.

The Power of Product Owners in Scrum

Vasco Duarte underscores the significant influence Product Owners have on a team's success:

"A Product Owner has the power to make the team succeed or fail. They determine what work the team undertakes and ensure clarity in goals."
(07:57)

He contrasts this with the role of Scrum Masters, who can guide the team but do not hold the same level of decision-making authority. Ramya concurs, tying their responsibilities back to the Scrum Guide:

"The Product Owner's role is to maximize the value of the product, ensuring that the team delivers what truly matters to the customer."
(09:26)

Ensuring Success Through Clarity and Discipline

Both hosts agree that clarity and discipline are paramount for Product Owners to lead effectively. Without these, teams may face:

• Directionless Efforts: Without clear goals, teams lack motivation and purpose.
• Overloading: Introducing too many tasks can overwhelm the team, leading to burnout and decreased morale.
• Loss of Focus: Frequent changes in direction can result in incomplete work and wasted effort.

Conclusion and Final Thoughts

As the episode winds down, Ramya emphasizes the importance of Product Owners understanding their roles deeply and committing to practices that support team success. She encourages listeners to connect with her through LinkedIn and her YouTube channel, Agile Coaching Roundtable, for further insights into Agile practices.

Vasco Duarte wraps up by highlighting the critical nature of discussions like these, which help Scrum Masters and Product Owners alike cultivate environments where teams can thrive and deliver meaningful value.

---

Key Takeaways

1. Importance of Sprint Goals: Clear sprint goals provide direction, prevent context switching, and enhance team focus.
2. Avoiding Anti-Patterns: Product Owners should refrain from being task-driven without a cohesive goal, as it leads to inefficiency and burnout.
3. Traits of Excellent Product Owners: Protective of the team, effective scope management, advocacy for team capacity, and a focus on maximizing value.
4. Power Dynamics: Product Owners have a significant impact on a team's success, more so than Scrum Masters in decision-making authority.
5. Clarity and Discipline: Essential for Product Owners to maintain team focus and prevent overloading, ensuring sustainable productivity and team morale.

---

Further Resources

• Ramya Shastri on LinkedIn: Connect with Ramya Shastri
• Agile Coaching Roundtable Podcast: Listen on YouTube
• Scrum Master Toolbox Community: Join the Membership Site for exclusive content and community interaction.

---

Stay tuned for more episodes of the Scrum Master Toolbox Podcast, where Vasco Duarte continues to bring you actionable advice and inspiring conversations to enhance your Scrum Mastery.

Transcript

[Vasco Duart]

Hi, I'm your host, Vasco Duart. Welcome to the Scrum Master Toolbox podcast where we share tips and tricks from Scrum Masters around the world. Every day we bring you inspiring answers to important questions that all Scrum Masters face day after day. Hello, everybody. Welcome to our Friday product owner and TGIF episode this week with Ramya Shastri. Hey, Ramya, welcome back.

[Ramya Shastri]

Hi, Vasco. Happy to be back.

[Vasco Duart]

Absolutely. And a pleasure to have you back to talk about what is, at least in my opinion, a critical role for the success of any Scrum implementation. And one could even say any delivery, whatever that might be. And that is of course, the product owner role. So, Rami, let's explore that. We'll talk about what great product owners do in a second. But first, share with us potentially the worst product owner anti pattern you've witnessed in your career.

[Ramya Shastri]

Absolutely. So one of the biggest anti pattern I would say is I have faced product owners, I'm saying owners, I'm not even a single person, I have faced product owners who don't even help teams understand the sprint goal. I mean, that is the biggest anti pattern. Right. I mean, I'm not sure what we would be working with if you don't have spring goals. Right. So typically a product owner will come and say, you know what, this is the priority, this is what we want to work, and he or she will come bombarding with the requirements after requirements after requirement. Correct? Correct. So this is one of the biggest anti patterns, I would say, because there is no mechanism whatsoever to kind of put a full stop to requirements that we are trying to deliver. Right. I mean, the value we are trying to deliver. Just because there is a product owner who is facing the customer, who is talking to the customer, understanding the business aspects of it, doesn't mean that you come left, right, center, give requirements, change things upright in the middle of the sprint anytime and anywhere and that will have adverse effects on teams. Right. So that is the biggest anti pattern where the product owners are not even worried about the spring goal. They don't even know what the sprint goal is.

[Vasco Duart]

So when you think about that anti pattern, right. How do you help product owners first understand the value of the sprint goal? That's of course very important. But then also to be able to put that into practice because it does require a high level of discipline and clarity to be able to define a sprint goal. So how do you help the product owners you work with to first understand what the sprint goal is about and second, to have that discipline and clarity to be Able to communicate that with the team.

[Ramya Shastri]

Sure. So if I have to make someone aware about the importance of the sprint goal, I try to give them an analogy, which is my favorite analogy. I have kind of built up this analogy wherein say I come up with a scenario where I'll say that suppose you want to reduce weight, right? You are on your weight loss journey, right? So if you want to lose weight, obviously you will have some target in mind, right? I mean, saying that okay, by end of these many months I would want to be leaner, fitter or whatever, or reduce weight, right? So now when you say you want to reduce weight and you're making an effort to it, imagine you are eating junk at one side, you are saying I want to reduce weight and you are eating junk on the other side. So what does that mean is you are not, you don't have a goal at all. If you have a fixed goal saying that, you know what, I want to reduce so and so weight, so much weight, say whatever, 5 kgs, 10 kgs, 2 kgs. At the end of three months, you will have to set that as your goal and work accordingly. You will have to do only those things that will support your goal. So if you, if you want to reduce weight, you will have to maybe work out. You may want to do cardio, you may want to do cross weight, you may want to do yoga, meditation, whatever you want to do. But then because that those are aligned to your goal of reducing weight, you don't, you will not be foolish enough to say that, no, I'll eat junk food, I eat pizza, I'll eat burger. No, if you're going to do that, you are going to impact your health. You are going to splash water on whatever you have done, right? So that's what I try to say. So if you don't have a goal for your team and you go and adding things up, you are, you don't know what you're trying to achieve, right? So you don't even have a vision, what you're trying to, where you're going to go ahead with, right? So it's like you are walking in a fog. You don't know what is lying ahead, right? So this is what I try to explain them, that you must be having a sprint bowl and whatever things that are aligned to the goal is only going to be part of your sprint backlog, not anything. Otherwise team will burn out. There would be a situation where there would be a lot of context switching happening within the team. Today team is working on something. Tomorrow you'll come up with some other requirement which is not even related to what you were originally working on. Right. So team will lose the context. There will be a lot of context switching. So this is kind of an example I try to give them.

[Vasco Duart]

Yeah. And it's very important for us to be aware of those consequences of the lack of a goal. Right. Like going in all kinds of directions, never finishing anything, accepting too much work, burnout, etc. Are great examples to discuss with our product owners. Now, Ramya, not all product owners are bad. Some are actually quite excellent. So share with us the example of potentially the best product owner you've ever worked with. How did they work?

[Ramya Shastri]

Okay, so obviously the opposite to do what I said now. So I did had an opportunity, I did have an opportunity to work with a few of my product owners who did know exactly what their job is. Right. I mean, what their role is. Right. So for an example, they used to be like a Scrum Master. They used to be very protective about the teams, team members, right? So they would have the sprint goal. They would ensure that there is a sprint goal in team within the sprint. And they would also ensure in a way that for an example, if there is a very demanding customer, right? And they say that, you know what, you have to do this, beg, borrow steel, you have to get this thing done. Right. I have seen a product owner within the projects that I've worked in, wherein the product owner would always come back to team and check with team members whether you are in a position to take this up, whether you will be able to complete this. And that person used to be kind of a spokesperson for the team with the customer saying that no, he used to push back the customer saying that, no, we cannot accommodate this. Our team is already doing so much, we cannot do this. And the product owner used to understand we should not bombard things to team members and we should not make decisions on behalf of team members. So this was also a case where I had an opportunity where the product owner was very accommodative and used to understand his job very well.

[Vasco Duart]

Yeah, absolutely. And this ability to protect the team can be critical for the product owner. The way I usually describe it is that the product owner has the power to make the team succeed or fail. Like we as Scrum Masters, we don't have that power. We can help them succeed, we can help them fail. Both are possible, but we don't have that power. But the product owner has the power. Very simple example, a product owner that is scattered like we just talked about. A minute ago. Right. No sprint goals. Okay. Then that product owner will likely make the team fail because they will not bring the right work to them, they will not be clear about the goals, they will overload them, etc. But a product owner that is very clear on the goal and is able to proactively manage the scope together with the team will help the team succeed. And that is a huge impact. And for me, what's really important is to bring up these topics, like what you just did. Right? Like, what do great product owners do so that we can try to convey that information to our product owners so that they may help their team succeed. Because at the end of the day, they are the ones that can help the team fail or succeed because it's what the team delivers that is the object of success in the end. Right. If the customer is happy, you know, even if we don't deliver all the scope but the customer is happy, that's success. And the product owner has a huge impact on that.

[Ramya Shastri]

Absolutely. And the point that you mentioned. Right on. The product owner has the kind of a power to ensure the team is successful. Even if you check the Scrum Guide, it says the product owner is someone who maximizes the value of the product. Right. And by all means, I mean, he or she is the one who ensures that the team delivers the maximum value to the customer.

[Vasco Duart]

Yeah, absolutely. And that requires clarity and discipline. That's very important. Right. Because otherwise we just end up doing all kinds of things and overloading our teams. Ramia, we're getting close to the end. Thank you very much for sharing all those stories. But before we go, where can people find out more about you and the work that you're doing?

[Ramya Shastri]

All right, they can follow me on LinkedIn. That's where I am, like, super active. And they can also follow me on YouTube because I have a YouTube channel and I have, like, as I mentioned, I have two podcast shows. They can probably find me on the podcast by Agile Coaching Roundtable, because that is related to the topic that we are talking about. It's about Agile Practitioner and Agile ways of working. Right. So that is where typically they can follow me.

[Vasco Duart]

Absolutely. Well, we'll put all the links to the show notes and the podcasts that Ramia hosts in the show notes as well. So, Ramya, thank you very much for your generosity with your time and your knowledge.

[Ramya Shastri]

Thank you so much. Vaspo, it was great talking to you.

[Vasco Duart]

One more week of the Scrum Master Toolbox podcast is over, but there's a lot more. We have to share. We have developed our own membership site where you find a community of active and engaged Scrum Masters. In this site you get access to exclusive content and get to interact with us, your podcast host, as well as the best Scrum Masters in the world. So join [e-mail] and keep this podcast free of advertising. See you next week for one more full week of Scrum Master tips and tricks. We really hope you liked our show, and if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum Masters know about this valuable resource for their work. Remember that sharing is caring.