Podcasts about product owner role

Jean Coetzee: Breaking Free from the Proxy Trap And Reclaiming the Essence of the Product Owner Role Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Breaking Free from the Proxy Trap And Reclaiming the Essence of the Product Owner Role In this episode, Jean addresses some anti-patterns in the role of a Product Owner, with the most detrimental being when they become mere proxies for business owners or sponsors. He laments the recent disregard for the essence of the PO role, emphasizing that it should not serve as a mere intermediary. When POs are placed in proxy positions, they are set up for failure, relegated to the role of translators rather than empowered owners. Jean advocates for a reevaluation of the PO role to ensure they have the autonomy and authority necessary for success. The Bad Product Owner: Empowering Teams, Lessons from an Exceptional Product Owner In this episode, Jean shares a compelling story of a Product Owner who excelled without formal training in Agile or Product Ownership. This PO approached the role with a fresh perspective, free from preconceived notions. They embodied true ownership of the product, prioritizing vision-setting and supporting the team's end goal. The distinction between ownership and management was evident, as the PO focused on protecting the team from interference while also holding them accountable. Importantly, this Product Owner struck a balance by empowering the team to take ownership of their purpose, ultimately leading to a highly successful and self-sufficient team.   [IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate.   About Jean Coetzee Jean is passionate about humans, and how they work together from a psychology and neuroscience perspective. Jean, credits the early ScrumMaster podcasts for shaping his Agile career. These insightful episodes provided vital guidance during the early days, boosting confidence in serving others effectively. Jean learned to navigate uncertainties and gain confidence in their Scrum Master role, all thanks to this and other podcast contributors. You can link with Jean Coetze on LinkedIn. 

Gregory Miller: From High Performers to Demoralization, And How The Product Owner Role Can Destroy A Scrum Team Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. In this episode, Greg reflects on a team that self-destructed, causing him significant pain. The team, previously considered an exemplary high-performing unit, faced external factors and decisions that disrupted their dynamics. Leadership discussions about replacing their product, the removal of their Product Owner (PO), and a lack of support left the team directionless and demoralized. Greg recognizes the detrimental impact of removing the PO, highlighting it as an anti-pattern that ultimately led to the team's disbandment. This episode serves as a powerful reminder of the importance of providing support, direction, and maintaining team cohesion to foster a thriving and motivated workforce. Featured Book of the Week: "The Scrum Pocket Guide" by Gunther Verheyen In this segment, Greg talks about his most influential book for Scrum Masters, which is "The Scrum Pocket Guide" by Gunther Verheyen, a previous guest on the podcast. He highly recommends this book, as it has been invaluable to him in his role. Greg frequently refers to it and even keeps it on his nightstand for easy access. One aspect that stands out to Greg is Gunther's emphasis on the values side of Agile. The book delves into why the Scrum values are significant and explores their importance in the context of Scrum. Greg appreciates this focus on values as a fundamental aspect of Agile practices. For further exploration of the Scrum values, Greg suggests referring to the values section in the Scrum Guide. Overall, "The Scrum Pocket Guide" has had a profound impact on Greg's understanding of Scrum and serves as a go-to resource for him as a Scrum Master.   [IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM's that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!     About Gregory (Greg) Miller Greg is an Agilist and Coach who has been working in Agile software development for more than 10 years. He hosts The Agile Within podcast with Mark Metze (a previous guest), which promotes agile behaviors and mindset. He lives in Ohio with his wife and four children, two of which are twins. You can link with Gregory (Greg) Miller on LinkedIn and connect with Gregory (Greg) Miller on Twitter.

⏩ Join Ryan and Todd for a Scrum.org's course: https://buytickets.at/agileforhumansllc

