The Developers report that test environments take nine days to provision because a central platform team handles every request by ticket. The Scrum Master has a good relationship with that team's lead and could probably raise each ticket herself and chase it. What is the better expression of her accountability?

Professional Scrum Master I, objective 2. Developing people and teams medium

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

The options

Not correct Raise and chase every environment ticket herself, so the Developers never lose a day to it

Wrong, and it is the tempting one because it works immediately and makes the Scrum Master popular. It makes her the permanent workaround for a nine-day queue, and the queue survives untouched for every other team.

Not correct Accept the delay as a constraint and coach the Developers to forecast less work each Sprint

Wrong. Lowering the forecast normalises the impediment and hides it from the organisation, which is the opposite of the transparency that would get it fixed.

Not correct Add the provisioning delay to the Sprint Backlog as an item so the Developers can fix it themselves

Wrong. The impediment sits in another department's process, well outside what the Developers can reach from inside their own Sprint; putting it on their plan makes the nine-day queue their problem to work around while the queue itself stays exactly as it is.

Correct Work with the platform team and their management on the provisioning process so the delay stops existing, while helping the Developers cope in the meantime

Correct. The accountability is causing the removal of impediments — acting on the cause so the impediment goes away, which here means changing how provisioning works rather than absorbing it personally.

Why

The Guide says causing the removal of impediments, not removing them, and the wording is doing real work. A Scrum Master who personally fixes everything becomes a dependency the team cannot outgrow, and the underlying condition — a nine-day queue, an absent approver, a missing skill — is left in place. Causing removal means finding the person or the change that ends the impediment. Personal heroics that leave the cause intact are a wrong answer even when they help this Sprint.

Where this comes from

Cited
Scrum Guide section Scrum Master
What it says
Causing the removal of impediments to the Scrum Team's progress

Practise this

Reading one question is not practice. The trainer will draw a set from objective 2 and space the ones you get wrong.

Practise Professional Scrum Master I

More questions on this objective

All questions on Developing people and teams