How do you handle backup for the Product Owner role in your companies?
I'm still looking for a community to talk to. I'm in a mid-sized company that has very few people on the dev team: two architects, two other "developers" who unfortunately don't have strong programming or technical skills, and one of them is slow when it comes to developing certain topics. Two external consultants were hired, and later another one from the same consulting company. One of them is more available than the other two but doesn't code—he knows declarative stuff in Salesforce, including flows. The second one knows how to code and handle more technical topics, but he's only available two days per two-week sprint, and the third one is often on sick leave.
These consultants have contracts until the end of December, and even though I’ve shared my opinion with the manager of the development operations team (which includes the Scrum Master, who isn’t a developer but acts as a coordinator), the manager is closed to any changes and always gives the same response: “But the tickets are being prioritized, right?” Well, that’s one issue—but what I’d really like to know in this thread is: how do you handle this in your companies in your roles as Product Owners? If you go on vacation or get sick, who usually acts as your backup?
The Scrum Master often refers business stakeholders to me with ticket-related matters, saying “you have to talk to the Product Owner.” On her end, her backup is a “developer” who doesn’t know how to code. So I feel like I don’t have an official backup. The last time, I asked the Scrum Master to please invite the business (key users) to the Daily meetings so they can stay informed on the current status of their tickets—since I don’t have a backup.
The Product Owner is the authoratitive voice regarding the Product. If he or she wishes to appoint a suitable "backup", that's all it would take for the matter to be official. The PO could delegate the doing of their job to the office cleaner if they really wanted to, but the Scrum Guide makes it clear that the PO would remain accountable.
Would you say that you are fully accountable for value in your situation, and are the authoratitive voice of the product, and that this is clear to others?
Wow, the more you post the less I would want to be employed at your company. I'm sorry.
Since your company seems to refuse to allow any kind of cross knowledge within groups, it seems your best bet would be to ask one of the other Product Owners if they could "cover" for you while you are out or sick. Make a deal with them that you will do the same for them. Then the two of you can cross train each other to the point that you should be able to cover each other for short periods. That way you are not violating the "cross knowledge" rule that your management seems to have.
Prioritization is not the ideal way to manage a Product Backlog. I have worked in backlogs where the highest priority item in the list could not be done because there was no technology available to do what is being asked. This was because some salesperson asked someone they were trying to close a deal with what it would take. The perspective client took advantage of that and asked for something that would have been great but was not technically possible because that technology did not exist. It still does not exist and this was about 8 years ago when it occurred. Ordering the backlog in a manner that most efficiently uses the team members time and delivers immediate value, even if very small, to the stakeholders/users is the better thing. It ensures that the money being spent by your organization is helping bring in profits that make the company able to survive. So, the next time your manager asks if the backlog is being prioritized, take the time to explain that it is being managed appropriately. If you need to, use my story and feel free to make it your own.
Good luck.
“developer” who doesn’t know how to code.
This does come across as a bit antagonistic without knowing the full context. Some are stronger than others, but arrange for training or upskilling via peer programming techniques or learning workshops.
On the question of a PO backup - yes, absolutely. It is a good idea to arrange for someone to stand in during leave, ideally arrange prior cross-training to ensure continuity.
By the way I won't recommend inviting the business (key users) to the Daily meetings. The daily standup meetings are for the developers, it is their meeting. Having the business key users there will only discrupt the daily stanup meeting for the developers. Definately the Sprint Review is the meeting that the key business users and other stakeholders can attend. If further alignment is needed, additional conversations can be arranged outside the Daily Scrum.