Kirill Golubev: The Pitfalls of a Project Management Mindset in the Product Owner role Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Building a strong relationship between Scrum Master and PO, a critical contribution to the success of the team Kirill talks about how important it is for Scrum Masters to build a close understanding and trusting relationship with the product owner (PO), and how that relationship is critical for the success of the team. He emphasizes that if there is no chemistry between the Scrum Master and PO, it's better not to join that team. When there is good chemistry, the team will benefit much more from both Scrum Master's and PO's presence. Kirill also stresses that the PO needs to have guts and be clear about prioritizing the backlog. He warns against the anti-pattern of conflict between the Scrum Master and PO.  The Bad Product Owner: The Pitfalls of a Project Management Mindset in the PO role In this segment, Kirill shares why he thinks that the PO role is a cornerstone role in Scrum and without a PO, a Scrum team cannot even get started properly. We explore how POs that come from the project management field, often have a project management mindset, which hinders their ability to grasp the PO role. Kirill shares an example of 3 POs for one team who were new to the role and to Agile. The POs did not trust the team to self-manage, and wanted to control everything by telling the team what they had to work on, and when. We discuss how we can help the PO understand that it helps the team to trust and help them self-manage. We also refer to the concepts of Theory X and Theory Y and how, knowing about that can help the PO's understand their role as a leader.   Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate.   About Kirill Golubev Kirill considers himself an Agile and common-sense apologist. He wants to see simple processes in place, when people self-organize and manage themselves without constant push from management. You can link with Kirill Golubev on LinkedIn.

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Technical background is not necessary to be a great Product Owner! This PO had never been exposed to Agile, however this person wanted the product to be successful, and understood that software development was a team's sport! This PO, even without software development background was able to be open-minded enough to learn what was necessary, to collaborate with the team, and was open to getting help from the Scrum Master!  The Bad Product Owner: Helping PO's that didn't want to be PO's in the first place Sometimes, we work with PO's that did not want to be given that responsibility. When the PO is forced to take that role and work with the team, the conditions are rife for problems. There might be many reasons for this, including that PO is the next “logical” step for a technical person's career. In this segment, we talk about how Scrum Masters can help do “damage control” and help the team and the PO work together.  Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate. About Omar Perez Omar is an Agile Coach from Barcelona who currently supports distributed teams that build data products to enable their company to be genuinely data-driven. He has had many previous lives as a design thinker, market analyst, communication consultant, project manager and startup founder. He aspires to become a “peopleware” expert.   You can link with Omar Perez on LinkedIn. 

