The Professional Scrum Master™ level I (PSM I) Assessment: Set 2

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity?

- By removing impediments that hinder the Development Team - By facilitating Development Team decisions

When does the next Sprint begin?

A new Sprint starts immediately after the conclusion of the previous Sprint. Sprint: time-boxed event of 30 days, or less, that serves as a container for the other Scrum events and activities. Sprints are done consecutively, without intermediate gaps.

How long is each sprint event expected to take?

Daily Scrum: time-boxed event of 15 minutes Sprint Planning : time-boxed event of 8 hours (One-month sprint) or less Sprint Review: time-boxed event of 4 hours (One-month sprint) or less Sprint Retrospective: time-boxed event of 3 hours (One-month sprint) or less.

When is the sprint goal developed?

During sprint planning

During a Sprint, a Development Team determines that it will not be able to finish the complete forecast. Who should be present to review and adjust the Sprint work selected?

During the Sprint, scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

What is the recommended size for a Development Team (within the Scrum Team)?

Optimal Development Team size is small enough to remain nimble and large enough to complete significant work. Fewer than three Development Team members decreases interaction and results in smaller productivity gains. More than nine members simply requires too much coordination. 3 to 9

What is an increment?

The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be "Done,".

Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?

The Product Owner is the sole person responsible for managing the Product Backlog, which includes that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next.

What is the sprint backlog?

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team. The Sprint Backlog makes visible all of the work that the Development Team identifies as necessary to meet the Sprint Goal. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.

The length of a sprint should be...

- Short enough to keep the business risk acceptable to the Product Owner. - Short enough to be able to synchronize the development work with other business events. Incorrect answer - No more than one month.

What is a Sprint Review?

A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed Based on what was done during the sprint and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value. This is at most a four-hour meeting for one-month Sprints. The Scrum Master ensures that the event takes place and that attendees understand its purpose.

What is the importance of transparency in scrum?

Scrum relies on transparency. Decisions to optimize value and control risk are made based on the perceived state of the artifacts. To the extent that transparency is complete, these decisions have a sound basis. The Scrum Master's job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change. Transparency doesn't occur overnight, but is a path.

What are the scrum artefacts?

Scrum's artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everybody has the same understanding of the artifact. The Scrum Artifacts are: Product Backlog Sprint Backlog Increment

The time-box for the Sprint Planning meeting is?

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

The maximum length of the Sprint Review (its time-box) is:

Sprint Review is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.

What are some characteristics of sprint retrospective events?

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. This is at most a three-hour meeting for one-month Sprints. The purpose of the Sprint Retrospective is to: • Inspect how the last Sprint went with regards to people, relationships, process, and tools; • Identify and order the major items that went well and potential improvements; and, • Create a plan for implementing improvements to the way the Scrum Team does its work.

What are some characteristics of sprint review events?

The Sprint Review includes the following elements: • Attendees include the Scrum Team and key stakeholders invited by the Product Owner; • The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done"; • The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; • The Development Team demonstrates the work that it has "Done" and answers questions about the Increment; • The Product Owner discusses the Product Backlog as it stands. • Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and, • Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.

What is product backlog refinement?

Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones. More precise estimates are made based on the greater clarity and increased detail; the lower the order, the less detail. The Development Team is responsible for all estimates. 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.

Describe the product backlog

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. A Product Backlog is never complete. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. Product Backlog items have the attributes of a description, order, estimate, and value. Product Backlog items often include test descriptions that will prove its completeness when "Done."