During the Sprint planning and after the crafting of the Sprint goal, the developers have opted out on some of the PBIs you proposed. All other selected PBIs for the Sprint are valuable and congruent with the Sprint goal. What should you do?

Enlist the Scrum Master for help to ensure that the developers respect your decision.
Force the developers to take on all the items that you proposed. Otherwise, the Sprint will not be complete.
Respect the decision of the developers as they are the ones doing the job. As long as the PBIs in the Sprint are the most valuable to reach the Sprint goal, you are fine with that.
Other items will come in next Sprint if still necessary.Let the developers have it their way but make sure that the remaining items get taken on mid Sprint.

Towards the end of the Sprint, the developers and yourself are debating if some of the Sprint Backlog Items where completed or not. The Scrum Master suggests to you and the developers to refer to the Definition of Done (DoD). Who should set up the DoD?

You as Product Owner as you have the authority to decide what is done and what is not.
The Scrum Master as he/she knows how Scrum works and what fit best in an Agile environment.
The developers as they are the ones doing the actual work of converting the Sprint Backlog Items into an Increment.
The Scrum Team unless the organization already has one. In that case, they should follow the Definition of Done as a minimum.

The developers in your Scrum team do not feel confident in presenting a working increment during the Sprint review. How should you react?

The Sprint review is a key event allowing inspection and adaptation. You enlist the Scrum Master's help to ensure that this event take place with the developers and other stakeholders in.
This does not hurt as you are meeting the stakeholders in separate meetings anyway to get feedback about the product. You leave it as is.
The Scrum team is self managing, you therefore have to respect the developer's decision.
You are fine with that as you have a very clear idea on how the product should move forward, stakeholders are optional in this regard.

The Scrum team is made of cross functional and self managing members. You have been working in a Scrum team for quite a while as product owner. In the last few weeks and due to time constraints, the developers started to work on ordering the product backlog items. A few stakeholders came back to you already and mentioned that they believe that the Scrum team has not been working on the most valuable items lately. What should you do?

You mention that the developers are now responsible for the ordering and that you will talk to them about it as soon as you have time.
As a Product Owner, you are accountable for the ordering of product backlog items. You apologize for this situation and free up some time to work with the developers on the ordering of the product backlog.
You address this issue to the Scrum Master so that she teaches the developers on how to best order the product backlog items by value.
The Scrum team is responsible for the ordering of the product backlog. If the developers are not doing it properly, it reflects on the entire team but you are not the only one to blame.

The team is coming towards the end of the Sprint (two days left) and the majority of the PBIs will not be completed. There is a real threat that there will be no increment to demonstrate. As Product Owner, what should be done?

The Scrum team self organizes. The developers have committed to the Sprint goal and need to figure out by themselves how to get those PBIs done.
You ask from every developer an extra effort for this Sprint.
You propose to extend the Sprint length by a week so that developers can complete the committed PBIs.
You review with the developers what are the key PBIs and the ones which could be removed from the Sprint in order to reach the Sprint goal.

You are working as a Product Owner in a Scrum team since a few weeks. During the current Sprint, the developers encountered some difficulties and after checking with the Scrum Master, they decided that the Sprint should be cancelled. Although the Product Backlog Items selected for those Sprints were challenging, the Sprint goal is still valid and you are available to answer any question that the developers may have. You are of the opinion that this Sprint should not be cancelled. What should be done?

Only the product owner has the authority to cancel the Sprint. You will therefore not cancel it but try to address the developer's concerns as best as you can and work towards the Sprint goal.
The developers are responsible for completing the work. If they are not confident in completing the Sprint, it should be cancelled and restarted anew.
The Scrum team decides if the Sprint should be cancelled. As the majority of the team think that it should be cancelled, the Sprint should be called off
The Scrum Master has the final authority on Scrum so if she supports the decision, you will go with it.

The Product Owner manages the Product Backlog. Who is accountable for estimating the effort to complete the Product Backlog items?

The Developers. As a collective, they have a complete view of the work needed to transform PBIs into Increments of product.
The PMO. They have all the history on projects delivered, and this enables the IT department to make delivery commitments.
The Product Owner. The Product Owner is required to commit on delivery to the users and the stakeholders.
The Scrum Master. The Scrum Master is supposed to get the estimates done from the Developers.

As product owner in a Scrum team, you started to create Product Backlog Items (PBIs) for your product backlog. You are unsure about the attributes that you should enter for each of those PBIs and plan to ask your Scrum Master. What should your Scrum Master tell you about the attributes of the PBIs?

That they can have as many attributes as required as long as they are properly estimated with Fibonacci numbers.
That they depend on the domain of the work and that as product owner, you are free to add whatever you think is fit.
That they should have an order, a title, a description and a size.
That they should be written in the form of user story with a requestor and a value stated.

Review Answers

Skillier

Skillier

Get In Touch

Resources

Featured

Policies

Trending Courses

2023 © Skillier All Rights Reserved

Skillier

Skillier

Get In Touch

Resources

Featured

Policies

Trending Courses

2023 © Skillier All Rights Reserved

🥳 Get an extra £25 off today by signing up for our emails 🎉