Which three behaviors demonstrate that a team is self-organizing? (Choose three.)
Options:
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).
Question 2
What is the time-box for the Sprint Review?
Options:
A.
As long as needed.
B.
2 hours for a monthly Sprint.
C.
4 hours for a monthly Sprint.
D.
4 hours and longer as needed.
E.
1 day
Answer:
C
Explanation:
According to the Scrum Guide1, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. The time-box for the Sprint Review is four hours for a one-month Sprint.
References: Scrum Guide
Question 3
How much work must a Development Team do to a Product Backlog item it selects for a Sprint?
Options:
A.
A proportional amount of time on analysis, design, programming, testing, and documentation.
B.
As much as it can fit into the Sprint. Any remaining work will be transferred to a subsequent Sprint.
C.
All development work and at least some testing.
D.
As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done”.
Answer:
D
Explanation:
The Development Team must do as much work as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of “Done”, as stated in the Scrum Guide1: “The Development Team works to forecast the functionality that will be developed during the Sprint. The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal. The entire Scrum Team collaborates on understanding the work of the Sprint.”