Product Owner Summit EARLY BIRD tickets expire soon! Get them now!

Get your EARLY BIRD ticket now!

Caterina Palmiotto: The Phantom Product Owner, How Lack of Decision-Making Impacts the Team and Kills Innovation

The Great Product Owner: The Collaboration Between PO and Team as Key to PO Success

In this segment, Caterina shares a story of a great Product Owner who worked closely with their team. The PO took the time to share the high-level vision and timeline for a new module, collected doubts and comments from the team, and presented user stories with enough information to start a discussion. The PO listened to all suggestions and was available every day to collaborate. The refinement process was done in two parts, with the second part focused on investigating technical aspects. The PO even participated in retrospectives and worked with the team to improve the product based on either technical or functional ideas by the team. Caterina emphasizes the importance of building this kind of productive collaboration between POs and their teams, with the help of Scrum Masters.

The Bad Product Owner: The Phantom PO, How Lack of Decision-Making Impacts the Team and Kills Innovation

In this segment, Caterina talks about a Product Owner who only wrote user stories but was unable to make decisions. The Product Owner always needed to report to his boss, which caused a delay in decision-making. This led to delays in the team’s work, resulting in not completing the story in the sprint. Additionally, the team lost trust in the PO, and did not have enough information or support from the PO to bring their contribution to the product through technical innovation. Eventually, the team started to make decisions on their own and stopped suggesting ideas to the PO. Caterina emphasizes the importance of Product Owners being able to make decisions and not causing delays in the team’s work.

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 Caterina Palmiotto

Caterina started as a software developer but soon realized that she was passionate about team dynamics and communication, and embraced agility from the moment she saw it.

Caterina believes a team can be more than the sum of its parts and that growing the right culture is essential. When people are surrounded by good examples they will be motivated to do their best.  So the first step is doing your best to be a good example of the culture you want to nurture.

You can link with Caterina Palmiotto on LinkedIn.

BONUS: Ryan Jacoby on the 7 responsibilities of an innovation leader

Innovation is a topic that gets a lot of attention. There are innovation processes, specific creative games for teams to work with to seek innovative ideas. There’s the Lean Startup movement that tries to codify innovation-friendly processes, and there’s also the UX community pushing the argument that we need more innovation in software companies.

You’ve probably heard the same argument at work. We need to be more innovative to be competitive. Great! But how?

In this episode, we explore how leaders can set up their organizations for innovation. Ryan Jacoby helps us explore the how of that critical question: how can we be more innovative?

Ryan has written a book titled Making Progress – The 7 Responsibilities of an Innovation Leader to describe how organizations can focus on enabling innovation in practice.

The first action you, and your organization need to take

Ryan describes an approach that aims to focus on the team and organization on the customer needs. His approach is simple and immediately actionable. First start by jotting down in plain language and from the point-of-view of the user/customer: what problems are you trying to solve for that customer? Select the top 3.

The other dimension of innovation is your organization’s goals. Define what it means to meaningfully grow the impact of the organization over 6 to 18 months. This growth could be in the number of customers, revenue growth, profit, etc.

Now you have the start of a growth strategy that is centered on customer needs and also directly linked to the company’s/organization’s growth. Next, we talk about innovation in practice.

The 7 responsibilities of an innovation leader

When it comes to putting innovation in practice, Ryan argues that there are 7 areas to take into account.

  1. Define progress for your organization, in other words: what is the impact you seek and the growth in that impact factor
  2. Set an innovation agenda by prioritizing the innovation problems to solve, user and customer groups you want to serve, nature type of innovation to pursue.
  3. Create support teams that build the product
  4. Cultivate the ingredients for success for innovation
  5. Giving great feedback to teams: prepare and setup the feedback moments so that teams can learn quickly.
  6. Inspire progress
  7. Reward progress (as defined in #1)

Ryan explains how he came to value these 7 responsibilities of an innovation leader by telling us his own story when he was responsible to help the New York Times grow their impact through innovative solutions.

Ryan’s book: lessons learned about each of the 7 responsibilities of an innovation leader

You can read more about Ryan’s work and find his detailed explanation of the 7 responsibilities of an innovation leader in his book: Making Progress – the 7 responsibilities of an innovation leader.

 

About Ryan Jacoby

Ryan Jacoby, is the founder of MACHINE, a strategy, and innovation company that helps its clients Think Big and Act Small.

MACHINE clients over the years have included people responsible for growth and innovation at The New York Times, Marriott, Viacom, Etsy, Google, Nike, The Washington Post, Feeding America, Fresh Direct, NBC Universal, and The Knight Foundation.

Prior to founding MACHINE, Ryan led teams and relationships at the design and innovation firm IDEO. He was a founding member and location head of the IDEO New York office and built the Business Design discipline at the firm.

Ryan is also the author of the book named “Making Progress” with Sense and Respond press. A book he describes as “a tactical guide for you, the person charged with leading innovation”

You can link with Ryan Jacoby on LinkedIn and connect with Ryan Jacoby on Twitter.

For more on Ryan Jacoby’s work, visit his company’s site at Machine.io.

Claudio Perrone on why the daily meetings fail

Daily meetings fail for many reasons, and Claudio has an idea of why it happens regularly. The 3 questions in the Scrum daily just can’t work in all situations. Claudio discusses some ideas on how to improve the questions the team asks in the daily meeting and gives a few tips on how to improve the Scrum board to make work more visible and focus the team on Flow.
We also discuss a promising framework to help teams understand the “why” of every story they develop. This is a framework developed based on the work by Clayton Christensen (Innovator’s Dilemma), and tries to define the content of products from a different perspective: the job to be done that customers hire the product for. Watch Clayton Christensen present the idea of jobs to be done on youtube. Or listen to the Jobs-To-Be-Done radio podcast if you want to know more about this promising framework.

About Claudio Perrone

Claudio is an independent Lean & Agile management consultant, entrepreneur and startup strategist. You may know him for the amazing cartoons he creates for his presentations or, perhaps, for A3 Thinker, a deck of brainstorming cards for Lean Problem Solving. These days he focuses on PopcornFlow, a brand-new continuous evolution method for personal and organisational change.
You can connect with Claudio Perrone on twitter, and see Claudio Perrone on LinkedIn. These days Claudio is focusing on his latest work: PopcornFlow, a method by which you can Learn how to establish a continuous flow of small, traceable, co-created, explicit change experiments. For you, your team, your organization.

Get The Booklet!
How to deliver on time and eliminate scope creep By scoping projects around outcomes and impacts, not requirements!
Get the Product Owner Booklet!
Avoid scope creep! And learn to scope projects around impacts and outcomes, not requirements!
Get These Valuable Lessons Today!
Down-to-earth, hard-earned Scrum Masters lessons and the Tips from the Trenches e-book table of contents, delivered by email
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works