Viewing entries tagged
agile roles

Here we go again, picking on the poor Product Owner

Comment

Here we go again, picking on the poor Product Owner

Joshua Kerievsky recently wrote a post entitled Eliminating the Product Owner role. As of December 3, 2018, it had received 766 likes and 162 comments on LinkedIn.

https://www.linkedin.com/pulse/eliminating-product-owner-role-joshua-kerievsky/

The opening premise of Joshua’s article is here:

Before I get into who or what would replace the PO role, let me offer a bit of background on this group. Three coaches, including myself, had assessed this group prior to beginning work with them. Our findings were typical:

  • Too much technical debt was slowing development to a crawl

  • There was insufficient clarity on what needed to be built

  • The developers spent little time with their Product Owner

  • The team was scattered around a building, not co-located

  • etc.

When you perform numerous assessments of teams or departments in many industries, you tend to see patterns. The above issues are common. We've worked out solutions to these problems eons ago. The challenge is whether people want to embrace change and actually solve their problems. This group apparently was hungry enough to want change.

So, springing from this problem statement, Josh makes the point that if you: 

Comment

Mixed Feelings about Roles & Responsibilities

Comment

Mixed Feelings about Roles & Responsibilities

In our last Meta-cast, Josh Anderson and I explored the good and the bad around defining roles and responsibilities in agile contexts.

It’s a mixed bag really that requires some common sense and nuance. I think we landed on the need for them, but caution around the negative effects that they can have IF you’re trying to create a healthy instance of self-directed agile teams.

The Basics

One place to start is looking at the Scrum Guide and how it handles the Scrum roles.

Beyond the basic definitions of the roles, I really like the collaboration advice given BETWEEN the roles. I’ve found that it’s the interplay between the Team, Product Owner, and ScrumMaster that really makes the difference in high-level team performance.

I’d recommend you read (and share) the guidance in the Scrum Guide.

Comment

Back to the Role of the Product Owner vs. Business Analyst

1 Comment

Back to the Role of the Product Owner vs. Business Analyst

A few years ago I quantified the 4 Quadrants of the Product Owner role as a means of communicating the depth and breadth of the role. 

My intention at the time was to provide guidance to agile teams about the level of difficulty in performing within the role. I also had the intent to provide enough nuance so that Product Owners would realize that they typically would need help. That even though Scrum emphasizes a singular Product Owner per team (backlog), that more than one person might be needed to help fill all of the requisite skills and daily chores.

As part of the 4 Quadrants, I bundled the activities of a Business Analyst under the Product Owner role. It doesn’t mean that the Product Owner needs to be a Business Analyst. It just means that they have to either (1) have these skills themselves, or (2) have access to these skills within their team in order to effectively perform their job.

1 Comment