All of the above topics should be discussed in the Sprint Review, as stated in [4]: "The purpose of this meeting is to inspect what was delivered during this sprint and adapt what we want to deliver next. This means we will discuss three things:
What did we do this sprint?
How did we do it?
What do we want to do next?"
Question 2
How much work must a Development Team do to a Product Backlog item it selects for a Sprint?
Options:
A.
A proportional amount of time on analysis, design, programming, testing, and documentation.
B.
As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.
C.
All development work and at least some testing.
D.
As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done”.
Answer:
D
Explanation:
The Development Team must do as much work as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done”, as stated in the Scrum Guide1: “The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.”
Question 3
Which of the following are true about the length of the Sprint? (Choose two.)
Options:
A.
The length of the Sprint should be proportional to the work that is done in between Sprints.
B.
It is best to have Sprints of consistent length throughout a development effort.
C.
Sprint length is determined during Sprint Planning, and should hold the time it will take to code the planned features in the upcoming Sprint, but does not include time for any testing.
D.
Sprint length is determined during Sprint Planning, and should be long enough to make sure the Development Team can deliver what is to be accomplished in the upcoming Sprint.
E.
All Sprints must be 1 month or less.
Answer:
B, E
Explanation:
The correct answers are B and E, because these statements are true about the length of the Sprint. It is best to have Sprints of consistent length throughout a development effort, as this helps establish a reliable rhythm and cadence for the Scrum Team and the stakeholders. All Sprints must be one month or less, as this ensures that the Scrum Team can inspect and adapt frequently and deliver value incrementally.