Here is an interesting PSM practice test quiz for you to test your knowledge about Professional Scrum and the role of the Scrum Master. Try taking this quiz and see how well you can score. So, are you ready to take this PSM mock test? Let's get started then. All the best!
Every Sprint to promote shared learning.
Never, because it reduces productivity.
As needed, while taking into account a short term reduction in productivity.
As needed, with no special allowance for changes in productivity.
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.
As much as it can fit into the Sprint.
All development work and at least some testing.
Analysis, design, programming, testing and documentation.
Without a new vocabulary as a reminder of the change, very little change may actually happen.
The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost.
Management may feel less anxious.
The place can be named.
The consistency reduces complexity.
The Product Owner demands it.
Rooms are hard to book and this lets it be booked in advance.
Development Team and Scrum Master
Development Team and Product Owner
Scrum Master and Product Owner
8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
Whenever it is done.
Immediately following the next Sprint Planning.
When the Product Owner is ready.
Immediately after the conclusion of the previous Sprint.
To make sure every team member answers the three questions.
He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.
To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.
To gather status and progress information to report to management.
The event must happen at a set time.
The event must happen by a given time.
The event must take at least a minimum amount of time.
The event can take no more than a maximum amount of time.
Continually monitor staffing levels of the Development Team.
Monitor the Development Team's productivity.
Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software.
Identify and remove people that aren't working hard enough.
The Product Owner can help clarify or optimize the Sprint when asked by the Development Team.
The Sprint Backlog is fully formulated in the Sprint Planning meeting and does not change during the Sprint.
As a decomposition of the selected Product Backlog Items, the Sprint Backlog changes and may grow as the work emerges.
The Development Team may work with the Product Owner to remove or add work if it finds it has more or less capacity than it expected.
It is a mechanism to control the Development Team's activities during a Sprint.
It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.
It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
Short enough to keep the business risk acceptable to the Product Owner.
Short enough to be able to synchronize the development work with other business events.
No more than one month.
All of these answers are correct.
3 to 9
7 plus or minus 2
When it becomes clear that not everything will be finished by the end of the Sprint.
When the Development Team feels that the work is too hard.
When the sales department has an important new opportunity.
When the Sprint Goal becomes obsolete.
A complete methodology that defines how to develop software.
A cookbook that defines best practices for software development.
A framework within which complex products in complex environments are developed.
A defined and predictive process that conforms to the principles of Scientific Management.
The same time of day every day.
Two minutes per person.
15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter.
4 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
As long as needed.
4 hours and longer as needed.
When all Product Backlog items meet their definition of done.
When the Product Owner says it is done.
When all the tasks are completed.
When the time-box expires.