Nick Stewart: The Inexperienced PO and what to do to help them

From an inexperienced PO to a PO with a clear Vision, in this episode, we explore two totally different types of Product Owners, and we learn from Nick what worked in those cases.

The Great Product Owner: The Clear Vision PO

This Product Owner behaved like a great PO from the start of the project. The PO had a clear vision for the end result and was able to filter all the requests and requirements. From the team’s perspective, the process felt seamless. 

If it was only like this for all teams we work with. Listen in to learn what made this PO so productive and his approach motivating for the team

The Bad Product Owner: The Inexperienced PO

At one point Nick was working with a new and inexperienced Product Owner. This did not make things easy, and the anti-patterns quickly started to surface. 

It was a coaching challenge for Nick. In this segment, we explore the techniques and approaches that Nick used to try and help this inexperienced PO.

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 Nick Stewart

Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.

You can link with Nick Stewart on LinkedIn and connect with Nick Stewart on Twitter

Nick Stewart: Focus on people to define and measure success as a Scrum Master

When asking his own success questions, Nick prefers to focus on the people in the team and the team’s direct environment. He asks questions about how those people feel or act, and from that, he derives his own self-evaluation for the role of Scrum Master.

Featured Retrospective Format for the Week: The Sailboat Retrospective

There are many reasons why we prefer one or the other Retrospective format. And Nick’s perspective is no different. He has many reasons to like the sailboat retrospective format, and explains why in this episode.

Follow this link, if you want to explore how a previous guest used this specific sailboat agile retrospective format.

About Nick Stewart

Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.

You can link with Nick Stewart on LinkedIn and connect with Nick Stewart on Twitter.

Nick Stewart: 3 steps to help you improve your process

Nick shares the process a team went through to move from Scrum to Kanban. Their initial goal was not to move to Kanban, but through small steps and focusing on improving they found themselves using Kanban even without trying. 

Do you wish all change process would be this simple? Listen in to learn what steps Nick went through with the team.

About Nick Stewart

Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.

You can link with Nick Stewart on LinkedIn and connect with Nick Stewart on Twitter.

Nick Stewart: Why the Definition of Done is critical for Scrum teams wanting to be more predictable

This team that Nick was working with had trouble delivering on time. When Nick looked into it, he discovered that the team did not take into account all the work necessary to adhere to the Definition of Done. Once he found that, however, he had to work with the team to help them realize what was going on, and how they could become more predictable by simply taking into account what they had committed to: the Definition of Done criteria.

Featured Book of the Week: The Goal by Elyahu Goldratt

When reading The Goal by Goldratt, Nick had a lightbulb moment. In that book, the author describes the impact that one single aspect of work can have: throughput. 

The book describes how not paying attention to that aspect may destroy the ability to deliver value. 

In this episode, we also discuss The Phoenix Project by Gene Kim et al

About Nick Stewart

Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.

You can link with Nick Stewart on LinkedIn and connect with Nick Stewart on Twitter

Nick Stewart: What to do about the Product Owner that was changing priorities mid-sprint?

Nick was working with a team that had just lost their Product Owner. The new Product Owner had a conflict of interest and was changing priorities mid-sprint. This is a common anti-pattern that many teams face. 

In this episode, we talk through Nick’s efforts to help the Product Owner understand the consequences of his behavior. It’s never an easy situation to be in, but we must be ready. 

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 Nick Stewart

Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through the pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.

You can link with Nick Stewart on LinkedIn and connect with Nick Stewart on Twitter.

Sebastian Reverso: The PO who as able to be the Voice of the Customer

In this episode, we discuss two very different Product Owner patterns. We talk about a PO that felt their role was to be the voice of the customer, and the PO who felt the team was merely a “service provider” and they were the “outsider” who would demand service.

The Great Product Owner: The voice of the customer

This Product Owner had faced real customers. The PO worked previously in customer services and had to face the customer regularly. As she started working with the team, she was able to convey her ideas clearly, and from the customer’s point of view. At the same time, she did not interfere with the team’s technical discussion, letting them decide how the team would implement those ideas in practice.

The Bad Product Owner: The “outsider” PO

