What is the time-box for the Sprint Review?
Answer(s): C
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.
Scrum Guide
Who is responsible for tracking the remaining work of the Sprint?
Answer(s): A
According to the Scrum Guide1, only people who are actively working on items in the Sprint Backlog participate in updating it during a Sprint; this includes tracking progress made on those items. This is typically done by Developers updating their remaining work every day after their Daily Scrum. The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving their Sprint Goal.
What is the tactic a Scrum Master should use to divide a group of 100 people into multiple Development Teams?
According to the Nexus Guide2, which is a framework for scaling Scrum, one way to form multiple Development Teams from a large group of people is to ask them to self-organize into teams based on dependencies, skills, domain knowledge, and personal preferences. This approach respects the autonomy and empowerment of the Developers and allows them to choose how they want to work together.
Nexus Guide
Which statement best describes a Product Owner's responsibility?
According to the Scrum Guide1, ordering Product Backlog items is solely up to the Product Owner's discretion. The Product Owner orders items in the Product Backlog to best achieve goals and missions. To do this, they optimize value by considering various factors such as cost and benefit, risk, dependencies, date needed, etc. The Product Owner is responsible for maximizing the value of the work the Development Team does.
The Sprint Review is mainly an inspect and adapt opportunity for which group?
According to the Scrum Guide1, the Sprint Review is an informal meeting at the end of the Sprint, where the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on what to do next. The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done"; the Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; and the Development Team demonstrates the work that it has "Done" and answers questions about the Increment. The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning. The Sprint Review is mainly an inspect and adapt opportunity for the Scrum Team and stakeholders.
Post your Comments and Discuss Scrum PSM I exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PSM I content, but please register or login to continue.