With this in mind, the follow up session has a focus on what is product ownership, who makes a good product owner and the value of having one dedicated product owner.
As I am going to be going over in detail some of these points with my client this week, I thought that I would share with you some of my key thoughts on product ownership.
- Are responsible for the product, but this doesn't mean that they should be afraid or too proud to ask for help.
- Are part of the team - they should feel part of the development team.
- Are not "the boss" of the team.
- Are there to make the life easy for the development team. I try my best to constantly remind my team this!
- Need to be close to their stakeholders.
- Need to have an interest in technology (or whatever sector your product sits in).
- Must make brave and sometimes unpopular decisions (try telling your CEO that they cannot have a feature that they love!).
- May not be appreciated by the organisation at first (especially organisations new to SCRUM, agile etc) but must celebrate their successes in order to earn respect.
- Should not pass the blame.
- Are critical to the success of the product.