This particular Product Owner was stuck with the idea that the PO is not part of the team. That led to several problems. For example, the team would end up reporting “status” to the PO in the dailies and ended up trying to push more stories into the sprints. In this segment, we discuss how we can help PO’s that have that “outsider” perspective and how to get to a point when the PO feels like they are part of the team.

 

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 Sebastian Reverso

Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017. 

Among his favorite activities are mountain biking and football (soccer).

You can link with Sebastian Reverso on LinkedIn and connect with Sebastian Reverso on Twitter.

Sebastian Reverso: Liquid Organizations and how they help shape your Agile Retrospectives

Are you a Scrum mom? When assessing our own success as Scrum Masters, we must look not only at how the team performs but also how we get there. How we contribute to that team’s success. 

In this episode, we talk about some of the questions you can ask to learn if you are transitioning from that initial Scrum Mom role to an approach that allows the team to grow and continue on their own when you are not available.

Featured Retrospective Format for the Week: Liquid organizations, and how to adapt

When we reflect on our success or actions, we often focus on the task, and its success (or not). However, the way people contribute to the team may often be ignored. For example, a team member that is focused on helping others succeed may feel they are “not contributing”. In this episode, we discuss a different approach to retrospectives. An approach inspired by the concept of Liquid Organizations by Stelio Verzera, and that focuses on recognizing the contribution of each team member to the common success. Team members evaluate their peers’ contribution, so that the person who was focused on helping, may feel they contribute, even if they don’t work on many stories.

About Sebastian Reverso

Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017. 

Among his favorite activities are mountain biking and football (soccer).

You can link with Sebastian Reverso on LinkedIn and connect with Sebastian Reverso on Twitter.

Sebastian Reverso: Drawing people to change, instead of pushing change onto them

When introducing change to an organization, the way we present ideas and involve people become key aspects to our success. In this episode, we talk about how introducing ideas in different ways may have radically different results. We identify some approaches that have worked well, and we talk about the concept of “baby steps”, or relentless movement towards a direction. Finally, we discuss how to involve the team members directly in that process. As Scrum Masters we don’t need to tell the team what to do, they know. If they understand why the change is necessary, they can come up with the right steps.

About Sebastian Reverso

Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017. 

Among his favorite activities are mountain biking and football (soccer).

You can link with Sebastian Reverso on LinkedIn and connect with Sebastian Reverso on Twitter.

Sebastian Reverso: The Treasure Island Retrospective as a way to help team members empathize

As Sebastian started to work with multiple teams, he started to note some patterns of behavior that might cause problems. In this episode, we focus on the “professional jealousy” that some team members showed towards each other. We discuss how to detect it, and what the possible consequences of that behavior might be. Learn to detect it, and listen in to learn how Sebastian helped the team move forward.

In this episode, we refer to the Agile retrospective format: The Treasure Island, and to Solution Focused Coaching

Featured Book for the Week: Por Un Scrum Popular: Notas para una Revolución Ágile (Spanish Edition)

Por Un Scrum Popular by Mayer and Cyment is the Spanish edition of the popular: The People’s Scrum by Tobias Mayer

Sebastian found especially informative the aspects of the day-to-day Scrum that the authors go through, and how they compare what work looks like when using Scrum and when not using Scrum. 

In this segment, we also refer to the Scrum Master Toolbox Podcast episode with Claudia Toscano where the book “Por un Scrum Popular” is discussed in more depth.

About Sebastian Reverso

Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017. 

Among his favorite activities are mountain biking and football (soccer).

You can link with Sebastian Reverso on LinkedIn and connect with Sebastian Reverso on Twitter.

Sebastian Reverso: What to do when the Scrum team is facing big quality problems

When Sebastian took up the Scrum Master role, he did not expect to face the trial by fire he was about the experience. A few months into that new role, he was facing a situation where the application was blowing up everywhere. As the team pushed to release quickly, they didn’t account for all the technical problems or even some of the non-functional requirements they had to adhere to. As a developer-turned-Scrum Master, Sebastian had to learn the hard way how to help teams “divide and conquer” their work. We discuss how we can avoid similar problems in other teams, and some of the techniques Sebastian learned to help teams in that same situation.

In this episode, we refer to the Jassy’s episode where he also describes a transition from developer to Scrum Master.

About Sebastian Reverso

Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017. 

Among his favorite activities are mountain biking and football (soccer).

You can link with Sebastian Reverso on LinkedIn and connect with Sebastian Reverso on Twitter.