Scrum Quiz

16 questions covering Scrum: roles, events, artifacts, Sprints and the Definition of Done.

Roles

#

The Product Owner is on holiday for a Sprint and nobody has been delegated authority. What is the main risk?

The Sprint cannot start without a Sprint Planning attendee

The Scrum Master must write the Sprint Goal alone

Priority questions stall or get answered by the team, so business value decisions drift to people not accountable for them

Correct. The Product Owner role is a single accountable decision-maker precisely so that priority never becomes a committee outcome.

Velocity will be inaccurate for that Sprint

#

Which action is inconsistent with the Scrum Master role?

Facilitating the Retrospective

Assigning Sprint Backlog items to individual developers

Correct. Developers pull their own work. Assignment removes self-organization, which is where most of the team's adaptive capacity lives.

Removing an impediment caused by another department

Coaching the Product Owner on backlog refinement

#

Scrum states there are no sub-teams within the Developers. What does that rule out?

A separate testing group that owns quality while others own coding

Correct. The whole team is accountable for the Definition of Done, and a handoff to a testing sub-team reintroduces a phase.

Developers with different levels of seniority

Specialists in security or performance

Pairing between two developers on one item

#

Who is accountable for maximizing the value of the product?

The Scrum Master

The Developers collectively

The Business Sponsor

The Product Owner

Correct. Which is why they alone order the Product Backlog and may refuse work.

Events

#

Sprint Planning answers three questions. Which is the first?

How will the work be broken into tasks

What can be Done within the Sprint

Why is this Sprint valuable, which produces the Sprint Goal

Correct. Value comes before selection and decomposition, otherwise the Sprint is just a batch of tickets.

Who will work on which item

#

The Daily Scrum has degenerated into each developer reporting status to the Scrum Master. What has been lost?

The timebox, which is now longer than 15 minutes

Its purpose as a re-planning event for the Developers against the Sprint Goal

Correct. It is a planning event for the people doing the work. Reporting upward makes it overhead rather than coordination.

The Product Owner's visibility into progress

The opportunity to update the burndown chart

#

A team prepares slides describing what was built for the Sprint Review. What does that signal?

That a Done Increment probably does not exist, since a real Increment can simply be shown working

Correct. The Review inspects the Increment, and a description is not an Increment.

Good preparation, since stakeholders need context

That the Review timebox is too short

That the Product Owner has not refined the backlog

#

What is the correct output of a Sprint Retrospective?

A list of every problem raised, sent to management

A revised Sprint Goal for the Sprint just completed

An updated Definition of Ready

One or two improvements pulled into the next Sprint Backlog, so they compete for real capacity

Correct. Improvements that are not given capacity are how retrospectives lose credibility over a few months.

#

Backlog refinement is best described as what?

A formal Scrum event with its own timebox

A meeting run by the Scrum Master before each Sprint

An ongoing activity, commonly capped near 10% of capacity, that keeps upcoming items ready enough for Planning

Correct. It is not one of the five events, but skipping it turns Sprint Planning into a discovery session.

The process of splitting the Sprint Backlog into tasks

Artifacts

#

Each Scrum artifact carries a commitment. Which pairing is correct?

Product Backlog and Definition of Done

Sprint Backlog and Sprint Goal

Correct. Product Backlog carries the Product Goal, and the Increment carries the Definition of Done.

Increment and Sprint Goal

Sprint Backlog and Product Goal

#

Why does the Product Backlog have a "iceberg" shape, detailed at the top and vague further down?

Because refining items that may never be built, or that will change before they are, is waste

Correct. Detail is added just in time, as items approach the top of the order.

Because the Product Owner has limited time to write items

Because low-priority items are never implemented

Because Scrum forbids estimating items more than one Sprint ahead

#

Stakeholders treat the Sprint Backlog as a delivery commitment they can hold the team to. What is wrong?

Nothing, the Sprint Backlog is a contract for the Sprint

It should be a commitment only if the team estimated in hours

Only the Scrum Master may show it to stakeholders

It is the Developers' own working plan, expected to change daily, and only the Sprint Goal is the commitment

Correct. Scope inside a Sprint is renegotiated with the Product Owner as the team learns, which is why the Goal is stated as an outcome.

Sprints and Done

#

Two days before a Sprint ends, it is clear two items will not be finished. What happens?

The Sprint is extended by two days

The items are marked Done and finished next Sprint

The Sprint ends on its fixed date, and the unfinished items return to the Product Backlog for re-ordering

Correct. The timebox never moves, because a variable Sprint length destroys the cadence that makes forecasting possible.

The Scrum Master cancels the Sprint

#

Who may cancel a Sprint, and when?

The Scrum Master, when the team is blocked

The Product Owner, and only when the Sprint Goal has become obsolete

Correct. It is rare, and "we will not finish everything" is never a reason, since unfinished work simply returns to the backlog.

The Developers, by majority agreement

Any stakeholder whose priorities changed

#

A team's Definition of Done omits deployment to staging. What is the predictable consequence?

Deployment work accumulates as undone work until a hardening phase is needed to absorb it

Correct. Excluded work is deferred rather than cancelled, and it returns at a worse exchange rate.

Velocity becomes more stable

The Product Owner gains flexibility over releases

Nothing, since deployment is an operations concern

#

What is the difference between a Definition of Done and a Definition of Ready?

They are the same checklist applied at different times

Ready is mandatory in Scrum, Done is optional

Done applies to the Increment, Ready applies to the release

Done says how finished any item must be to count, while Ready says how prepared an item should be to enter a Sprint, and a strict Ready gate quietly recreates a requirements phase

Correct. Ready is a useful guideline and a harmful gate, which is why the Scrum Guide names only the Definition of Done.

Quiz Progress

• Answered: 0 / 0 (0%)
• Correct: 0 / 0 (0%) Reset