A.Daily Scrum.

B.Sprint Retrospective.

C.Release Retrospective.

D.Sprint Testing.

E.Sprint 0.

F.Release Testing.

G.Sprint Planning.

A.During Spring Planning.

B.Prior to starting a new Sprint.

C.During the Sprint Retrospective.

D.Prior to starting a new project.

A.To be able to reprimand the team when they don't meet their velocity goal for the Sprint.

B.To have complete transparency into what has been done at the end of each Sprint.

C.To know what the team will deliver over the next three Sprints.

D.To predict the team's productivity over time.

A.Coach the team on why the Daily Scrum is important as an opportunity to update the plan.

B.Acknowledge and support the self-organizing team's decision.

C.Learn why the Development Team wants this and work with them to improve the outcome of the Daily Scrum.

D.Consider the request and decide on which days the Daily Scrum should occur.

E.Have the developers vote.

A.False. A Product Owner can be replaced by a business analyst in the Development Team.

B.False. A Scrum Master is only required when asked for by the Development Team.

C.True. Each must be 100% dedicated to the Scrum Team.

D.True. Outcomes affected by their participation and availability.