A.When the sales department has an important new opportunity.

B.When the Development Team feels that the work is too hard.

C.When it becomes clear that not everything will be finished by the end of the Sprint.

D.When the Sprint Goal becomes obsolete.

A.Make up a plan for the rest of the project.

B.Create an increment of potentially releasable software.

C.Define the major product features and release plan architecture

D.Analyze, describe, and document the requirements for the subsequent Sprints.

E.Develop at least one piece of functionality.

A.Prior to starting a new project.

B.During the Sprint Retrospective.

C.During Spring Planning.

D.Prior to starting a new Sprint.

A.Its productivity is likely to stay the same.

B.Its productivity is likely to decrease.

C.Its productivity is likely to increase.

A.Put them on a separate list on the Scrum board, available for all to see.

B.Run the integration and regression tests before the end of the Sprint, and capture the open work for the
Sprint Backlog of the next Sprint.

C.Add them to the Product Backlog and keep the Product Owner posted on the expected effort.

D.Add them to the definition of "Done" so the work is taken care of every Sprint.

E.Run the integration and regression tests before the end of the Sprint, and capture the open work for the
Sprint Backlog of the next Sprint.