Sprint review meeting

Question 1

Customer Service Team Lead is getting many customer complaints regarding the email confirming an order. To whom should the Stakeholder talk to get this addressed?

Directly to the developers responsible of building the product
The Scrum Master
The product owner
The scrum team

Answer 1

The product owner

By ordering the Product Backlog, the Product Owner decides which features will be implemented in a Sprint

Question 2

By ordering the Product Backlog, the Product Owner decides which features will be implemented in a Sprint

True or false

Answer 2

FALSE

Incomplete work (also called not “done” work) is not part of the Increment and is not an outcome of the Sprint. Demonstrating unfinished work may give the impression that the work is done and can be released immediately. This does not mean that incomplete work cannot be mentioned or discussed.

Question 3

The Scrum Team meets with the Stakeholders at the end of the Sprint. What should the Product Owner do if a Product Backlog Item is only partially done?

Inspect the work toghether with the stakeholders. If part of the work is acceptable, the product owner should release it to get feedback from the market.
Consult with the developers. If they feel the work is good enough, it can be released. Any issues should be added to the product backlog and fixed in the next spring.
Put the remaining work in the Product backlog. Partially done work should not be released.

Answer 3

Put the remaining work in the Product backlog. Partially done work should not be released.

Incomplete work is not releasable. The Product Owner should put the item back into the Product Backlog and decide what should happen next.

Question 4

The Stakeholders have been complaining to the Scrum Master that the Sprint Review meeting is too long. In order the speed-up the review meeting, the Scrum Team has created a presentation with slides of the features it has completed in the Sprint. Is this a good idea?

Yes, this is acceptable as the meeting is time-boxed
Yes, beacause the Product Owner has already reviewed the features before the meeting
No, because the stakeholders cannot give valuable feedback without trying out the actual Increment

Answer 4

No, because the stakeholders cannot give valuable feedback without trying out the actual Increment

This is generally not a good idea, as one aspect of the meeting foster collaboration and get feedback on the actual Increment. This does not mean that slides cannot be used, but it should not entirely replace the demonstration.

Question 5

The Product Owner accepts work only during the Sprint Review meeting.

True or False?

Answer 5

FALSE

There is no need to wait for the Sprint Review meeting to review work. The Developers and the Product Owner should collaborate throughout the Sprint to ensure that the Increment and any completed items are acceptable. This is part of the inspection process.

Question 6

What is the duration of the Sprint Review meeting for a three-week Sprint?

1 or less
2 or less
3 or less
4 or less
8 or less

Answer 6

4 or less

The Sprint Review is at most a four-hour meeting for one-month Sprints. The meeting is usually shorter for shorter Sprints. The Scrum Guide does not say it should be proportionally shorter. In practice, you can use math to figure out how long a meeting should take for Sprints that are shorter than 4-weeks, but AGAIN, this is NOT imposed by Scrum. Many online questions/articles say something like “Scrum Events are directly proportional to the length of the Sprint.” Unfortunately, this is incorrect.

Question 7

The Sprint Review is the last prescribed Scrum meeting in the Sprint.

True or False?

Answer 7

FALSE

The Sprint Review happens at the end of the Sprint, but it is not the last event in the Sprint. The last event is the Sprint Retrospective.

Question 8

The Developers can only interact with the Stakeholders during the Sprint Review or through the Product Owner.

True or False?

Answer 8

FALSE

Scrum does not impose any restrictions. The Developers are free to interact with the Stakeholders anytime during the Sprint. If it makes sense, they can even talk directly with the Stakeholders, but they should keep the Product Owner in the loop regarding any new developments.