PSM Preparation
True
All Development Teams working on the same Product should use the same Product Backlog.
False
All the Scrum Teams working on the same product should have the same Sprint length.
Yes - but this is not best practice because it could create a conflict of interest.
Could the Product Owner and the Scrum Master be a part of the Development Team?
Yes, if the remaining work is also estimated, maybe in bigger units
Could the Sprint Planning be finished if only work planned for the first days of the Sprint is decomposed to units of one day or less?
False - During each Sprint Retro, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate.
Definition of "Done" is created during the first Sprint and remains unchanged until the Product release.
True
Definition of Done can be reviewed and adapted during each Sprint Retrospective. True or False?
- Sprint Planning - Sprint Backlog - Sprint Review - Sprint Retro
Formal opportunities to inspect and adapt
- DoD ensures artifact transparency - DoD is used to assess when work is complete on the product Increment - DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning
How does Definition of "Done" help the Scrum Team? Select three most applicable items.
- Facilitating Scrum events as requested or needed - Finding techniques for effective Product Backlog management - Understanding product planning in an empirical environment
How does the Scrum Master help the Product Owner? Select the three most appropriate answers.
- Helping the Development Team to create high-value products - Coaching the Development Team in self-organization and cross-functionality - Removing impediments to the Development Team's progress
How does the Scrum Master serve the Development Team? Select the three most appropriate answers.
- Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization - Planning Scrum implementations within the organization - Leading and coaching the organization in its Scrum adoption
How does the Scrum Master serve the Organization? Select the three most appropriate answers.
Frequently, but it should not get in the way of the work
How frequently should scrum users inspect Scrum artifacts and progress toward a Sprint Goal?
Not more than 8 hours - time-boxed to a maximum of eight hours for a one-month Sprint.
How much time does the Sprint Planning take?
As soon as possible to minimize further deviation
If an inspector determines that one or more aspects of a process deviate outside acceptable limits, when must an adjustment be made?
False Sprint is cancelled only in the case of the Sprint Goal became obsolete. If some work could not be done, the Backlog should be re-negotiated between the Product Owner and Dev Team.
If an item in the Sprint Backlog cannot be finished by the end of the Sprint (it turned out there is a lot more work to do than was estimated), the Sprint is cancelled
Make sure the Sprint Backlog for the next Sprint includes at least one high priority process improvement.
Imagine the following situation. At the Sprint Retrospective meeting the Scrum Team identified some improvements that can be done. What should the Scrum Team do? Select the best option.
Optimal Dev Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Dev Team members decrease interaction and results in smaller productivity gains.
Imagine you are a Scrum Master in a small Organization that tries to adopt Scrum. There are 10 developers and the Product Owner. How can they be divided into teams? Choose all applicable options:
Only in the Sprint Review
In which meetings the Key Stakeholders are allowed to participate?
No 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.
Is it allowed to skip the Daily Scrum if there is nothing interesting to talk about?
False
It is a good practice to have at least two Product Owners on big projects
False - It is prohibited. Purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done".
It is a good practice to have, from time to time, a special technical Sprint that consists only of tasks removing the technical debt without implementing any new functionality.
False (It is not normal. Dev Teams deliver an Increment of product functionality every Sprint. This Increment is usable, so a Product Owner may choose to immediately release it. So there is nothing to prepare. Each increment contains only "Done" functionality that could be released immediately.)
It is normal to have a "hardening" Sprint to remove all technical debt and prepare the Product for upcoming release. (T or F?)
False - Plan is created by the collaborative work of the entire Scrum Team.
Only the Product Owner and the Development Team participate in the Sprint Planning. There is nothing to do for the Scrum Master.
Look this up
People other than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice. T or F?
Sprint Planning Daily Scrum Sprint Review Sprint Retro
Scrum Events in the right order:
False
Scrum does not allow additional meetings that are not defined in Scrum.
Empiricism
Scrum is founded on
True - rather a framework within which you can employ various processes and techniques.
Scrum is not a process or technique. True or False?
False Each component within the Scrum framework serves a specific purpose and is essential to Scrum's success and usage.
Scrum recommends using only those Scrum components and rules which suit most for a particular project.
Openness Commitment Respect Courage Focus
Select the five Scrum Values
Sprint Planning - for technical or domain advice Sprint Review - Product owner is responsible for inviting the Key stakeholders to the Sprint Review meeting
Select the two meetings in which people outside the Scrum Team are allowed to participate.
False Scrum does not require a minimum duration.
The Daily Scrum always should take exactly 15 minutes. For example, if your team managed to do it in 5 minutes, you should spend 10 more minutes on some useful team activity like Product Backlog refinement, but not more.
False
The Daily Scrum time-box depends on the size of the Development team.
True
The Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment. T or F?
- Ensures that the Development Team has the meeting - Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box - If others are present at the Daily Scrum, ensures that they do not disrupt the meeting
The Scrum Master does the following regarding the Daily Scrum (select all applicable variants):
Scrum Master is a servant-leader for the Scrum Team. Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't.
The Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team.
The Dev Team The Product Owner The Scrum Master
The Scrum Team consists of
False - The Dev Team modified the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.
The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the Sprint Backlog later by the Development Team.
- Create a plan for implementing improvements to the way the Scrum Team does its work - Identify and order the major items that went well and potential improvements - Inspect how the last Sprint went with regards to people, relationships, process, and tools
The purpose of the Sprint Retrospective is to (select three)
False - There are other ways of conducting the meeting as well.
The structure of the Daily Scrum is well-defined and constant. Every team member should answer the three main questions: What did I do yesterday? What will I do today? Do I see any impediment?
- Daily Scrum - 15 minutes - Sprint Review is a four-hour-time-boxed meeting for one-month Sprints. Shorter for shorter Sprints - Sprint Retro is a three-hour time boxed meeting for one-month Sprints. - Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.
Time Box for each event:
- As long as a product exists, its Product Backlog also exists - It is never complete - It is dynamic
What are Product Backlog features? Select three.
Increment Product Backlog Sprint Backlog
What are the Scrum Artifacts?
- Scrum recognizes no sub-teams in the Dev Team - Scrum recognizes no titles for Development Team members - Accountability belongs to the Development Team as a whole
What are the characteristics of a Development Team? Select three most appropriate choices.
- What can be delivered in the Increment resulting from the upcoming Sprint? - How will the work needed to deliver the Increment be achieved?
What are the questions that Sprint Planning answers?
Productivity Creativity Flexibility
What are the three main qualities the team model in Scrum is designed to optimize?
Product Value Maximizer Lead Facilitator of Key Stakeholder Involvement Product Marketplace Expert
What are the three most applicable characteristics of the Product Owner?
- Adaption - Inspection - Transparency
What are the three pillars that uphold Scrum?
- What did I do yesterday that helped the Development Team meet the Sprint Goal? - What will I do today to help the Development Team meet the Sprint Goal? - Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
What are the three questions the Scrum Guide gives as an example that can be used at the Daily Scrum?
- It should choose how best to accomplish their work, rather than being directed by others outside the team - It should have all competencies needed to accomplish the work without depending on others not part of the team.
What are the two essential features a Scrum Team should possess?
Sprint Backlog
What belongs solely to the Development Team?
Artifacts Rules Roles Events
What comprises Scrum?
The Product Backlog
What could be a source of requirements for any changes to be made to the product?
How much work remains till the end of the Sprint.
What does Burn-down Chart show?
How much is known about the Product over time
What does Cone of Uncertainty show?
- Clearly expressing Product Backlog items; - Ordering the items in the Product Backlog to best achieve goals and missions; - Optimizing the value of the work the Development Team performs; - Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next - Ensuring the Development Team understands items in the Product Backlog to the level needed.
What does Product Backlog management include?
Complex work that can include all the suggested options and even more
What does the word "development" mean in the context of Scrum? Select the best option.
- No changes are made that would endanger the Sprint Goal - Quality goals do not decrease - Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
What happens during the Sprint?
- All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog - Any completed and "Done" Product Backlog items are reviewed - If part of the work is potentially releasable, the Product Owner typically accepts it
What happens when a Sprint is cancelled?
A framework within which people can address complex adaptive problems, while delivering valuable products.
What is Scrum?
The sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints
What is the Increment?
The Product Backlog items selected for this Sprint plus the plan for delivering them.
What is the Sprint Backlog?
It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint
What is the Sprint Retro?
A small team of people that is highly flexible and adaptive
What is the essence of Scrum?
- Past performance of the Development Team - The Product Backlog - Projected capacity of the Development Team during the Sprint - The latest product Increment
What is the input to the Sprint Planning? Select four.
Less valuable items at the bottom. (The product owner is responsible for placing the most valuable and clear items at the top of the Product Backlog.
What is the order of items in the Product Backlog?
A revised Product Backlog that defines the probable Product Backlog items for the next Sprint
What is the result of the Sprint Review?
Not more than 10%.
What percentage of the capacity of the Development Team does Product Backlog refinement usually consume?
The Sprint Goal - an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Dev Team on why it is building the Increment.
What provides guidance to the Dev Team on why it is building the Increment?
- Conventions, standards and guidelines of the Organization - Definition of "Done" of other Scrum Teams working on the same Product
What should be taken into account for the Definition of "Done"? Select the two most appropriate items.
- Research and identifying of viable markets, technologies, and product capabilities - Development of products and enhancements - Development of almost everything we use in our daily lives as individuals and societies - Development and sustaining of Cloud and other operational environments - Development of software and hardware - Managing the operation of an organization
Where can Scrum be used? Check all the applicable items.
Dev Team
Who creates the increment?
The Product Owner
Who has the ability to cancel the Sprint?
Dev Team
Who is allowed to change the Sprint Backlog during the Sprint?
- Product Owner - Dev Team - with permission of the Product Owner
Who is allowed to make changes in the Product Backlog? Select two options
The Dev Team
Who is allowed to participate in the Daily Scrum?
Dev Team
Who is responsible for all estimates in the Product Backlog?
Scrum Master
Who is responsible for coping with incomplete artifact transparency?
The Scrum Team - After the Dev Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal.
Who is responsible for crafting the Sprint Goal at the Sprint Planning?
Dev Team
Who is responsible for creation of the Definition of "Done"?
Product Owner
Who is responsible for managing the Product Backlog?
The Product Owner - Tracks total work remaining at least every Sprint Review. Compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal.
Who is responsible for monitoring progress toward high-level goals?
The Scrum Master They do this by helping everyone understand Scrum theory, practices, rules and values.
Who is responsible for promoting and supporting Scrum?
Product Owner - The Product owner is responsible for the Product Backlog, including its content, availability and ordering
Who is responsible for the Product Backlog?
Dev Team
Who is responsible for tracking the total work remaining in the Sprint Backlog to project the likelihood of achieving the Sprint Goal?
The Product Owner The Scrum Master The Dev Team
Who participates in the Sprint Planning?
Scrum Master Product Owner Dev Team Key Stakeholders
Who participates in the Sprint Review?