Which three behaviors demonstrate that a team is self-organizing? (Choose three.)
A.
Stakeholders walking in at the Daily Scrum to check progress and work with the Scrum Master to optimize the functional scope for the Sprint.
B.
The Development Team members are working within the boundaries of their functional description and nicely handing off work from analyst to developer to tester to integration.
C.
The Product Owner doesn’t need to be at Sprint Retrospectives.
D.
The Development Team creating their own sprint backlog, reflecting all work that is part of the definition of “Done”.
E.
The Development Team has all the skills needed to create a releasable Increment.
F.
Development Team members collaboratively selecting their own work during the Sprint.
G.
The Development Team inviting external people to the Sprint Planning to ask them how to turn a Product Backlog item into an Increment via a complete and detailed Sprint Backlog.
According to the Scrum Guide, three behaviors that demonstrate that a team is self-organizing are creating their own sprint backlog, having all the skills needed to create a releasable Increment, and collaboratively selecting their own work during the Sprint. The other options are not behaviors that demonstrate self-organization, as they are either contrary to Scrum values and principles (such as stakeholders walking in at the Daily Scrum or working within functional boundaries) or unnecessary for self-organization (such as the Product Owner not being at Sprint Retrospectives or the Development Team inviting external people to the Sprint Planning).
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit