Product Owner experiences on a third grade level. Whether you are new to scrum, agile, lean or any rapid development method, I cover insights and thinking patterns that hopefully make sense. Don’t let the audio from the first couple of episodes run you off. It gets better I promise. Join me for a practical approach to being a product owner. Don’t forget to subscribe and check for new episodes. Topics and questions from listeners are becoming more frequently shared. Give feedback via email! firstname.lastname@example.org And now you can support me using Venmo J-G-1-222 or Cash App $jsgscott
After a wildly successful episode last time, I have put together a few items and topics to follow up on for a product owner and your leadership in a scaled agile framework. But this episode may be a difficult conversation for organizational leaders who are considering moving toward that framework. There’s a lot of defense for the product owner that is often overlooked..which is a totally different episode.
Are you a product owner who has come from a single development initiative or a single project-based mindset and new to a scaled agile environment? If so this episode may be for you. This comes from a question submitted by a listener! Do you know how I love those LOL. Today we talk about the product owner and how to make some adjustments coming from your microcosm into the new macrocosm of scaled agile! I will explore some risks and some opportunities for you! This is a rather long episode But it has a little bit for everyone. We’ll talk about why we scale agile, what to expect at least a little bit, and what you bring to the table. I hope you find this helpful in navigating your new journey and adding value. Thanks for your emails, thoughts and prayers as we have made it through hurricane Sally on the Gulf Coast! I’m glad to be back and sorry for the delay.
This episode has a very important announcement in the first segment that I don’t want you to miss! The topic today is one from a listener who asked about moving into a product owner role from a QA role. Well maybe the jump seems impossible, but I’d like to share with you some good traits that will make you a great product owner as well as some bad traits that you just need to leave before making the jump. I discuss good qualities you have, ones to fix then provide a little insight to get yourself moving. This episode is not targeted to a specific audience. I think organizational leaders, product owners, scrum masters and team would benefit from this episode.
As a result of a recent topic posted on social media, I would like to give my thoughts on why we shouldn’t do away with the product owner role. This episode should give you some insight and clarity for not only to the role itself, but how you can maybe address some of those objections if they come to you from this trending topic. Email me at email@example.com. I’m also happy to accept donations if you are enjoying the cast and finding it helpful! Venmo: @J-G-1-222 and Cash app: $jsgscott
Hey product owner! Do you suffer from routine, boring and check the box daily scrum’s? Hey scrum master have you laid down the law or had it given to you for the daily scrum structure? And hey dev team are you bored with having to go to this “meeting” everyday? Let’s talk a little about the daily scrum, shall we?
Part one of a possible series. You know how it feels when you are the new team member and as a youngster and new product owner, you want to learn the ropes as soon as you can so you are gaining respect. Nice user story, huh? Today we talk about some of the intangible stuff you need to know when starting new relationships with the new role. Welcome in!
This is one that you may want to miss if you are an organizational leader, product owner, scrum master or any agile dev team member. Let’s talk about adopting these frameworks like SAFe or scaled agile and talk about how they may work and more importantly why they may not work. I’m likely stepping on toes but I’m definitely speaking for the teams here. But they are at the center of your adoption and your execution.
What does it mean when we talk about inception, elaboration, construction and transition? The product owner needs to adopt some ownership in these areas but probably needs to know the basics first. This episode gives an overview of these phases and how they relate to some of your frameworks or even stand alone features. Glad to be back!
I know. Its light hearted and kinda fun but we discuss points and relative estimation. Don’t miss the point about points. I wanted a light topic ahead of next week. It’s the calm before the storm. The episode next week is gonna be one you don’t want to miss but you may not want to hear.
Conflicting priorities usually stem from conflicting feelings about the priorities. Everything is a priority. Everyone’s thing is the highest priority. This episode provides some tips and tools on balancing the priorities and gives some examples of how and when to handle potential outliers.
Another non-solicited question from a new listener! How does the Product Owner know they have the priorities right?! It’s a big responsibility for sure. In this episode, I give one example on how to make sure you’re on the right track. Let’s talk roadmap, product backlog, valuable and potentially shippable work, and leverage a little thing called a sprint goal.
I love it when listeners ask for topics! I was asked to backup a little and talk about the Product Owner and the backlog a little more at a high level. This episode gives some insight into not just the role but I also share some basic but effective tips about how I manage a large product backlog and communication strategies that have proven to be helpful in the journey. This episode is a little longer than usual so hang tight!
I didn’t say “no”. I said “not right now”. You need some rules of engagement to determine the next steps in your roadmap as requirements change or even while planning it. I would love to share some experiences I’ve had with this and three questions I ask before we commit to that path.
Talk to me like I’m three years old. Let’s get some basics cleared up before we get too deep. There are three fundamental outcomes and purposes of scrum. Iterative development • Self organizing teams • The shippable product. Let’s talk about some ways the Product Owner can help promote these.
I hope I have listeners after this episode...Let’s have some difficult conversations about some difficult things we deal with as product owners. I think we need to have difficult conversations in order to grow. This is an episode you may not want to hear, but it is one you need to hear. Responding to change doesn’t mean reacting to change
Listener question here. “I need a plan for my new gig”. This episode gives you some tactical moves that will put you on a nice journey. This one could apply to anyone in an existing or new role on the scrum or agile team. So if you are taking a new product owner, scrum master, dev team or even agile coach role, this is for you!
Today’s episode we have a reading, from the Scrum Guide along with some tips and tricks for a more effective Sprint Planning ceremony. I’m offering a little insight on how to prep for it more than the actual ceremony facilitation in this episode. Enjoy and welcome to season 2!
Let’s check out some fundamental guidance for scrum masters and product owners to work together on the team. This is kind of an intro to basic rules, antipatterns and solutions. Season 2. For real y’all. firstname.lastname@example.org
I’ve identified three types of Product Owners in this episode and tips on moving up in your journey. We are on a journey...applying some practical thinking patterns to develop the art of becoming a more effective product owner. This could be my last agile or scrum product owner podcast episode of this year. Subscribe, share and scrum. Send feedback to email@example.com
Let’s identify who needs to help prevent it. What to do if we have it. And how we can prevent others from getting it. This is not all encompassing. Just a few factors and a few players. But some good tips. Email me at firstname.lastname@example.org as always with your feedback!
Please tell me it’s not a check the box meeting that you are having or not having at all. The retro is a crucial time for the team to work ON the work and not IN the work. This episode outlines some of the good, bad and ugly about retros. Teasing the last segment for organizational leaders to listen in.
Many times we are in an anti pattern and we may not realize it. We have to back up and inspect and adapt ourselves sometimes. In this episode I share some of the top anti patterns I’ve seen, done and fought hard against. Hope you aren’t in these, but you may not even know if you are.
Are we inspecting and adapting our ceremonies? If your demos are boring, uninspiring or routine you should spice them up. Id like to share 5 things to incorporate into your demos to help you with a different perspective.
Today we dive into some ideas to help you with the inherent tasks of release communications and transition. I also offer some encouragement to you today because you guys need some love. Be sure to subscribe and tell a friend who may gain some value from listening!
So we are on the journey! This episode I share some feedback and questions from a listener. Let’s see how his user stories are written and how it has helped his team. Next I hope I answer his question about managing different work types in one big backlog. Like bugs, debt, features etc. Remember it’s about real world solutions and thinking patterns for Product Owners on the journey! Scrum masters are obviously welcome!
Often times we get cornered into following the formats dictated to us when it comes to our organizational processes. Sometimes we get in a rut and don’t progress as we should in writing effective user stories. Some of us even miss the point and don’t even know “why” we even use them. Let’s talk about that, shall we?
Ok so we walk out of the big session with the big document and we have a big task. Let’s recap a minute about the risks, value, obstacles and metrics first. Then we need to actually figure out how to make this thing real to solve the need.
Ok so I’m back from an unexpected personal break to recap the last episode and finish up some ideas about bridging the gap between traditional language and lean thinking. I give away a few secrets in this one that I think you will enjoy. I love it when science and art play together!
This is part one of three parts. We are talking about how to interpret the large document with the right questions. We speak a different language and we just need to acknowledge it, embrace it and build a bridge that works.