Question 4 - PSM II discussion

A Scrum Team is self-managing, meaning that they have the autonomy and authority to organize and manage their own work within the boundaries of Scrum. A self-managing Scrum Team:

Creates their own Sprint Backlog, reflecting all work that is part of the Definition of Done , which is a valid option as it shows that the Developers are responsible for planning and executing the work needed to deliver a potentially releasable Increment at the end of each Sprint.

Collaboratively selects and re-plans their work during the Sprint (D), which is another valid option as it shows that the Developers are able to adapt to changing requirements, priorities, or circumstances within the Sprint, without relying on external instructions or approvals.

The other options are not correct because they:

Invite management to the Daily Scrum for a progress update and subsequently work with the Scrum Master to optimize the plan for the next day (A), which is not a good option as it shows that the Scrum Team is not self-managing, but rather dependent on management intervention and direction. The Daily Scrum is an event for the Developers to inspect their progress and plan their work for the next 24 hours, not a status report for management or anyone else.

Work strictly within the boundaries of their function description, and hand off work in a timely fashion to the other members within the team (B), which is not a good option as it shows that the Scrum Team is not self-managing, but rather following a rigid and siloed structure. The Developers are cross-functional, meaning that they have all the skills necessary to create a ''Done'' Increment, and they collaborate and coordinate their work as one team, not as separate individuals or roles.

Invite the right external people to the Sprint Planning to help them create a complete and detailed Sprint Backlog before the meeting timebox expires (E), which is not a good option as it shows that the Scrum Team is not self-managing, but rather relying on external assistance and input. The Sprint Planning is an event for the Scrum Team to create a Sprint Goal and a Sprint Backlog, based on the Product Owner's proposal and the Developers' forecast. The Scrum Team may invite other people to provide advice or expertise, but they are ultimately accountable for their own plan.