PSPBM – Quiz

Explanation
Definition of Ready can help the Scrum Team understand how a Product Backlog item is deemed to be ready to be worked on, which means refined, and ready to be pulled during Sprint Planning. It helps create understanding amongst the team, considering the boundaries of the item and its attributes, but it is not a contract or definitive, it might emerge as more is learned.

Explanation
According to the Scrum Guide “Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items.” and “For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often done by decomposing Product Backlog items into smaller work items of one day or less.”

Explanation
The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.

Explanation
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation. The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

Explanation
They shouldn’t have, that is too certain but might be a good practice, each team decides.

Explanation
Scrum Guide states “The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.”

Explanation
The Scrum Guides states “The Scrum Team turns a selection of the work into an Increment of value during a Sprint.” The work produced by the Scrum Team comes from the Product Backlog, and the potential value it creates it is for the customers/users.

Explanation
In complex work, nothing can be certain, so providing an exact date can be a risk. However, transparency is everything, and the Product Owner can utilize complementary practices to help create more transparency for stakeholders and customers, like providing a roadmap based on past releases, the amount of work to be done and adjusting it as necessary without sticking to fix dates due to changes that might happen.

Explanation
The Kano Model is a framework for identifying the most important features when creating a product, based on the level of satisfaction they’re expected to bring to users.

Explanation
Deleting the item or pausing the sprints doesn’t make sense, as it is a Product Backlog item to be worked on. However, the Scrum Team might choose to evaluate how to work on that item and perform research on it first.

Explanation
According to the Scrum Guide, there is no requirement for all items to be decomposed, each Scrum Team utilized any practice they decides to

Explanation
The stakeholder made a request for a product feature, it is not an idea The Product Owner doesn’t assign request to anyone According to the Scrum Guide, all work to be done for a product has to come from the Product Backlog, and a Product Backlog is an ordered list of what is needed to improve the product.

Explanation
A Product Backlog is never full or complete, but contain necessary items to build or improve a product.

Explanation
According to the Scrum Guide, Product Backlog items don’t differ between features, bugs, or defects, they are items and it states “Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size. Attributes often vary with the domain of work.” Each Scrum Team might choose to categorize them. Usually, steps to recreate might be helpful for defects and bugs.

Explanation
Customers and Users of a product are the only ones who can really affirm if they receive value from a delivered item.