Certified Scrum Product Owner (CSPO) Workshop Practice Tests and PDFs

When a product grows, it is quite possible that the PO will get help from other Product Managers and others in the organization who interact regarding the customer facing activities and knowledge of the product marketplace. While it is fine for the PO to be aided by the aforementioned people, it is NOT acceptable for the PO to attempt to proxy or outsource their PO Scrum Team duties, especially the Scrum Team facing duties.

At the end of a Sprint, the new Increment must be Done, which means it must be in useable condition and meet the Scrum Team’s definition of Done. So it should be as per PO expectation and should contain all features.

The Development Team is responsible for all estimates in the Product Backlog. The Product Owner may influence the Development Team by helping it understand and select trade-offs, but the people who will perform the work make the final estimate.

The individual, detailed pieces of work that are needed to convert a product backlog item into a working software component or solution are called Task.

The workload indeed depends on all the requirements for a feature and thus includes the Definition of Done, since this list defines all the requirements for all the features on the Product Backlog

It happens. Not everything will always be completed in every iteration, no matter how well you plan. If there is leftover work or there are story points, they will be put back into the backlog and sorted by priority. Typically, that work would be put into the next iteration.

A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves

Daily Scrum, Sprint planning & retrospective are timeboxed events in scrum.

Progress on a Scrum project can be tracked by means of a release burndown chart. The ScrumMaster should update the release burndown chart at the end of each sprint. The horizontal axis of the sprint burndown chart shows the sprints; the vertical axis shows the amount of work remaining at the start of each sprint.

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

The burn-up chart shows whether there is any change in the total story points which the burn down chart does not show.

Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product. A Product Backlog attribute that groups items may then be employed. If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of Done.

The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.

The Scrum framework defines 3 main roles: 1.The Development team 2.The Scrum Master 3.The Scrum Product owner These 3 roles are together called the Scrum team.

Someone occupying one of the three Scrum roles (The Team, The Product Owner, The Scrum Master) who has made a commitment and has the authority to fulfill it. Anyone else is called a Chicken.