The Development Team needs a Sprint Goal to create a communications plan of who does what and when.

The Development Team needs a Sprint Goal to communicate exactly who'll do what in the Sprint.

The Development Team needs a Sprint Goal to create synergy among the Development Team members.

The Development Team needs a Sprint Goal so they'll see the value and importance of completing all of the user stories selected for the Sprint meet the definition of done.

Yes, because the Product Owner both understands the ordering and knows the Developers skills

Yes, because the Scrum Master and the Product Owner agree on who assigns work to the Developers

No, because the Scrum Master is accountable tor dividing product backlog items over the Developers

No, because this conflicts with the principle of self-management and the Developers do not agree

Quality Control involves execution of planned quality activities; Quality Assurance involves carrying out

integration-type activities.

Quality Control lessons are learned during the Sprint Retrospect meeting; Quality Assurance is

demonstrated during the Sprint Review Meeting.

Quality Control activities are carried out during the process of Creating Deliverables that are potentially

shippable; Quality Assurance activities are usually standalone activities, not carried out as part of the work.

Specific skills are not required to perform Quality Control activities; Quality Assurance is a significant factor

of the definition of Done.