Paddy Corry: Enabling Scrum teams to learn faster from the feedback they get

Building on feedback is one of the key aspects of Agile teams. What happens when the PO’s either help or prevent teams from learning from feedback? We explore that question in this episode.

The Great Product Owner: Enabling teams to learn faster from the feedback they get

In certain projects, it is more important than usual to build on the feedback we get from retrospectives and Sprint demos. In this segment, we talk about a different approach to refinement, enabled by the Product Owner, that allowed the team to learn quickly and delay decisions that would otherwise cause problems. 

The Bad Product Owner: The Solutions-pushing Product Owner.

Product Owners who want to help the teams move quickly can sometimes focus on delivering solution descriptions instead of problem descriptions and letting the team come up with the solution. In this segment, we talk about the PO that wanted to help the team but ended up creating more problems by pushing solutions and removing the motivation the teams have to find their own solutions.

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 Paddy Corry

Paddy was a developer for many years, after which he started his Scrum Master journey with special interest for coaching and developing the agile mindset. 

You can link with Paddy Corry on LinkedIn and connect with Paddy Corry on Twitter.

Paddy Corry: Reflecting and requesting feedback as a way to grow into the Scrum Master role

When developers move to a Scrum Master role, they face a completely new set of expectations. Paddy reminds us that reflecting on that change is critical, as well as regularly requesting feedback from the teams we work with.

Featured Retrospective Format for the Week: Influence over what went well/not so well

In this segment, we talk about a classic retrospective format: “What went well, not so well”. Paddy adds a twist to that format, by adding a second dimension to each of the categories: “is this item under our control?” This raises some good conversations in the team, and helps teams that may be facing frustration from not being able to resolve some problems.

 

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 experiences: 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 Paddy Corry

Paddy was a developer for many years, after which he started his Scrum Master journey with special interest for coaching and developing the agile mindset. 

You can link with Paddy Corry on LinkedIn and connect with Paddy Corry on Twitter.

Paddy Corry: Overcoming resistance when adopting Scrum and communication tools

When teams are distributed over multiple locations, they need to overcome the problems that come with that situation. In this episode, we talk about how Paddy introduced a tool to help a team that was distributed, and what was the change approach he used to overcome resistance from other teams and the rest of the company.

About Paddy Corry

Paddy was a developer for many years, after which he started his Scrum Master journey with special interest for coaching and developing the agile mindset. 

You can link with Paddy Corry on LinkedIn and connect with Paddy Corry on Twitter.

Paddy Corry: Helping Scrum teams that are under schedule pressure

When teams feel they are under pressure, they tend to focus on “just doing it”. When that happens, they might want to skip refinement, and other ceremonies (e.g. retrospectives), which then leads to problems. In this episode, we talk about those pressures, where they come from, and what Scrum Masters can do to help those teams.

Featured Book of the Week: Flow by Mihaly Csikszentmihalyi

In Flow: The Psychology of Optimal Experience, by Mihaly Csikszentmihalyi, Paddy found the idea of psychological flow: when time melts away, and you can get a lot done. This helped him understand why it is important to block out time for deep work, and changed his approach to the role of the Scrum Master. 

In this segment, we also refer to a blog post by Paul Graham on the concept of “maker’s schedule”.

About Paddy Corry

Paddy was a developer for many years, after which he started his Scrum Master journey with special interest for coaching and developing the agile mindset. 

You can link with Paddy Corry on LinkedIn and connect with Paddy Corry on Twitter

Paddy Corry: A personal transformation from developer to Scrum Master

As developers, who move to a Scrum Master position, we usually face some conflicts between how we used to work, and what the Scrum Master role demands from us. 

In this episode, we talk about the transformation that Paddy went through from a developer to a Scrum Master. As he puts it: “At some point, you need to decide: you can either make great things or you can make things great”.

About Paddy Corry

Paddy was a developer for many years, after which he started his Scrum Master journey with special interest for coaching and developing the agile mindset. 

You can link with Paddy Corry on LinkedIn and connect with Paddy Corry on Twitter.