To enable collaboration, the Product Owner, the Scrum Master, and the Scrum Team collaborate with each other and the stakeholders to create…

Scrum embraces change through continuous refinement and reprioritization of the Product Backlog, managed by the Product Owner. While collaboration with the customer is key, Scrum does not use a formal process for managing "large numbers of Change Requests" typical of traditional project management. Instead, changes are incorporated as new or modified items in the backlog for consideration in future Sprints. Options B, C, and D describe core, direct benefits of collaboration in Scrum: collective risk management, shared responsibility for achieving Sprint Goals, and continuous process improvement through events like the Sprint Retrospective.

B. Collaboration is essential for risk management in Scrum. The team collectively identifies, assesses, and decides on responses to risks throughout the project lifecycle.

C. The principle of collective ownership, fostered by collaboration, means team members assist each other to ensure the Sprint Goal is met, even if individual tasks face delays.

D. The Sprint Retrospective is a dedicated, collaborative event where the Scrum Master facilitates the team's discussion on process improvements for subsequent Sprints, embodying continuous improvement.

1. A Guide to the Scrum Body of Knowledge (SBOK® Guide)

3rd Edition.

For Correct Answer (A): Section 8.3.1

"Managing Changes in a Scrum Project

" explains that changes are handled by the Product Owner who maintains the Prioritized Product Backlog. The guide contrasts this flexible approach with the formal change control procedures of traditional project management

which deal with "Change Requests."

For Incorrect Option (B): Chapter 7

"Risk

" particularly Section 7.1

describes risk management as an iterative and collaborative process involving the entire Scrum Team to identify

assess

and respond to risks.

For Incorrect Option (C): Section 3.7

"Collaboration

" emphasizes that the Scrum Core Team works together to create deliverables. This principle underpins the team's ability to self-organize and align to meet Sprint commitments.

For Incorrect Option (D): Section 11.4

"Retrospect Sprint

" details the collaborative meeting where the team discusses what went well and what did not

creating actionable improvements for the next Sprint

which is a cornerstone of continuous improvement.