card2brain.ch (2024)

Optimizing the value of the work the Development Team does.

Directing the Development Team.

Managing the project and ensuring that the work meets the commitments to the stakeholders.

Keeping stakeholders at bay.

Next Monday.

Immediately following the next Sprint Planning.

When the Product Owner is ready.

Immediately after the conclusion of the previous Sprint.

Deliver an increment of potentially releasable software.

Determine the complete architecture and infrastructure for the product.

Develop and deliver at least one piece of functionality.

Create the complete Product Backlog to be developed in subsequent Sprints.

Develop a plan for the rest of the release.

Without a new vocabulary as a reminder of the change, very little change may actually happen.

The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost.

Management may feel less anxious.

All answers apply.

The same time of day every day.

Two minutes per person.

15 minutes.

4 hours.

15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.

It is a mechanism to control the Development Team's activities during a Sprint.

It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.

It is a demo at the end of the Sprint for everyone in the organization to check on the work done.

The Scrum Master

The Development Team

The Product Owner

The most junior member of the Team

Each Development Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.

Each Development Team uses its own but must make their definition clear to all other teams so the differences are known.

All Development Teams must have a definition of "Done" that makes their combined work potentially releasable.

It depends.