Correct Answer to Q#9: C

During a Sprint Review, the Scrum Team presents the completed work (the Increment) to stakeholders and gathers feedback. This helps inform what may be prioritized next.

A ❌ More related to the Sprint Retrospective.
B ❌ The next Sprint's scope is not formally determined during the Sprint Review.
C ✅ Correct.
D ❌ Root-cause analysis of unfinished work belongs more to the Sprint Retrospective.

Question 9: What happens during a Sprint Review?

A. Review of what the team could do more or less off during the next sprint.
B. Figure out the scope for the next sprint.
C. End of the sprint demo for everyone to solicit feedback on the work done in the sprint.
D. It is an opportunity to brainstorm and do a root cause analysis of work items that could not get done.

Correct Answer to Q#8: B

In Extreme Programming (XP), the team takes collective ownership of the code, meaning everyone is responsible for the quality and maintenance of the entire codebase—not just the parts they personally wrote.

For collective ownership to work effectively:

Trust is essential because team members need to feel comfortable modifying each other’s code and making decisions together.
Collaboration is important because developers continuously communicate, review, and work together to improve the code.

Other options describe useful XP practices, but they are not the key principles specifically supporting collective code ownership.

Question 8: XP teams take collective ownership of code. For such a team, _______ and _______ are the key.

A. Definition of done and pair programming.
B. Trust and collaboration.
C. Velocity and co-location.
D. Onsite customer and test-driven development.

Correct Answer to Q#7: D

Burnup and burndown charts provide a quick visual indication of how the Agile team is progressing during an iteration:

Burndown chart: shows remaining work over time.
Burnup chart: shows completed work against the total scope and can make scope changes visible.

The other options are less appropriate:

A. Weekly status report — not typically the primary Agile progress-tracking tool.
B. Sprint backlog — shows the work, but not as clearly the overall progress/trend.
C. Defect log — focuses on defects rather than iteration progress.

Question 7: A project stakeholder wants to have a look at how the Agile team is progressing in the middle of an iteration. As a member of the Agile team, you can guide him to:

A. The most recent weekly status report.
B. The sprint backlog.
C. The defect log.
D. The combined burnup and burndown charts.