The project manager does not have the authority to remove a Scrum Team member

The project manager can remove any impediment, including Scrum Team members

The project manager must consult with the product owner before removing a Scrum Team member

There is no project manager in Scrum

There can be multiple Product Backlogs, when it's possible to divide the product into different application areas

There can be multiple Product Backlogs, but still a single integrated Product Backlog to summarize them all.

There's only one Product Backlog for all of them

True

False

Discuss with the senior management and issue a formal notice to the team for improving performance.

Defend the team at any cost and find loopholes in the client's requirement.

Setup a meeting with the team to gain an understanding of the exact situation and devise a strategy to meet the acceptance criteria.

Offer sincere apologies to the client and convince him that a new team will deliver the work units which meet the acceptance criteria.

Using formal change control to manage Product Backlog when market provides feedback from Product usage

Clearly expressing and ordering Product Backlog items

Ensuring the Developers understand items in the Product Backlog to the level needed

The Sprint would be cancelled, and the next one will start as soon as enough items at the top of the Product Backlog are clear.

The Sprint Planning would be delayed, until enough refinement is done on the items at the top of the Product Backlog.

Nothing; the Sprint would be planned anyway.

The Sprint Planning would be extended, to have the items refined before adding them to the Sprint Backlog.

The Product Owner as he/she is responsible for the product’s success

The Scrum Master as he/she is responsible for the Developers' productivity

The development organization (or the Scrum Team if none is available from the development organization)

False

True

Making informed decisions.

Making unilateral decisions.

Making individual decisions.

Making absolute decisions.

Estimates the value of Product Backlog items

Is responsible for engaging the stakeholders

Participates in the Daily Scrum meeting

Explains the Product Backlog items