Bradley Pohl: how to help Product Owners and Scrum Teams collaborate in an Agile transformation

As we work with organizations in transition, we need to help teams and Product Owners make sense of the new ways of working. In this episode, we discuss how Scrum Masters can help Product Owners and teams find a way to collaborate when changing towards Agile. We share some tools that help large groups come together and learn to focus more on the impact they seek, rather than just the work they need to do.

About Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an “Agile Transformation.” As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

Bradley Pohl: how to work with a team of outside contractors

Working with a team of contractors can be a savior for some organizations. However, there are specific challenges that come with using “outsiders” to do significant projects in any organization. In this episode, we discuss one of the anti-patterns that come with teams of contractors: the lack of future outlook. We also discuss some of the important lessons Bradley learned and how to prepare for when you need to work with a team of contractors.

Featured Book of the Week: Drive by Daniel Pink

In Drive by Daniel Pink, Bradley found the 3 aspects of motivation that later helped him work with the teams he facilitates. In this episode, we also refer to Coaching Agile Teams by Lyssa Adkins and Mindset Growth by Carol Dweck.

About Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an “Agile Transformation.” As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

Bradley Pohl: how to help PO and team collaborate better

The relationship between Product Owner and the team is critical. So critical that if it does not work, it has the potential to derail the whole effort. In this episode, we talk about how to identify possible problems in collaboration between the team and PO, and how to help teams and PO’s collaborate.

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 Bradley Pohl

Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an “Agile Transformation.” As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.

You can link with Bradley Pohl on LinkedIn.

Jeremy Willets: The product owner that was the team manager

As usual on the Friday’s episodes, we explore Product Owner patterns and anti-patterns to help you work effectively with the Product Owner.

The Product Owner pattern for the week

This Product Owner was the manager for the team, but despite that, he was an effective PO. Listen in to learn how this PO stepped back to help the team contribute, and how he separated his PO responsibilities from his management responsibilities.

The Product Owner anti-pattern for the week

Product Owner’s personalities can have a big impact on the relationship with the team. In this episode, we explore what happens when the PO is self-centered and egotistical. We discuss the symptoms that indicate this anti-pattern and some of the things you may want to do as a Scrum Master to help the PO and team collaborate.

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 Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.

Jeremy Willets: using the Speed Car Retrospective exercise to host an impactful Retrospective

Jeremy explains the questions that he asks himself when evaluating his contribution to the team. As Scrum Masters, these are some of the many questions that can help us assess our work and improve our approach to help make teams successful.

Featured Retrospective Format of the Week: The Speed Car retrospective format

The Speed Car retrospective format is one of the many metaphor exercises that helps teams get out of the details of what happened and think about the impact those events might have on their performance, just like many aspects have an impact on a race car.

In this episode, we refer to the classic book: Agile Retrospectives by Larssen and Derby.

About Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.

Jeremy Willets: OKR rollout story in an Agile organization

OKR’s are a management tool that is gaining wide acceptance in the tech industry and other industries. The ideas are simple and should be simple to adopt, except they are not.

In this episode, we talk about what Jeremy learned about the roll-out of OKR’s at his company and how Scrum Masters can help adopt OKR’s the right way! Not a simple process.

About Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.

Jeremy Willets: how interruptions kill Scrum team effectiveness and efficiency

A team was given a new assignment. They would finally start developing a cool new technology that they had wanted to focus on for a while. They were assigned full-time to this new project. What’s not to like? Well… It’s never that simple. Scrum teams don’t exist in a vacuum, and soon enough the “old” work started interrupting the “new and cool tech project”! Listen and learn what happened to that team.

In this episode, we refer to the book: Principles of Product Development Flow by Don Reinertsen.

Featured Book for the Week: Kanban: Successful Evolutionary Change for Your Technology Business by David Anderson

In Kanban: Successful Evolutionary Change for Your Technology Business by David Anderson, Jeremy found that Scrum needs to evolve, and that following Scrum as such may not be the best option for you, or your teams. In Kanban, David Anderson answers the following questions:

  • What is Kanban?
  • Why would I want to use Kanban?
  • How do I go about implementing Kanban?
  • How do I recognize improvement opportunities and what should I do about them?

About Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.

Jeremy Willets: Component teams make you slow, are you paying attention?

How we set up teams has a direct impact on their ability to deliver. As Scrum Masters, we should pay attention to the early signs that something is going wrong. In this episode, we discuss the “platform team” anti-pattern, the dependencies that it causes and how we can raise the issue early enough to have an impact.

In this episode, we refer to the Marshmallow experiment blog post by Marcus Hammarberg, a great illustration that quick iteration with the result in mind can be much more effective and efficient for Scrum teams.

About Jeremy Willets

Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!

You can link with Jeremy Willets on LinkedIn and connect with Jeremy Willets on Twitter.

BONUS: Johanna Rothman and Mark Kilby share tips on how to help Distributed teams succeed

When Johanna visited Agile 2017, one of the largest Agile conferences that year, she was disappointed that the main advice people were giving on stage was: “don’t do distributed”. She then met Mark and started sharing her experience on how she had been able to make distributed agile work in her consulting work.

From that disappointment and both Johanna’s and Mark’s experience, a book was born: From Chaos to Successful Distributed Agile Teams: Collaborate to Deliver.

The most important lessons about making Distributed Agile work for your team

Continue reading BONUS: Johanna Rothman and Mark Kilby share tips on how to help Distributed teams succeed

Elena Popretinskaya: Scrum Product Owner anti-pattern and an example of a great PO

In this episode, we continue to ask the Product Owner question: examples of Product Owner anti-patterns, and examples of great Product Owners. We often get asked about what is a good Product Owner, and how to define the role so that success becomes clear. 

Elena’s example of a Product Owner anti-pattern is the “Solutionizer despot PO”, a Product Owner that always has the solution and replaces the team’s own thinking by proposing detailed solutions.

Elena’s example of a great Product Owner is someone that can bring Vision to the team. Help motivate and direct the team’s thoughts without imposing solutions.

Learn from Elena about how to tackle the anti-pattern, but also how to learn from the great Product Owner example to help your Product Owner succeed. After all, the team’s success depends on the PO’s performance!

 

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 Elena Popretinskaya

Elena considers herself a lifetime learner (she says, she absolutely loves having “aha!” moments). And she especially enjoys learning together with and from other people: her team and her friends. Elena is curious about everything: people, software craftsmanship and the world around. Elena is also a passionate hiker and a cross-country skier 🙂

You can link with Elena Popretinskaya on LinkedIn and connect with Elena Popretinskaya on Twitter.