In this special Christmas BONUS episode, we cover some of the key lessons that Vasco collected throughout 2022. You get an insight into his lessons learned, but also the thinking process that led to them.  Listen in to learn about  The results of a change management poll for Scrum Masters and Agile Coaches, and what that says about our community  Product Ownership in 2022, and why the PO role needs a new approach in the Agile community Why the concept of Antifragile can, and should be applied to the work we do as Agile Coaches and Scrum Masters A BONUS reflection question for you to reflect on at the end of this year.  You can send your questions to podcast@oikosofy.com!    If you are interested in being part of a volunteer team that will be working on helping Product Owners during the year 2023, contact Vasco at Vasco@Oikosofy.com, and share why you'd be interested to be part of this work to help Product Owners!    About Vasco Duarte Author of http://NoEstimatesBook.com, and daily podcast host at https://scrum-master-toolbox.org/. I try to give back to the community every single day in an effort to improve the IT and product industry all over the world. Product Manager, Scrum Master, Project Manager, Director, Agile Coach are only some of the roles that I've taken in software development organizations. Having worked in the software industry since 1997, and Agile practitioner since 2004. I've worked in small, medium and large software organizations as an Agile Coach or leader in agile adoption at those organizations.

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: Curiosity, dedication and Vision, critical skills for great Scrum PO's Great Product Owners play a pivotal role in the success of Scrum teams, they define the Vision, and work to anticipate end user needs. But to achieve that, they - as Robbie puts it - “do all kinds of small things along the way”. In this episode, we discuss how this PO was able to put into practice some specific techniques that helped them define what needed to be done, while keeping a great relationship with the stakeholders, and keeping the trust by the team.  The Bad Product Owner: The many demands on the Scrum Product Owner role The Product Owner is a very demanding role, Robbie describes how this aspect is often misunderstood by people in the role. The demands of the PO role go far beyond the context of the product itself, and include many demands on the human relations and collaboration skills for the Product Owner.  Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate.   About Robbie Ross Robbie is an Agile Practice Manager at Jumar Technology with a passion for working with and empowering teams to foster an Agile environment at scale. He's also a Certified Scrum Master, Kanban practitioner and Agile community member helping teams release their genuine potential to deliver value. Quite a career shift since completing a Sports Science degree at University. You can link with Robbie Ross on LinkedIn and connect with Robbie Ross on Twitter. 

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Product Owner: The PO as a leader A great PO is also a great leader. As Nilesh puts it, it's not possible to disconnect leadership from the role of the PO, because that role is all about creating alignment, and autonomy in the team.  In this segment, we refer to the book: Flow: The Psychology of Optimal Experience by Mihaly Csikszentmihalyi.  The Bad Product Owner: The PO that had multiple responsibilities In this segment, we talk about a Product Owner that was not able to shield the team from the interference by external stakeholders, and what are the consequences we can expect from that anti-pattern. We also talk about how, sharing the PO role with other responsibilities can create other anti-patterns.  Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate. About Nilesh Makan Nilesh is the founding Director at Padawan Consulting, where the vision is to build transformed businesses through transformed people. He works with companies in the arena of Digital Transformation, considering how to leverage people, process and technology to design and build innovative solutions. You can link with Nilesh Makan on LinkedIn and connect with Nilesh Makan on Twitter.

In this episode, we will discuss the role of the product owner. Reference: https://scrumguides.org/scrum-guide.html#product-owner https://www.agilealliance.org/glossary/product-owner Taking the PMP Exam in 2021? Sign up for our boot camp: http://www.projectmanagementmasterclass.com/ Main site: http://praizion.com

The Product Owner role is often the most misunderstood and misinformed role in the entire Agile Framework. Join V. Lee Henson, president and founder of AgileDad as we discuss what the PO role should really be doing and why they should be the most revered role in your organization. 

