Deliver It Cast

When it comes to knowing what’s most important, how does a Product Owner prioritize? Which methods do you use to find some way to talk about and rank them with the team and stakeholders? In this episode, we look at some different ways to do prioritization and some contexts in which they would be useful.  This is an activity that PO’s need to be really good at, so keep learning. Try something new!    

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

Des Traynor - Product strategy means saying no

Gerald Weinberg - Lullaby Language

Daniel Zacarias - 20 Product Prioritization Techniques

Steve Johnson - Quick prioritization

Rik Higham - Seven Simple Steps to Stress-Free Prioritisation

The latest offering from Geoff Watts is a great book for Product Owners about “Product Mastery”. Geoff offers some great insight into how PO’s can move from good to great through stories, examples, and some tried and true agile basics.  In this episode, Cory and Geoff talk about why the best product owners are DRIVEN to find success for themselves, the teams, and the customers.

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

Melissa Perri - The Lean Product Management Manifesto

Michael Sahota - Top 10 secrets of agile transformation

Geoff Watts - https://inspectandadapt.com/ - @geoffcwatts - @theagilepubcast

Geoff Watts - Product Mastery: From Good to Great Product Ownership

Having useful metrics is such a handy thing for Product Owners to refer to.  There are, however, a lot of useless ones out there that will make things worse for you and the teams.  Finding something that allows you to keep up with important information, trends, and areas to use your unfair advantage are wonderful to have.  PO’s can help the teams and stakeholders focus on a few key items to help drive successful ongoing delivery for your customers.

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

John Cutler - Trello, “Jira Sucks”, and Tool Dysfunction

Jeremy Jarrell  - 3 Ways Product Owners Can Help with a Great Sprint Planning

APN - Agile Podcast Network

Scrum.org - Evidence Based Metrics

Robert Boyd - 9 Scrum Metrics to Keep Your Team on Track

On our last 2016 episode, there are a bunch of Product Owner questions that need to be asked, and answered.  Thank you all for your support in helping us grow this year, the ability to connect with great people and share the best information to help along your way is why the show was created.  The show will return in Feb 2017 with new interviews, topics, and still focusing on the PO role.

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

Joshua Kerievsky - Customer Obsessed teams don't have product owners

Henrik Kniberg - Focus - Focus Keynote

Agile Contracts Book - Creating and managing successful projects with scrum

Getting valuable information in front of the Product Owner and other interested parties is a big key to success with agile. The easiest way to do that is to make it obvious and impactful where they are. An “Information Radiator” is anything that helps to accomplish that, it can be dashboards, burndown charts, or build status lights. Some of them are meant for the team, some are meant for stakeholders, and all of them need to be understood by the PO.  Helping to build them and support their existence is the topic of this show.

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

Melissa Perry - Designing to Learn

Roman Pichler - Mindfulness tips for PO's

Lachlan Heasman - What makes a good Information Radiator?

ScrumPLoP - Information Radiator

Giulia Mantuano - Visualizing Interruptions on a Lego Wall

The most frequent relationship a Product Owner has, is with the developers on a team.  Sometimes you don’t speak the same language ( business vs technical ) and need to find common ground.  In this episode, David Frink, an experienced agile developer and coach, joins the show to talk about how to strengthen that engineer/PO relationship, and tips on how to deal with some resistance from them. Looking for ways to engage and understand the team, this is it!

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

Ash Maurya - But will it scale?

Martin Eriksson - Things we learned at Mind the Product 2016

David Frink - Overcoming resistance how to engage developers in agile adoption

Thaler Pekar - Storytelling for engineers

Mikael Boman - Top 6 technical practices every PO should know

It should be a rare occurrence when a Product Owner needs to cancel and re-plan a sprint, but it does happen. How can you help the team decide what to do next and what part do you play in that activity? In this episode, we discuss some ideas on how to do exactly that with some examples of when Cory has needed to cancel a sprint before. Taking the step after that, what happens if you become so interrupt driven that you can’t plan consistently.

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

John Cutler - #agilebrandproblem

Amandah Wood - Spotify-How the team designs holistic experiences for music listeners and creators

Ed Wehr - The Sprint That Blew Up

Mike Cohn - Sprint Planning For Agile Teams That Have Lots Of Interruptions

One of the best resources for Product Owners is Roman Pichler’s blogs and books. His latest book “Strategize” is a great source of information about Product Strategy and Roadmaps. Roman joins on this episode to discuss some of those areas of his book as well as the ideas around how best to use that information. It’s part of the job for PO’s to be constantly learning, and Roman is a great teacher.

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

Roman Pichler - romanpichler.com & @romanpichler

Strategize - Strategize Product Strategy Roadmap Practices

Gregor Meyenberg - benefits-of-transparent-costs

Amy Morin - 5 things to remember the next time you're tempted to say yes to something you don't want to do

Luis Goncalves - NPS - Help PO structure Backlog

One of the first things a Product Owner should do when planning a sprint, is to determine what the goal of that iteration will be.  Will it be something to increase customer loyalty? Finally finish the promised feature so customers will use it? Or might it be to learn how to use a new technology? Setting the goal will help the team, customers, and stakeholders agree on the direction and focus for the next few weeks.  In this episode we dig into the “why” surrounding a goal so you can knock ‘em out.

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

Luis Goncalves - NPS - Help PO structure Backlog

Maddy Kirsch - How Product Managers can say "No"

Roman Pichler - Effective Sprint Goals

Barry Overeem - 11 advantages of using a sprint goal

Even though it’s not what should happen, sometimes you have to pull double, or even triple duty as a Product Owner.  It could be because of the size of the team or company, or that fact not everyone is “bought in” to the role the way it should be.  Someone still has to be the PO and if that’s you, how can you make the best of a bad situation.  In this episode, there are some ideas, tips, and strategies for handling multiple roles so you don’t lose control.

Feedback:

twitter - @deliveritcast

email - [email protected]

Links:

Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host

Nancy Duarte - Resonate

Michelle Pauk - Finding your Rhythm as a PO

Jennifer Yeadon - Should Scrum Roles Ever Be merged?

Mitch Lacey - Mixing Roles In Scrum