Seeking for advice from Product Owner experts
I'm seeking advice or, if possible, a chance to chat at a specific time with someone who has extensive experience as a Product Owner—and if they're a Salesforce Product Owner (i.e., they have worked or are working as a Product Owner with Salesforce technology), that's even better. I have some doubts since the role is very new to me. I have the following questions:
- I've noticed in my current job that the Scrum Master moves bugs to the previous sprint. Is that valid in Scrum? I've always assumed that bugs should be moved to the next sprint; am I correct? When should bugs, issues, or user stories in general be moved to the previous sprint?
- My next question is: Does the PO have to be in all the daily scrums? The Scrum Master invites me to attend and participate in the daily scrums (every day) as well as in the solution design meetings with the developers—is that valid? As far as I know, the PO does not have to participate in the daily scrums.
- Another question I have is: What do you do as a PO in a sprint planning session? What do you tell the developers and the business? What is the procedure the PO should follow in such sessions—what should the PO say?
- Additionally, in the sprint reviews, how can the PO participate, and what should they say?
I’m a bit lost since I only have books that, in theory, offer little or no practical help. I’d really appreciate your help.
Thank you in advance.
Additional questions I have are:
- How do you as PO prioritize user stories, which user stories do you take from the backlog?
- Should a PO have admin rights for working with a specific technology they are working on as PO?
I've noticed in my current job that the Scrum Master moves bugs to the previous sprint. Is that valid in Scrum? I've always assumed that bugs should be moved to the next sprint; am I correct? When should bugs, issues, or user stories in general be moved to the previous sprint?
Since there is only one Sprint at a time, there is no "next" or "previous" Sprint.
The Scrum Master shouldn't be moving work between Sprints. The Product Owner is accountable for the Product Backlog and the Developers are accountable for the Sprint Backlog. If there is undone work at the end of a Sprint, it should be moved into the Product Backlog, appropriately reordered, and selected by the Developers for a Sprint.
What do you do as a PO in a sprint planning session? What do you tell the developers and the business? What is the procedure the PO should follow in such sessions—what should the PO say?
Much of the work should happen before the Sprint Planning - making sure that the Product Goal reflects the next step for the product, that the Product Backlog is ordered to support maximum value, that the refinement has been done and the Developers have a clear understanding of the Product Backlog Items.
At Sprint Planning, the Product Owner must ensure that the next most valuable step - the Sprint Goal - is clearly described. This could turn into a negotiation between the Product Owner and the Developers, since the Sprint Goal needs to be achievable within the Sprint and only the Developers can make that assertion. The scope of the Sprint Goal may need to be adjusted to make it achievable.
There's no formula for how to conduct a Sprint Planning. Different teams find different techniques to be useful.
How do you as PO prioritize user stories, which user stories do you take from the backlog?
There are many ways to order the work. However, prioritization alone is often insufficient. You likely need to consider dependencies and risks and order the work in a way that allows for reducing the risk of future work and being able to make changes in direction.
The Product Owner doesn't take work from the Product Backlog. Work is selected by the Developers at the Sprint Planning.
My next question is: Does the PO have to be in all the daily scrums? The Scrum Master invites me to attend and participate in the daily scrums (every day) as well as in the solution design meetings with the developers—is that valid? As far as I know, the PO does not have to participate in the daily scrums.
The Daily Scrums are by and for the Developers. The Developers can choose who to invite. For example, when the Developers are learning Scrum or need outside feedback, they may invite the Scrum Master to help coach them through or facilitate the event. The Developers may also find it helpful for the Product Owner to attend to get their input on any questions or for any planning. Regardless, the Developers make the decision.
Additionally, in the sprint reviews, how can the PO participate, and what should they say?
The participation of the Product Owner is up to the discretion of how the team decides how to conduct the Sprint Review. Since it is a conversation between the Scrum Team and the stakeholders, the Product Owner will participate. However, my experience tells me that the Developers should be comfortable talking about the work that they accomplished and how it supports the Product Goal and Sprint Goal.
Should a PO have admin rights for working with a specific technology they are working on as PO?
This greatly depends on the context. If this is helpful for a Product Owner to understand the product that they are owning, how stakeholders use it, and how to make decisions to maximize value, then yes. But there may be other ways to accomplish these goals.
I've noticed in my current job that the Scrum Master moves bugs to the previous sprint. Is that valid in Scrum? I've always assumed that bugs should be moved to the next sprint; am I correct? When should bugs, issues, or user stories in general be moved to the previous sprint?
Bugs should be fixed now. The work is not Done when defects are present. The Scrum Master ought to be encouraging the Developers to ensure their commitment to the Definition of Done is satisfied each Sprint.
My next question is: Does the PO have to be in all the daily scrums? The Scrum Master invites me to attend and participate in the daily scrums (every day) as well as in the solution design meetings with the developers—is that valid? As far as I know, the PO does not have to participate in the daily scrums.
What does the Scrum Guide say about who ought to be at the Daily Scrum? That's the truth on the matter.
Another question I have is: What do you do as a PO in a sprint planning session? What do you tell the developers and the business? What is the procedure the PO should follow in such sessions—what should the PO say?
The point of Sprint Planning is for the Scrum Team to come up with a Sprint Goal and a forecast of work. That Sprint Goal will mitigate a significant business risk or uncertainty. The Product Owner should make sure the Product Goal is clear, and that enough work has been refined and is and ready for consideration.
Additionally, in the sprint reviews, how can the PO participate, and what should they say?
Think less about saying and more about doing. The critical output of a Sprint Review is to have an updated Product Backlog. The Product Owner might reasonably share the current state of the Product in the market so this can be achieved.
How do you as PO prioritize user stories, which user stories do you take from the backlog?
You don't take any work from the Product Backlog, the Developers do, if that work would help them to frame and meet a valuable Sprint Goal. You would help them to identify what that valuable Sprint Goal could be. A Product Owner orders and organizes a Product Backlog so value delivery is optimized Sprint by Sprint.
Should a PO have admin rights for working with a specific technology they are working on as PO?
If they do, they are effectively one of the Developers. The Developers are the ones doing the work to build an Increment, and they should have all of the rights to get an Increment to Done.
A few points—good advice has already been given.
Moving bug tickets to a previous sprint sounds like a workaround and not transparent.
The Daily Scrum is for the Developers, and the Product Owner does not need to attend every session. However, it is beneficial for the PO to be available for any developer questions.
The PO represents the business and is responsible for determining which backlog items provide the most value. The backlog should be ordered based on what makes the most sense to deliver the highest value first. While backlog prioritization can be collaborative, the PO has the final say.
The PO explains functionality and acceptance criteria to the team but should not dictate how Developers build the solution. Instead, the PO supports the team by renegotiating scope when backlog items turn out to be larger than expected. Additionally, the PO can help Developers explore alternative functional approaches that are less complex while still satisfying business needs.