What makes us unique as Product Owners?
What defines and characterises each of us?
Together with my colleagues at Teletronics I have tried to characterise how we are different as Product Owners in our organisation in order to highlight the quality of variety. By identifying our differences the aim where to work better to support each other – something which is easy to overlook outside the traditional scrum team configuration.
You can read the first part of the blog below, and then continue the reading by following the links.
No two the same
Whatever your title, I’m sure you do your job differently than anyone else with that title.
What you focus on is the result of a combination of things: varying expectations (from boss, colleagues, self) or a preference for some specific tasks – probably those where you experience success more often.
Sometimes, you place your focus where you feel the need to improve.
Most important of all, you contribute where you feel your contribution is valuable. If there’s an unoccupied space that you think it would make sense for you to step into, you do it. You claim ownership of that space and do your best with it because you feel it’s the right thing to do at that time.
The choices of an Agile Product Owner
As a Product Owner in a truly agile organisation, you get to make a choice about where you want to place your focus at any given time and provide value to someone. One minute you are working within a development team and the next you are aligning with a customer, trying to make more sense of what value they are actually looking for. To build a useful network and gain more understanding of the product in full, you spend time in the server room with an admin installing hardware and deploying software.
The above tasks are all vastly different aspects of crafting software. All of those things need to be done to make it in our game, but nobody expects anyone to do all of it. That’s why we work in teams.
A team of Product Owners
We are currently 5 Product Owners working with each our product. Some products have overlaps and collaborative opportunities. Others don’t. Regardless, we can use each other and our differences to become better at our jobs and create better products.
Working in a team doesn’t apply only to developers, testers and devops:
That is why we are trying to be a team of Product Owners.
In forming ourselves as a team, we have discovered that we have vastly different interests, skills, experience and focus, which we can use to help each other and deliver more value, faster. Just like a team.
To get an idea of how we complement each other, we are working with identifying what makes us unique as Product Owners; what defines and characterises each of us. In addition, it’s also an attempt to show that none of those unique qualities are better or worse than any other. Rather, it’s to encourage that everybody benefits from us working as a team.
Continue to read about the different flavours of a Product Owner: