Impediment Log can be discussed during Daily Standup.

Internal impediments from within the team are never recorded in the Impediment Log, and only brought up

during the Daily Standups.

Transparency in Scrum ensures swift and easy identification of impediments.

Scrum Master maintains and updates the Impediment Log.

Leadership style, problem-solving, availability, commitment

Stress management, people management, communication, loyalty

Responsiveness, problem-solving, facilitator, negotiation

Intuitiveness, people management, reliability, facilitator

A and В

A

A and D

A, B, and C

User Stories are objective, and the Acceptance Criteria provides the subjectivity required for the User Story

to be considered as Done.

In the Sprint Review Meetings, the Acceptance Criteria provides the context for the Scrum Master to

decide if a User Story has been completed satisfactorily.

It is the Scrum Master who has to ensure that the Acceptance Criteria for a User Story are not changed by

the Product Owner in the middle of a Sprint.

It is the Scrum Team ' s responsibility to keep track of what changes are being made to the Acceptance

Criteria even during the Sprint.

The Development Team will work with Martha to estimate the items in the Product Backlog with story points.

The Development Team will work with you, the Scrum Master, to create time and cost estimates for all the Product Backlog items.

Martha can estimate the items in the Product Backlog, but you, the Scrum Master, must be approve the estimates prior to each Sprint Planning meeting.

Martha can estimate the items in the Product Backlog, but the Development Team must approve the estimates prior to the Sprint beginning.

They reduce the productivity of a Scrum team.

Impediments can be both internal and external.

Impediments should be documented only by the team members in the Impediment Log.

Impediments faced are brought up by the Scrum Team during the Daily Standup Meeting.

The Development Team will consult on user stories for the Product Backlog.

The Development Team chooses the Product Owner for each Sprint.

The Development Team determines who ' ll do what task in the Sprint Backlog.

The Development Team will estimate the work of Product Backlog.

Only В

A and C

В and D

A and B

A, C, and D

A and D

All of the above.

None of the above.

In Scrum, upfront planning is high, while in Traditional Project Management it is low.

In Scrum, performance measurement is based on plan conformity, while in Traditional Project

Management it is based on business value.

In Scrum, customer involvement is high throughput the project, while in Traditional Project it varies

according to the project ' s lifecycle.

In Scrum, Quality Assurance is process centric, while in Traditional Project Management it is customer

centric.