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.

You are the Scrum Master. The Sprint will complete in two days. Each day of the Sprint is equivalent to 8 hours. The team has just enough time to complete all tasks in the remaining 16 hours with the exception of three tasks. Of these three tasks, two tasks (a total of 6 hours) are required to complete one Product Backlog item and one task (an estimate of 2 hours) is required to complete another Product Backlog item. How should the development team handle the remaining three tasks?

The development team should negotiate with the Product Owner on the definition of "done".
The development team should work the extra 8 hours to complete their commitment to the Product Owner
The development team should place the two Product Backlog items back onto the Product Backlog
The development team should keep the three tasks on the Sprint Backlog for the next Sprint and complete those tasks first

You are in the Sprint Planning with the developers and the Scrum Master and have agreed on the Product Backlog Items which will be part for the Sprint Backlog. The Sprint goal need to be established before the planning end. Who should set this up?

The Scrum Team as it is a collaborative effort to craft the Sprint Goal
You as Product Owner as you own the Product and set the vision
The Scrum Master as he/she is responsible for the team's efficiency
The Developers as they are the ones who have to do the work

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.

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.

Select the correct timebox for each Scrum event

Sprint Planning - 4 hours, Daily Scrum - 15 minutes, Sprint Review - 4 hours, Sprint Retrospective - 4 hours.
Sprint Planning - 4 hours, Daily Scrum - 15 minutes, Sprint Review - 8 hours, Sprint Retrospective - 4 hours.
Sprint Planning - 8 hours, Daily Scrum - 15 minutes, Sprint Review - 4 hours, Sprint Retrospective - 3 hours.
Sprint Planning - 8 hours, Daily Scrum - 30 minutes, Sprint Review - 4 hours, Sprint Retrospective - 3 hours.

More than one Scrum Team is working on a single project or release. How should the Product Backlog be arranged?

A separate Product Backlog is constructed for each Scrum Team. All of the increments are integrated at the end in an integration Sprint
All Scrum Teams work from a common Product Backlog and integrate their work every sprint
Only one Scrum Team should work on Scrum project
Scrum Teams should have their separate Product Backlogs

Review Answers

Skillier

Skillier

Get In Touch

Featured

Policies

2023 © Skillier All Rights Reserved