Listen in as Jay Stansell and Victor Zanabria chat about Challenges of product owner role.To support the bushfire affected wildlife and communities of Australia that are mentioned in this episode head to bushfire.productcoalition.com To get pre-release access to all Product Coalition podcasts, product management mentorship, product management interview practice, and product management resume reviews, visit platform.productcoalition.comSupport the show (https://platform.productcoalition.com)Support the show (https://platform.productcoalition.com)

In this edition we will explore the Agile Product Owner Role and spell out a list of reasons why they should have your respect. We will discuss the folowing topics: PO Anti-Patterns, The Product Owner Triangle, Full Role Description, Product Owner Skills, Product Owner Qualities, Product Owner Attributes, and the supporting cast they need to get things done. 

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.  About Maarten Dalmijn Maarten is a Product Manager and Scrum practitioner who believes in 'less, but better'. By blending the world of Product Management and Scrum, Maarten helps teams beat the Feature Factory and uncover better ways of delivering value together. He has over 10 years of experience building products, and helped rebuild products as well as Agile Transformations as a leader and participant. He says: "Product management is about getting the right things done. It is easy to come up with a list of things to add to make something better. It is much harder to decide which things to leave out to make something better." You can link with Maarten Dalmijn on LinkedIn and connect with Maarten Dalmijn on Twitter.  Follow Maarten Dalmijn’s blog posts on Medium.

Recently, Dan received an email from a listener that posed an interesting question. In short, they said, “We’re doing alright every sprint and the business is doing alright too — we’re not really facing any competition. So, when the team asks, ‘Why should we continually improve?’ how can I help them through that scenario?” This is a great question! Though this team is stable, have been working together for a long time, and are doing well — they’ve reached a plateau.   When you dominate your market and you feel there is no competition there can end up being a serious lack of continuous improvement (especially if the barrier to entry is really high!) And it’s not totally unexpected that teams sometimes can get a little bit complacent — but it’s the Scrum Master’s job to challenge that. So, in today’s episode, Dan, and his collaborator, Sam Falco, will be answering this question and addressing how you, as the Scrum Master, can help remotivate your team to amplify what’s going well, shake things up, and make sure they’re all doing more of what they love!   Key Takeaways Why should you continually improve? In the case of competition (people may find an alternative to your company!) Because there is always something you can look to improve (even if things are going well you can always amplify that) How can you get your team to be interested in continuous improvement? What’s important to note as a Scrum Master or team leader? Watch out for change fatigue (sometimes it’s good to simply celebrate stability) Ask: “What could we try differently?” even if everything is going well (amplify what’s already going well!) Hold timeline retrospectives (i.e. with the team, plot the events that happened over a period of time and list them from most positive to least to see what people are feeling good or negative about) By looking back further than a sprint, you can do an exercise called a journey map for the last quarter (or as far back as a year) to look for trends Find the things that are going to be good for your team (i.e. a compelling interest beyond just the financials of the company) If some members of the team are bored with the work they’re doing, assign a new project or have them learn a new area of the business Work with the Product Owner on the question of: “What could we do to delight customers? What are they asking for?” using the Kano model Work with the Product Owner and coach them on the product road map/how to understand customer needs and creating more inspired product backlog items to fuel the motivation for continual improvement Look for ways to tap into your team’s intrinsic motivation (if you have a long-standing team it may be important to find out what motivates each individual member of the team [which could be autonomy, mastery, or purpose, according to Daniel H. Pink]) Remember that you are looking for the intrinsic motivators rather than the extrinsic motivators (which are things like time off or financial rewards) Try flipping the script; do your retrospective around: ‘What would destroy as us a team,’ ‘How can we mess up,’ and ‘What would make the next sprint a complete disaster?’ Identify somewhere that the team can go and lead the way by holding the vision and finding areas of improvement (i.e. lead more than serve) Be sure to keep in mind that change and improvement can take a long time Find a representative within the team of developers who is interested in continuous improvement to facilitate change, model the behavior, and lead through attraction   Mentioned in this Episode: Kano Model Drive: The Surprising Truth About What Motivates Us, by Daniel H. Pink Moving Motivators Cards Agile Coaches’ Corner Ep. 43: “The Importance of the Product Owner Role in Scrum with Sam Falco” Agile 2019 Conference Agile + DevOps East Conference “The Experience Trap” – Harvard Business Review   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.  Confidence is one of the symptoms you are in the presence of a good Product Owner, when you add to that the ability to articulate the reasons for the decisions made as well as using data and analysis to support decisions, we know we have a great PO working with us.  We also talk about the consequences from creating an implicit or explicit competition between Product Owners. The Great Product Owner: The confident and articulate Product Owner A great Product Owner will have a clear Vision of their product, but that’s not the only characteristic they exhibit. They can also clearly defend their Vision, using data, and analysis they’ve made. They intimately understand their product, business and customers. As they move away from “guessing” as a practice, they are not afraid to have difficult conversations about the product.  The Bad Product Owner: The Feature Owner anti-pattern Let’s imagine that your company creates an internal competition among teams and Product Owners. What will happen then?  We discuss the consequences on the PO role that Jim has witnessed.  In this segment, we refer to the work by Daniel Vacanti.  Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate. About Jim Sammons Jim is currently a Professional Scrum Trainer with Scrum.org and works with an amazing team at Insight as an Agile Coach and trainer for their clients around the world. His time as a Scrum Master was awesome and fueled his passion for agility at all levels. You can link with Jim Sammons on LinkedIn and connect with Jim Sammons on Twitter.

This episode marks the first anniversary of the start of the Agile Coaches’ Corner podcast! In celebration of this special mark, Dan Neumann and his collaborator, Sam Falco, are taking a look back at the very first episode: “Do Scrum Well Before Scaling!” They’ll be revisiting the topic — but from a slightly different angle this time: “What anti-patterns interfere with or prevent good scaling?”   Tune in to hear Dan’s and Sam’s anti-patterns around scaling in Scrum and some of their solutions on how to address them or stop them before they start!   Key Takeaways Anti-patterns that interfere with or prevent good scaling: Not having a sprint goal; not having one clear goal for the sprint that is understood by everybody (which ends up creating a laundry list of items that are not tied together which can create unrealistic expectations about delivery) Having two sprint goals (which causes a lack of focus) — “If you aim at two goals you won’t hit either of them!” That everything doesn’t have to be integrated or can be integrated after a few sprints (this can be a side effect of not having a clear sprint goal), which creates risk build-up If everything is not integrated, technical debt will bring things to a grinding halt and create a mountain of undone work A lack of automated testing and thinking you can build out the unit tests and automated functional tests later — because later might never happen or, by the time you get to it, the effort becomes far too large Team dysfunctions and anti-patterns that affect scaling: Not making the impediments visible — if you make the impediments and dependencies visible and communicate in-person this can be resolved fast! A common dysfunction in beginning Scrum teams is this concept that individuals own the product backlog items which leads to siloed work (which, in turn, can lead to not getting things done because the team takes on more than it can handle and cannot coordinate properly) Assigning stories to individual developers (when it is actually much more effective to leave the PBI unassigned or assigned to the Product Owner) Multiple Product Owners for an individual Scrum team (you only want one — but if there are multiple ones in a scaled environment they should be aligned!)   Mentioned in this Episode: The Scrum Guide Agile Coaches’ Corner Ep. 1: “Do Scrum Well Before Scaling!” Agile Coaches’ Corner Ep. 51: “Getting to ‘Done’ Within a Sprint” Agile Coaches’ Corner Ep. 43: “The Importance of the Product Owner Role in Scrum with Sam Falco” Scrum@Scale   Sam Falco’s Book Pick: Mastering Professional Scrum: A Practitioners Guide to Overcoming Challenges and Maximizing the Benefits of Agility, by Stephanie Ockerman and Simon Reindl   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.  Stanislava has shown a keen focus on people, and their interactions this week, and to finish off the week we talk about how to apply that focus in the Product Owner role. First as a learning process, and helping a team member gain trust in their abilities. Later we talk about the great Product Owner, one that was ready to listen to the team, and answer their questions. The Great Product Owner: Listening to the team As an example of a great Product Owner, Stanislava mentions the ability to listen. To pay attention to what the team needs, and to be available to answer questions when they arise in the team.  We also talk about how important it is for teams to ask questions, and how Scrum Masters can coach teams to learn how to ask questions from the Product Owner. The Bad Product Owner: Learning to be a Product Owner from scratch Sometimes the “bad” Product Owner, is a temporary situation for a team member that wants to take on a new role. In this segment, we talk about how we can help shy, and inexperienced team members learn a new role.  Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate. About Stanislava Potupchik Stanislava is not only a serious games facilitator and a team coach, but she also spends a considerable amount of time rock-climbing and hiking, traveling with her partner and son, and drawing zentangles. You can link with Stanislava Potupchik on LinkedIn and connect with Stanislava Potupchik on Twitter. 

This week, on the Agile Coaches’ Corner, your host Dan Neumann and his AgileThought colleague, Sam Falco, will be taking a look at the Product Owner role in Scrum! The Product Owner Role sometimes gets overlooked in a lot of discussions around Scrum — yet, they’re one of the most important, complex, and crucial roles. They’re the visionary behind the product. Primarily, their responsibility to the Scrum team is to maximize the value of what the development team creates.   Tune in to hear Dan and Sam’s conversation to get more insight into the incredibly important Product Owner role — what it is, the challenges of being one, the valuable traits and skills for a PO to have, and some of the anti-patterns around the role!   Key Takeaways What is the Product Owner Role in Scrum? It is one of the three roles of Scrum (product owner, scrum master, and the development team) They’re the visionary behind the product They’re a crucial reason to why we have Scrum teams in the first place — they’re feeding the Scrum team the most valuable backlog items to turn into an increment of product every sprint The primary role of the Product Owner is to maximize the value of what the development team creates It’s important that it’s only one person; not a committee Challenges of the Product Owner Role: Managing and representing the opinions and voices of the dev team and stakeholders by distilling them into a coherent product backlog that’s optimized for value Valuable traits for a Product Owner: Someone with a distinct understanding of the market and a vision for a product that they want to bring into the world An entrepreneurial mindset Someone with very deep domain knowledge and business knowledge Understands the customers (or potential customers) Decisiveness Open-mindedness Strong leadership skills and the ability to motivate others Important skills for a Product Owner to have: Domain and business knowledge The ability to write a good business proposal as well as a strong canvas that articulates to funders what it is you’re trying to accomplish A willingness to test your hypothesis and do market research Communication skills and articulating things in a way that makes sense to your development team Negotiation skills Having a well-crafted and well-ordered backlog Being able to define the sprint goal Being able to communicate the vision and having the organizational skills to put the backlog in a good order so the dev team, customers, and stakeholders always know what’s next Technical skills (though it is not a must-have, it is helpful for them to have an understanding of the technology they’re working with) — but be careful, a PO with technical chops can sometimes interfere with the dev team Anti-patterns within organizations that are not setting up their Product Owner for success: Having someone without the right traits and skills in the Product Owner role Having a proxy PO stand-in for the real Product Owner, which jumbles the message and leads to “answer shopping” Having the role split into two people (where one becomes the ‘business’ PO owner and the other person becomes the ‘technical’ PO), which affects team self-organization and leads to uncertainty Product Owner anti-patterns: Rigidity Disregarding estimates Product Owner is an ‘order-taker’; simply taking notes and doing everything that is said (which causes issues because they cannot articulate a clear vision) When a Product Owner is not valuing everyone’s opinions equally (and instead, giving more value to those who are loudest or had the last say) Presenting a release plan to stakeholders that is wildly at odds with what the dev team can accomplish and expecting the dev team to live up to that Unbalanced focus and either being too involved with the dev team or not enough Spending too much time with the stakeholders Only showing up for sprint reviews   Mentioned in this Episode: Scrivener User Stories The Professional Product Owner: Leveraging Scrum as a Competitive Advantage, by Don McGreal and Ralph Jocham Thinking in Bets: Making Smarter Decisions When You Don't Have All the Facts, by Annie Duke   Sam Falco’s Book Pick: Business Model Generation: A Handbook for Visionaries, Game Changers, and Challengers, by Alexander Osterwalder and Yves Pigneur   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Why is there a dividing line between the Product Owner Role, and the Rest of the Solution Team?  How do we run our interactions to honour that? The division is meant to enforce the freedom of teams to solve problems the best way they collectively know how This doesn’t mean the owner can’t have input, but the best way to communicate those inputs is as needs - requirements, stories, Definitions of Done, etc

Episode 13 of the Modern Agile Show features an interview with Melissa Perri and Matt Barcomb. We discuss issues with the Product Owner role, as defined by Scrum and explore the importance of product management and how to make product ownership a team sport.

  Moving from dev to Product Owner with your team is something that is quite difficult to do.  There are a bunch of new skills, hats, and behaviors you have to be ready to learn.  In this episode, we talk with Jamie Collins who has been on that PO journey for the last year about his experience and what he has been able to do so far. If you want to share your PO story with us please contact the show, we love having other people talk about their successes, learnings, and how they do the role differently.   Feedback: twitter - @deliveritcast email - deliveritcast@gmail.com   Links: Co-host Post - Looking for a co-host Jamie Collins -  @jamieuka Darshana Sivakumar - How I transitioned from being a developer to a product manager at Amazon Uptal Vaishnav - Can the Principal Software Engineer Assume the Product Owner Role on a Scrum Team? John Culter - Fixing Quarterly Planning Dave Thomas - Agile is Dead  

Hosts Ryan Ripley, Tim Ottinger, Mark Davidson Discussion Ryan Ripley (@ryanripley), Tim Ottinger (@tottinge) and Mark Davidson (@AgileDelivery) got together to discuss the role of the Product Owner (PO) and Product Backlog Management. Topics ranged from Minimum Viable Product (MVP), Story Mapping, Product Backlog Item creation, and what to do when the backlog becomes unruly. A key take away form this episode is the power and importance of a physical card wall. Having a space where everything known about a product or project is visible can make or break an agile project. Such an area gives teams the space to discuss, solution, and celebrate. The tactile nature of cards also has an impact on team members that a tool cannot yet replicate. Alignment is a great benefit of card walls, as is the ability to ask a basic question: “How do we know that this product / project is a good idea?” We wrapped up with the psychological impacts of a backlog on a team. And then…we called it a night. Will you help the Agile for Humans podcast grow? Please review Agile for Humans on iTunes or Stitcher and leave your comments on the blog site. Help your friends and co-workers find Agile for Humans by sharing your favorite episodes with them. Thanks for all you do to support the show. Agile for Humans is brought to you by audible.com – get one FREE audiobook download and 30 day free trial at http://www.audibletrial.com/agile Resources, Plugs, and More Ryan – https://ryanripley.com AgileIndy 2016 – April 12 in Indianapolis, IN Path to Agility Conference – May 25 & 26 in Columbus, OH Mob Programming Conference – May 1 & 2 in Cambridge, MA Tim – http://industriallogic.com 14 Weird Observations About Agile Team Velocity The Scrum guide Mark – https://www.linkedin.com/in/medavidson AFH 022 – The Product Owner Role with Mark Davidson Story Mapping: Discover the Whole Story, Build the Right Product by Jeff Patton The post AFH 030: Product Backlog Management with Tim Ottinger and Mark Davidson [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

The post MBA064: Transitioning to a Product Owner Role appeared first on Mastering Business Analysis.

Hosts Ryan Ripley, Tim Ottinger, Mark Davidson Discussion Tim Ottinger (@tottinge) and Mark Davidson (@agiledelivery) joined me (@RyanRipley) for a discussion about the Product Owner Role, #NoEstimates, Product Management, and the concept of “controlled disappointment”. The Product Owner (PO) role is near super-human. Shared responsibility is one approach to bring this role back down to earth. During this discussion we talk about the complexity of the PO role, the impact that the PO has on the project, and how developers and Scrum Masters can support the PO as they lead the team towards delivering a successful product *release*. And then…we called it a night. Agile for Humans is brought to you by audible.com – get one FREE audiobook download and 30 day free trial at www.audibletrial.com/agile Resources, Plugs, and More Ryan – https://ryanripley.com Slide deck from SDEC2015 Agile in a Flash by Tim Ottinger Tim – http://agileotter.blogspot.com/ Modern Agile post by Josh Kerievsky Product Owner's Maximizing Value Mark – https://twitter.com/agiledelivery The post AFH 022: The Product Owner Role with Mark Davidson [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

I have worked with Jim on and off over the past year and he is one one of those people you do not forget working with.  Enough said about that.Early on he had a lot of questions related to ROI Calculations and Business Alignment.  Over time he brought me closer to his view of Business Alignment and I convinced him that ROI Calculations were at best lies codified by rigorous technique.  It is always a pleasure when you learn from someone you are coaching.I think he is Agile for life...Time will tell.-bob payne