Kirill Golubev: The Pitfalls of a Project Management Mindset in the Product Owner role

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.

Kirill Golubev: How the Scrum Master’s Role Contributes to Team Success

In this episode, Kirill discusses the difficulty of measuring the value of a Scrum Master and how success is ultimately tied to the success of the team. He emphasizes the importance of paying attention to retrospective preparation and capturing concerns expressed by the team. Kirill measures his own success and that of the team by the value delivered to a satisfied customer.

Featured Retrospective Format for the Week: Making Agile Accessible and Using User-Friendly Retro Formats

In this segment, Kirill discusses the importance of using different retrospective formats depending on what the team wants to achieve and the inputs involved. He mentions examples such as the hot air balloon and sailboat retrospectives, which can visually illustrate the key principles of Agile and help the team reflect on how they implement those. Kirill emphasizes the importance of avoiding the use of hard vocabulary in retrospectives, and making sure that everyone, including those unfamiliar with Agile, can actively participate and benefit from the session.

Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!

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.

Kirill Golubev: A Scrum Master’s Insights on Being a Change Agent in the Pharmaceutical Industry

In this episode, Kirill shares the story of when he was a Scrum Master in the pharmaceutical industry, and learned some important lessons about being a change agent in an organization. He highlights the importance of having the team’s support and readiness when implementing any change. Kirill also emphasizes the value of training management to showcase the benefits of Agile to them.

Kirill believes that Scrum Masters have a revolutionary role in bringing change to the workplace and that it’s essential to define a Scrum Master vision and have a mentor to understand critical things that are necessary for success in the role.

As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.

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.

Kirill Golubev: When Conflicts Escalate, Lessons Learned from a Scrum Master’s Story of an Agile Team’s Self-Destruction

In this episode, Kirill Golubev shares the story of a team that entered an unresolvable conflict. It all started small, with discussions on what framework and technology to use for the front-end. One person suggested that the decision was not optimal, but this person was not the lead developer. The team had other developers who had been together for a while and felt very united, and they started to push back against this developer’s comments and disagreement.

Unfortunately, the situation escalated, and it led to nearly-physical confrontation. Kirill was not prepared to see the conflict grow that big, although there were other conflicts in the team that were positive and constructive. Even when he tried to address the topic in the team retrospectives, there were no specific action steps to address the conflict issue. Overall, Kirill’s story highlights the importance of addressing conflicts proactively, especially when there are disagreements among team members. It’s essential to have clear action steps to resolve conflicts and prevent them from escalating.

Featured Book of the Week: The Subtle Art of Not Giving a F*ck by Mark Manson

Kirill Golubev mentioned “The Subtle Art of Not Giving a F*ck” by Mark Manson as the book that most influenced him. He highlighted the Pareto rule, which states that 80% of the effects come from 20% of the causes, and in that context, he stressed the importance of being selective in daily work and identifying which actions bring the most value, which is similar to prioritizing the backlog for Product Owners.

In addition, Kirill emphasized the need to take the smallest step possible to deliver the most value, which is crucial in Agile. Overall, the book helped Kirill understand the importance of prioritizing and identifying the most valuable tasks, which is essential for Scrum Masters and Agile Coaches.

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 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.

Kirill Golubev: The Challenges with Scaling and Product Ownership for a Growing Scrum Team

In the podcast episode, Kirill Golubev shares a story of a team he was working with, which had grown larger. As they grew larger, they added a second and a third product manager. However, this led to constant fighting for priorities among the product managers. What was worse, the product managers were organized around components, rather than features, which caused even more conflicts, and delays in delivery for the team.

In this episode, we talk about the importance of having only one Product Owner working on the backlog. In that situation, the team adopted the Nexus framework to scale their approach to Scrum and created three different teams for the three different components. This was not optimal, but helped to avoid the biggest PO anti-patterns.

Finally, Kirill emphasizes the importance of building agreements between teams and Product Owners to ensure a successful outcome. Overall, Kirill’s story highlights the challenges that can arise when a team grows too large and the importance of effective communication and collaboration between Product Owners, Scrum Master, and teams.

Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story – How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.

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.

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