Scrum Practice

Product backlog

A Scrum Artifact that consists of an ordered list of the work to be done in order to create, maintain and sustain a product. Managed by the Product Owner.

Scrum is:

An agile process that allows us to focus on delivering the highest business value in the shortest time

How should a Development Team deal with non-functional requirements? A. Ensure every Increment meets them. B. Make sure the release department understands these requirements, but it is not the Development Team's responsibility. C. Handle them during the Integration Sprint preceding the Release Sprint. D. Assign them to the lead developers on the team.

Answer A

When is a Sprint over? A. When the Product Owner says it is done. B. When all Product Backlog items meet their definition of "Done". C. When all the tasks are completed. D. When the time-box expires.

D. When the time-box expires.

The Daily Scrum always should take exactly 15 minutes. For example, if your team managed doing it in 5 minutes, you should spend 10 more minutes on some useful team activity like Product Backlog refinement, but not more (T/F)

False

What are Scrum Values?

Focus, Courage, Openness, Commitment, Respect

The time-box for the Sprint Planning meeting is?

8 hours for a monthly sprint.

What is a sprint?

a predetermined time box to create a product from planning to ship date.

What is the duration of a typical Daily scrum Meeting?

15 minutes

When can a Development Team cancel a Sprint? A. It can't. Only Product Owners can cancel Sprints. B. When functional expectations are not well understood. C. When the Product Owner is absent too often. D. When the selected Product Backlog items for the Sprint become unachievable. E. When a technical dependency cannot be resolved.

Answer A

When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint? A. Yes, but only for Scrum Teams whose work has dependencies. B. Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done. C. No, each Scrum Team stands alone. D. No, that is far too hard and must be done in a hardening Sprint.

Answer B

When is a Sprint over? A. When the Product Owner says it is done. B. When all Product Backlog items meet their definition of "Done". C. When all the tasks are completed. D. When the time-box expires.

Answer D

The three pillars of Scrum are transparency, inspection, and what else? A. Respect B. Adaptation C. Collaboration D. Self organization

B. Adaptation

Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint? A. The Sprint Backlog. B. The Sprint Goal C. The release plan. D. Sprint Review minutes.

B. The sprint goal

Empiricism Three Pillars

Empiricism has three pillars: transparency, inspection and adaptation.

Empiricism

Empiricism: process control type in which only the past is accepted as certain and in which decisions are based on observation, experience and experimentation.

Product owner

Role in Scrum accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Developers.

Increment

Scrum Artifact that defines the complete and valuable work produced by the Developers during a Sprint. The sum of all Increments form a product.

Daily Scrum

Scrum Event that is a 15-minute time-boxed event held each day for the Developers. The Daily Scrum is held every day of the Sprint. At it, the Developers plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.

Jason is responsible for resolving conflicts among Scrum Team members. What role is he playing on a Scrum project?

Scrum Master

Who is responsible for creating User Stories in the Develop User Stories process?

The Product Owner

Developer

any member of a Scrum Team, that is committed to creating any aspect of a usable Increment each Sprint regardless of technical, functional or other specialty.

Definition of Done

is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the Definition of Done, an Increment is born. The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review.