PSM I Practice Exam
All the Scrum Teams working on the same product should have the same Sprint length. True or false? True False (Correct)
False. Scrum does not require having aligned Sprints for multiple teams.
What type of leader is the Scrum Master? Servant leader (Incorrect) Strong leader True leader (Correct) Experienced leader
Scrum Masters are true leaders who serve the Scrum Team and the larger organization - Scrum Guide 2020 Please note prior to the 2020 updates the Scrum Master was described as a servant-leader.
Who is responsible for the creation of the Definition of "Done"? The Scrum Team (Correct) The Scrum Master The Developers The Product Owner
"If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product." - Scrum Guide 2020 Please note the Scrum Guide 2017 stated "If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product." As the Developers need to adhere to the Definition of Done and because they have the knowledge on how to develop the product, they are usually best placed to define the Definition of Done but responsibility lies with the whole Scrum Team.
What person or group has the authority to cancel the Sprint? The Developers The Product Owner (Correct) The Scrum Master The Product Owner and the Scrum Master The Key Stakeholders
A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.
If your team manages to complete the Daily Scrum in 5 minutes, can you finish early or spend another 10 on another useful team activity such as the Product Backlog refinement? No Yes (Correct)
All events in Scrum are time-boxed. It means that every event has a maximum duration. However, the Scrum Guide does not require a minimum duration for any event. As Scrum Teams mature, they can do some events faster (e.g. the Sprint Planning or the Sprint Retrospective). If you want to use the time doing the backlog review then that is fine.
What is the Increment? All "Done" items in the Sprint Backlog All items in the Sprint Backlog that could be released regardless of whether the Product Owner decides to actually do it The sum of all the Product Backlog items completed during the Sprint (Incorrect) A stepping stone towards the Product Goal and an additive to all prior increments which integrates successfully. (Correct)
An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.
How are "Developers" defined in Scrum Developers, researchers, analysts and scientists Software Developers only Anyone who gets value from Scrum (Correct) Architects, coders and all other technical people who contribute to the creation of applications and software Software and hardware developers
As Scrum's use spreads, developers, researchers, analysts, scientists, and other specialists do the work. We use the word "developers" in Scrum not to exclude, but to simplify. If you get value from Scrum, consider yourself included. "Developers, researchers, analysts and scientists" is not correct on because this is not an exhaustive list
As the Sprint Planning meeting progresses, The Developers sees the work is greater than they can handle in this Sprint. Select 2 valid actions Consider working overtime during this Sprint Recruit additional Developers Remove or change selected Product Backlog items (Correct) Cancel the Sprint Ensure the Product Owner is aware. The Scrum Team monitors the progress throughout the Sprint (Correct)
As you are in Sprint Planning you should be choosing work items that can be completed in one Sprint, you have the opportunity now to Plan correctly and remove or change any Product Backlog items you feel cannot be done in this Sprint. Also the Scrum Framework ensures opportunities for inspection and adaption, you will be inspecting/monitoring progress through the Sprint and adapting. Scrum enables proper planning, this should mitigate the need for overtime and additional resource. If this is needed something has gone wrong and should be discussed in the Sprint Retrospective.
Who is responsible for tracking the total work remaining at the Daily Scrum? The Scrum Master The Scrum Master The Product Owner The Developers (Correct) The Product Owner and the Development Team
At any point in time in a Sprint, the total work remaining in the Sprint Backlog can be summed. The Developers track this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal. By tracking the remaining work throughout the Sprint, the Scrum Team can manage its progress.
What does Burn-down Chart show? Hierarchy of tasks that comprise a project The evolution of the amount of uncertainty during a project Dependencies, start times and stop times for project tasks How much work remains till the end of the Sprint (Correct)
Burn-down chart shows the evolution of remaining effort against time.
Who participates in the Sprint Review? Select all applicable. The Organization Senior Managers Stakeholders (Correct) Developers (Correct) The Product Owner (Correct) The Scrum Master (Correct)
During the Sprint Review, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment
Of the below which are correct statements that explain what happens during the Sprint? Scope may be clarified and re-negotiated between the Product Owner as more is learned (Correct) Quality goals do not decrease (Correct) No changes are made that would endanger the Sprint Goal (Correct) Sprint scope is defined at the Sprint Planning and cannot be changed The Sprint Goal is changed frequently to reflect the status of the remaining work
During the Sprint: No changes are made that would endanger the Sprint Goal Quality does not decrease The Product Backlog is refined as needed Scope may be clarified and renegotiated with the Product Owner as more is learned.
Scrum recommends using and adapting the Scrum components and rules that work for a particular project or team. Adjusting Scrum to work best for you is encouraged. True False (Correct)
Each component within the Scrum framework serves a specific purpose and is essential to Scrum's success and usage.
Should the Daily Scrum be skipped if there is nothing that needs to be discussed? Yes No (Correct)
Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts. These events are specifically designed to enable the transparency required. Failure to operate any events as prescribed results in lost opportunities to inspect and adapt. Events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.
What is the Scrum Team expected to achieve in Sprint 0? A plan to progress for the following Sprints A list of all the access and the technologies they will need. There is no Sprint 0, they are expected to produce an increment. (Correct)
Every sprint should result in a useable, and potentially releasable product Increment no matter how small, even the first Sprint. There is no Sprint 0 in Scrum.
True or false, the Definition of "Done" is created during the first Sprint and should remain unchanged until the Product release? False (Correct) True
False. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate. Scrum 2017 During the Sprint Retrospective, the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The Scrum Team identifies the most helpful changes to improve its effectiveness. Scrum 2020
The Scrum Master should instruct the Developers on how to turn Product Backlog items into smaller Sprint Backlog items. False (Correct) True
For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value.
Who is responsible for time and effort estimates in the Sprint Backlog? The Product owner and the Scrum Master The Product Owner Experienced Senior Developers only The Scrum Team The Developers (Correct)
For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value.
The Scrum Master is a true leader, how does he or she serve the Organization? Select the three most appropriate. Making sure the key stakeholders are invited on all Scrum Reviews within organization Leading, training, and coaching the organization in its Scrum adoption (Correct) Mixing experienced developers and junior specialists across different development teams in the organization to speed up Scrum adoption Removing barriers between stakeholders and Scrum Teams (Correct) Planning and advising Scrum implementations within the organization (Correct)
From the Scrum Guide 2020 The Scrum Master serves the organization in several ways, including: Leading, training, and coaching the organization in its Scrum adoption; Planning and advising Scrum implementations within the organization; Helping employees and stakeholders understand and enact an empirical approach for complex work; and, Removing barriers between stakeholders and Scrum Teams.
When must an adjustment be made if an inspector determines that one or more aspects of a process has deviated outside of tolerable limits? The deviations should be discussed at the Daily Scrum and then an adjustment must be made After clarifying all the details with the Product Owner After Scrum Master approval As soon as possible to minimize further deviation (Correct)
If any aspects of a process deviate outside acceptable limits or if the resulting product is unacceptable, the process being applied or the materials being produced must be adjusted. The adjustment must be made as soon as possible to minimize further deviation.
The product is experiencing many bugs in testing. Is it normal to have a dedicated Sprint to remove all technical debt and prepare the Product for the upcoming release? Yes No (Correct)
It is not normal. The Scrum team delivers at least one 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.
When multiple Scrum Teams are working on the same product, should all of their increments be integrated every Sprint? Yes, otherwise the Nexus Product Owner may not be able to accurately inspect what is done (Correct) Yes, but only for those Scrum Teams whose work has dependencies on each other. No, that requires too much work and must be done in a hardening Sprint. No, each Scrum Team stands alone.
Multiple Scrum Teams may require a Nexus team to integrate the increments. The Nexus team also follows the Scrum Framework. "The Integrated Increment represents the current sum of all integrated work completed by a Nexus. The Integrated Increment must be usable and potentially releasable which means it must meet the definition of "Done". The Integrated Increment is inspected at the Nexus Sprint Review." - Nexus Guide
What do the Developers have sole responsibility for? The Product Backlog The Increment The Definition of Done The Sprint Backlog (Correct)
Only the Development Team should change its Sprint Backlog during a Sprint. The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum.
What does Product Backlog management include? Select the three most applicable items as per the Scrum Guide: Moving Product Backlog items into the Sprint Backlog Presenting Product Backlog items to the Key Stakeholders Ordering Product Backlog items (Correct) Creating and clearly communicating Product Backlog items (Correct) Developing and explicitly communicating the Product Goal (Correct)
Product Backlog management includes: Developing and explicitly communicating the Product Goal; Creating and clearly communicating Product Backlog items; Ordering Product Backlog items; and, Ensuring that the Product Backlog is transparent, visible and understood.
Which three are the most applicable characteristics of the Product Owner? Product Value Maximizer (Correct) Lead Scrum evangelist in the Organization Lead Facilitator of Key Stakeholder Involvement (Correct) Facilitator of Scrum events Product Marketplace Expert (Correct)
Product Value Maximizer Lead Facilitator of Key Stakeholder Involvement Product Marketplace Expert
Which of the below features does the Scrum Team possess? It should use tools, processes and techniques approved by the Organization It should have all competencies needed to accomplish the work without depending on others not part of the team (Correct) It should choose how best to accomplish their work, rather than being directed by others outside the team (Correct) It should be flexible enough to complete all the work planned for the Sprint even if some team members are on vacation
Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.
A Developer is not getting along with the team and creating a hostile environment. Who should fix the situation? The Scrum Team as a whole, but the Scrum Master may take the lead on resolving the issue (Correct) As a manager the Product Owner is responsible The Scrum Master. He or She is responsible as the Developer is creating an impediment to progress (Incorrect) The hiring manager is responsible because they brought the Developer into the team.
Scrum Teams are self-managing and empowered, so it is The Scrum Team's responsibility to work together and solve any internal conflicts. This is another tricky question. The question asks "who should fix the problem". It can be any member of the Scrum Team but the Scrum Master should definitely be involved. The Scrum Master serves the Scrum Team by "Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox" and the Scrum Master is accountable for the Scrum Team's effectiveness. If you get this in the assessment pay very close attention to how it is worded as the answer could be the Scum Master. The Scrum Team should try and sort the issue without leaving it totally to the Scrum Master.
Does Scrum allow additional meetings between the Developers in addition to the Scrum Events? No Yes (Correct)
Scrum allows additional meetings if they facilitate achieving the Sprint Goal. Daily Scrums improve communications, identify impediments, promote quick decision-making, and consequently eliminate the need for other meetings. The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint's work.
What is Scrum? A sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards. A lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. (Correct) A software development methodology which is intended to improve software quality.
Scrum is a framework for complex problems.
What is Scrum built upon? Scrum is built upon by the collective intelligence of the people using it (Correct) Many years of refinement in practice through Software development teams since the 1990s Built upon the knowledge of the founder's Ken Schwaber and Jeff Sutherland Using other development methods and framework, Scrum has been built upon their successes in practice
Scrum is built upon by the collective intelligence of the people using it. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.
What are the three pillars that uphold every implementation of empirical process control? Self-organization Adaptation (Correct) Transparency (Correct) Agility Inspection (Correct) Cross-functionality
Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.
Scrum is founded on: Empiricism (Correct) Empirical criticism Common sense Kanban system
Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials.
Is Scrum a process, technique, framework or method? Technique Framework (Correct) Process Method
Scrum is not a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques.
Scrum makes visible the relative efficacy of ...., so that improvements can be made. Select three environment (Correct) work tasks (Incorrect) current management (Correct) work techniques (Correct) organization competitor
Scrum makes visible the relative efficacy of current management, environment, and work techniques, so that improvements can be made.
What knowledge helps with selecting how much can be completed within a Sprint and Sprint forecasts? Projected capacity of the Scrum Team during the Sprint (Correct) The Product Owner's experience Past performance of the Developers (Correct) The Definition of Done (Correct) Feedback from the Key Stakeholders The Organizations policies The amount of development debt currently in the product
Selecting how much can be completed within a Sprint may be challenging. However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts.
What topics does the Sprint Planning aim to answer? Select Three. What new technologies could be used to speed up the Development velocity? Who will be responsible for each item in the Sprint Backlog? Why is this Sprint valuable? (Correct) How will the work needed to deliver the Increment be achieved? (Correct) What can be delivered in the Increment resulting from the upcoming Sprint? (Correct) What is the size of the Technical Debt and how it could be removed?
Sprint Planning addresses the following topics: Topic One: Why is this Sprint valuable? Topic Two: What can be Done this Sprint? Topic Three: How will the chosen work get done?
What questions does Sprint Planning answer? Select three. Why is the Sprint Valuable? (Correct) Who will be responsible for each item in the Sprint Backlog? How will the work needed to deliver the Increment be achieved? (Correct) What can be delivered in the Increment resulting from the upcoming Sprint? (Correct) What new technologies could be used to speed up the Scrum Team's velocity?
Sprint Planning answers the following: What can be delivered in the Increment resulting from the upcoming Sprint? How will the work needed to deliver the Increment be achieved? The Product Owner proposes how the product could increase its value and utility in the current Sprint.
How long should the Sprint Planning be? Until all the Items in the Sprint Backlog are decomposed to units of one day or less Not more than 10% of the capacity of the Scrum Team Not more than 8 hours (Correct) Not more than 4 hours
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. There is no need to decompose all the Items in the Sprint Backlog. It can be done only for the first days of the Sprint.
The time-box for the Daily Scrum is how long? Not limited. Every Scrum Team member should have enough time to answer the three Main Questions. 15 minutes (Correct) 20 minutes 25 minutes
The Daily Scrum is a 15-minute time-boxed event.
The Scrum Guide recommends increasing the Daily Scrum timebox dependant on the size of the Scrum Team. The more Developers the more time will be needed. True False (Correct)
The Daily Scrum is a 15-minute timeboxed event for a Scrum Team of any size.
The Definition of "Done" helps the Scrum Team. How does it help? Select three most applicable items. DoD helps in inspection and adaptation (Incorrect) A formal description of the state of the Increment (Correct) DoD creates transparency (Correct) DoD helps to calculate velocity of the Scrum Team Keeps quality standards consistent through multiple Scrum teams (Correct)
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the Definition of Done, an Increment is born. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done. The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment
Select the two meetings in which people outside the Scrum Team are allowed to participate. The Sprint Review (Correct) The Daily Scrum The Sprint Retrospective The Sprint Planning (Correct)
The Developers may invite other people to attend the Sprint Planning in order to provide technical or domain advice. The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting
What is the Developers' source of requirements for the product? The Key Stakeholders The CEO of the Organization The Product Backlog (Correct)
The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.
Choose the correct order of items in the Product Backlog? The recently added items at the top The less clear items at the top At the discretion of the Product Owner but the order needs to be communicated to the Scrum Team. (Correct) Alphabetical
The Product Backlog needs to be in an order, this order is up to the Product Owner. It is common for the least detailed to be at the bottom and the most detailed at the top ready for selection into a sprint.
Who has accountability for the Product Backlog? The Product Owner (Correct) The Product Owner and the Developers The Developers The Scrum Master and the Developers The Product Owner and The Scrum Master The Scrum Master
The Product Owner also accountable for effective Product Backlog management including: Developing and explicitly communicating the Product Goal; Creating and clearly communicating Product Backlog items; Ordering Product Backlog items; and, Ensuring that the Product Backlog is transparent, visible and understood.
Who is allowed to make changes in the Product Backlog? Select two options. The Developers The Key Stakeholders The Product Owner (Correct) Anyone, but only with permission of the Product Owner (Correct) The Scrum Master
The Product Owner is the sole person accountable for the Product Backlog. However, he or she can delegate some work related to product backlog management so long as he or she gives permission.
Who is responsible for managing the Product Backlog? The Product Owner (Correct) The Developers The Key Stakeholders The Scrum Master
The Product Owner is the sole person responsible for managing the Product Backlog
Who in the Scrum team is responsible for monitoring progress toward high-level goals? The Developers (Incorrect) The Scrum Team The Scrum Master and the Developers The Product Owner (Correct) The Scrum Master
The Product Owner tracks total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders.
Select the five Scrum Values. Respect (Correct) Courage (Correct) Focus (Correct) Commitment (Correct) Openness (Correct) Effectiveness
The Scrum Guide recognizes the following Scrum Values: commitment, courage, focus, openness and respect.
Can the Sprint Planning session be finished with work planned only for the first days of the Sprint where that work consists of units of one day or less? No, all items in the Sprint Backlog should be decomposed to units of one day or less by the end of the Sprint Planning Yes, if the remaining work is also estimated, maybe in bigger units (Correct)
The Scrum Guide requires only the work planned for the first days of the Sprint is decomposed by the end of the Sprint Planning, often to units of one day or less. However, the Developers should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-managed team to accomplish the Sprint Goal and create the anticipated Increment.
In the Daily Scrum the Scrum Master does which of the following? Select all that apply: Teaches the Team to keep the Daily Scrum within the 15-minute time-box (Correct) Ensures that the meeting goes ahead (Correct) Is responsible for conducting the Daily Scrum If others are present at the Daily Scrum, ensures that they do not disrupt the meeting resulting in an overrun (Correct)
The Scrum Master ensures that all Scrum events take place and are positive, productive, and kept within the timebox
A Scrum Master is basically the same thing as a Project Manager (PM) False (Correct) True
The Scrum Master is a different role to a traditional Project Manager and has different responsibilities.
True of false, the Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team. False (Correct) True
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. Remember the Scrum Master serves the Organization by "Leading, training, and coaching the organization in its Scrum adoption".
From the Scrum Team who is most responsible for promoting and supporting Scrum? The Product Owner The Scrum Master and the Product Owner The Developers The Scrum Team The Scrum Master (Correct)
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.
How does the Scrum Master serve the Product Owner? Select the three most appropriate Facilitating Scrum events as requested or needed (Incorrect) Helping the Scrum Team understand the need for clear and concise Product Backlog items (Correct) Finding techniques for effective Product Backlog management (Correct) Removing barriers between stakeholders and Scrum Teams Understanding product planning in an empirical environment (Correct)
The Scrum Master serves the Product Owner in several ways, including: Helping find techniques for effective Product Goal definition and Product Backlog management; Helping the Scrum Team understand the need for clear and concise Product Backlog items; Helping establish empirical product planning for a complex environment; and, Facilitating stakeholder collaboration as requested or needed.
The Product Owner is distant and not providing enough guidance to Scrum team on the business needs of the increment. What should the Scrum Master do? Report the Product Owner's behaviour to their manager Help the Product Owner find techniques for effective Product Backlog management (Correct) Find a proxy Product Owner End the Sprint and restart once the Product Owner is able to spend more time with the Scrum Team Discuss the issue in the Sprint Retrospective (Correct)
The Scrum Master serves the Product Owner in several ways, including: Helping find techniques for effective Product Goal definition and Product Backlog management; Helping the Scrum Team understand the need for clear and concise Product Backlog items; Helping establish empirical product planning for a complex environment; and, Facilitating stakeholder collaboration as requested or needed. So the Scrum Master must help the Product Owner to become more involved in the Scrum process. The Sprint Retrospective is the Scrum Team's opportunity to discuss the issue and find a resolution to try for the next Sprint.
Scrum Masters are true leaders who serve the Scrum Team and the larger organization, how does he or she serve the Scrum Team? Select the four most appropriate. Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done (Correct) Causing the removal of impediments to the Scrum Team's progress (Correct) Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox (Correct) Coaching the team members in self-management and cross-functionality (Correct) Helping find techniques for effective Product Goal definition and Product Backlog management (Incorrect) Adding or removing Developers in accordance with team velocity changes
The Scrum Master serves the Scrum Team in several ways, including: Coaching the team members in self-management and cross-functionality; Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done; Causing the removal of impediments to the Scrum Team's progress; and, Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox. Please note "Helping find techniques for effective Product Goal definition and Product Backlog management" is an example of how the Scrum Master serves the Product Owner, the question asks how the Scrum Master serves the Scrum Team specifically.
For a new product, 10 developers and the Product Owner have been assigned. As the Scrum Master how should you advise they be divided into teams? Choose all applicable options: 1 team of 10 people (because there is never a reason to divide) 2 teams of 6 and 4 people (after a short meeting the developers decided this is the best option) (Correct) 2 teams of 6 and 4 people (because it is good to have a separate QA team) 3 teams of 4, 3 and 3 people (each team is cross-functional) (Correct)
The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better and are more productive. If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, and Product Owner. 1 team of 10 people could be allowed if the Scrum Team has determined it is appropriate, but this answer is not correct as the statement of never needing to divide is not correct.
Some Key Stakeholders have asked the Scrum Master if they can attend the Sprint Planning to provide technical or domain advice. Should the Scrum Master allow or deny this? Allow (Correct) Deny
The Scrum Team may invite other people to attend Sprint Planning to provide advice.
Why should progress towards the goals be conducted frequently? To raise awareness to the Developers that are underperforming To detect undesirable variances or problems (Correct) To frequently report back to the Key Stakeholders To ensure the Sprint Goal will be met within the Sprint (Incorrect)
The Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems.
Select all the Scrum Artifacts Increment (Correct) Sprint Backlog (Correct) The Sprint Goal The list of removed impediments Product Backlog (Correct)
The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.
Who is allowed to change the Sprint Backlog during the Sprint? The Scrum Master The Developers (Correct) The Lead Developer The Product Owner
The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum.
What is the Sprint Backlog? The Product Backlog items selected for this Sprint The Product Backlog items selected for this Sprint plus the Team Backlog items The plan for delivering Product Backlog items The Sprint Goal, Product Backlog items selected for this Sprint plus the plan for delivering them (Correct)
The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).
What provides guidance to the Developers on why they are building the Increment? The Product Owner The Sprint Goal (Correct) The Sprint Backlog The Scrum Master
The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also creates coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives.
How long are the timeboxes for the Sprint Retrospective and the Sprint Review? 3 and 4 hours respectively (Correct) 3 hour time-box for each 4 and 3 hours respectively 4 hour time-box for each
The Sprint Review is at most a four-hour meeting for one-month Sprints. The Sprint Retrospective is at most a three-hour meeting for one-month Sprints.
Which are all the FORMAL events to inspect and adapt. The Sprint The Sprint Retrospective (Correct) The Daily Scrum (Correct) The Sprint Review (Correct) The Sprint Planning (Correct)
The Sprint is an event and also a container for all other events. Each event in a Sprint is a formal opportunity to inspect and adapt Scrum artifacts. As Scrum puts it: "Scrum prescribes four formal events for inspection and adaptation, within a containing event, the Sprint" These events are specifically designed to enable the transparency required. Failure to operate any events as prescribed results in lost opportunities to inspect and adapt. Inspection and adaption should happen throughout the Sprint.
True or False. It turned out there is a lot more work to do in the current Sprint than was estimated. If an item in the Sprint Backlog cannot be finished by the end of the Sprint, the Sprint is cancelled. False (Correct) True (Incorrect)
The Sprint is cancelled only in the case if the Sprint Goal became obsolete. If some work could not be done, the Sprint Backlog should be re-negotiated between the Product Owner and the Developers.
As a Scrum Master you are introducing Scrum to a new team. The new team does not see the need in the Sprint Retrospective. What action should you take? Agree and respect with the decision from the self-managed team Consult with the Product Owner to see if he/she is happy to neglect the Sprint Retrospective Involve Senior Management and host a meeting between them and the Developers Ensure that all Scrum events take place (Correct)
The Srum Master serves the Scrum Team by "Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.". The Scrum Master role is one of training as the Scrum Master serves the Organization by "Leading, training, and coaching the organization in its Scrum adoption". It should be within the Scrum Master's capabilities to lead and coach the Scrum Team in the value of the Sprint Retrospective.
At the Sprint Retrospective some improvements were identified. What should be done? Select the best option. Assign responsible team members for every improvement. Check the progress at the next Retrospective. Assign a responsible team member for at least one improvement. Check the progress at the next Retrospective. Consider adding the most impactful improvements to the next Sprint Backlog but certainly make sure they are addressed as soon as possible. (Correct) Make sure the Sprint Backlog for the next Sprint includes all the improvements.
The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
Why does Scrum have a Sprint Retrospective? It is an opportunity for the Scrum Team to plan ways to increase quality and effectiveness (Correct) It is a meeting where the Developers synchronizes activities and creates a plan for the next 24 hours It is a meeting to inspect the Increment and adapt the Product Backlog if needed It is the key inspect and adapt meeting (Incorrect)
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
What happens during the Sprint Retrospective? The Scrum Team inspects how the last Sprint went (Correct) The Scrum team discuss specific backlog items in depth The Scrum Team identifies the most helpful changes to improve its effectiveness. (Correct) The Scrum Team reviews their ways of working and how to improve (Correct) The Scrum Team plans ways to increase quality and effectiveness (Correct) The Product Owner asks Developers to account for any failures to the Key Stakeholders
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
Sprint Retrospective is to: (choose three) Create a plan for implementing improvements to the way the Scrum Team does its work (Correct) Get technical or domain advice from specialists invited by the Developers or The Scrum Master Inspect how the last Sprint went with regards to people, relationships, process, and tools (Correct) Identify and order the major items that went well and potential improvements (Correct) Get feedback from the Key Stakeholders invited by the Product Owner
The purpose of the Sprint Retrospective is to: Inspect how the last Sprint went with regards to people, relationships, process, and tools; Identify and order the major items that went well and potential improvements; and, Create a plan for implementing improvements to the way the Scrum Team does its work. Continue Retake test
If the Sprint Review is successful what is the resulting output? A list of improvements that the Scrum Team will implement in the next Sprint An understanding of what has changed in their environment and a plan on what to do next. The Product Backlog may be adjusted to meet new opportunities. (Correct) Common understanding of what can be delivered in the Increment and how will the work needed to deliver the Increment be achieved Common understanding of progress toward the Sprint Goal and how progress is trending toward completing the work in the Sprint Backlog
The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a working session and the Scrum Team should avoid limiting it to a presentation. "Common understanding of what can be delivered in the Increment and how will the work needed to deliver the Increment be achieved": This is related to planning "Common understanding of progress toward the Sprint Goal and how progress is trending toward completing the work in the Sprint Backlog": This mentioned the Sprint Backlog and progress towards the Sprint Goal but at the Review stage, the Sprint has already finished.
Sprint Planning only requires the Product Owner and the Developers. There is nothing to do for the Scrum Master. True False (Correct)
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.
During the Daily Scrum the Scrum Master should make sure each team member should answer the three main questions: What did I do yesterday? What will I do today? Do I see any impediment? True False (Correct)
There is not a prescribed structure set by the Scrum Guide. The structure of the Daily Scrum is set by the Scrum Team and can be done in any way so long as it focuses on progress toward the Sprint Goal. Some Scrum Teams will use questions, some will be more discussion based. The questions are a useful guide, but other ways of conducting the meeting are also possible. The Scrum Master helps to maximize the value created by the Scrum Team and removes impediments.
Management external to the Scrum Team wants to be involved in the Daily Scrum. Which are the best answers? If present the Scrum Master ensures that they do not disrupt the meeting (Correct) The Product Owner represents their opinions The Scrum Master is the Management The Senior Managers can give an update at the start of the Daily Scrum The Scrum Team self-manages and is the only management required at the Daily Scrum. (Correct)
This is a tricky question and you are likely to get something similar in the PSM. With questions like these remember to stick to what you absolutely know from the Scrum Guide, which in this case is the Developers self-manages, meaning they internally decide who does what, when and how. The Product Owner may well represent their opinions or the PO may not. Remember the Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting, and it is kept within the timebox.
What is the definition of a Product as given by the Scrum Guide? A product is a vehicle to deliver value. A product could be a service, a physical product, or something more abstract. (Correct) A product is a tangible asset that the customer has asked for A product is the output of work from the Scrum Team. It is a useable physical product, service or application that is the result of the original requirements that the Scrum Team worked from. (Incorrect)
Under commitment to the Product Goal in the Scrum Guide 2020: A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.
Select all of the most appropriate characteristics of the Developers Scrum recognizes no sub-teams or hierarchies (Correct) They are managed by the Scrum Master They hold each other accountable as professionals (Correct) They must adhere to the Definition of Done (Correct) They have broad skills and vary with the domain of the work (Correct)
Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Developers are always accountable for: Creating a plan for the Sprint, the Sprint Backlog Instilling quality by adhering to a Definition of Done Adapting their plan each day toward the Sprint Goal Holding each other accountable as professionals The specific skills needed by the Developers are often broad and will vary with the domain of work.
What improves the Scrum Team's focus and consistency? Well defined user stories (Incorrect) The experience of the Scrum Team Working at a sustainable pace (Correct) Visible work items
Working in Sprints at a sustainable pace improves the Scrum Team's focus and consistency - Scrum 2020 Visible work items will help with focus but the question also asks for consistency. User stories are not mentioned in the Scrum Guide The experience of the Scrum Team will likely help with focus and consistency as they may be able to estimate better but this may not necessarily be the case. Remember to choose the answer that is in the Scrum Guide
Does Scrum allow the Product Owner and the Scrum Master to also be a Developer? No Yes (Correct)
Yes. Scrum does not prohibit the Product Owner or the Scrum Master do development work. However, it could create a conflict of interest.