PSM1 Study Q&A
When might a Sprint be abnormally canceled? A. When the Sprint Goal becomes obsolete. B. When the sales department has an important new opportunity. C. When the Developers feel that the work is too hard. D. When it becomes clear that not everything will be finished by the end of the Sprint.
A. When the Sprint Goal becomes obsolete. Feedback: A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.
A Scrum Team consists of the following: A. Customers B. Product Owner C. Developers D. Users E. Scrum Master
A: Product Owner, Developers, Scrum Master Feedback: The Scrum Team consists of one Scrum Master, one Product Owner, and Developers.
What are two ways a Scrum Master serves to enable effective Scrum Teams? (choose the best two answers) A. By starting and ending the meetings at the proper time. B. By facilitating Developer decision-making. C. By keeping high value features high in the Product Backlog. D. By removing impediments that hinder the Scrum Team.
B. By facilitating Developer decision-making. D. By removing impediments that hinder the Scrum Team. Feedback: The Scrum Master serves the Scrum Team in several ways. Facilitation and removing impediments are examples of ways a Scrum Master helps a team become more effective.
Upon what type of process control is Scrum based? A. Complex B. Empirical C. Defined D. Hybrid
B. Empirical Feedback: Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed.
The CEO asks the Developers to add a "very important" item to a Sprint that is in progress. What should the Developers do? A. Add the item to the current Sprint without any adjustments. B. Inform the other members of the Scrum Team so the team can decide what to do. C. Add the item to the current Sprint and drop an item of equal size. D. Add the item to the next Sprint.
B. Inform the other members of the Scrum Team so the team can decide what to do. Feedback: The items selected for a Sprint have been selected as most valuable with the Product Owner. The items serve the Sprint's goal. No changes should be made that endanger the Sprint Goal. No one external to the Scrum Team can force changes on the Developers.
Which statement best describes a Product Owner's responsibility? A. Directing the Developers. B. Optimizing the value of the work the Scrum Team does. C. Managing the project and ensuring that the work meets the commitments to the stakeholders. D. Keep stakeholders from distracting the Developers.
B. Optimizing the value of the work the Scrum Team does. Feedback: The Product Owner is accountable for maximizing the value of the product and the work of the Scrum Team.
Which of the following are examples of a Scrum Team practicing Scrum poorly or not exhibiting traits of a self-managing Scrum Team? (choose the best three answers) A. The Developers are collaboratively selecting their own work during the Sprint. B. The Developers are working within the boundaries of their organizations functional description and nicely handing off work from analyst to developer to tester to integration. C. Stakeholders attend the Daily Scrum to check on the Scrum Team's progress. D. The Developers have all the skills they need to create a valuable, useful Increment. E. The Developers create their own Sprint Backlog, reflecting all work that is required to meet the Definition of Done. F. The Developers invite external stakeholders to the Sprint Planning to ask them how to turn a Product Backlog item into an Increment via a complete and detailed Sprint Backlog.
B. The Developers are working within the boundaries of their organizations functional description and nicely handing off work from analyst to developer to tester to integration. C. Stakeholders attend the Daily Scrum to check on the Scrum Team's progress. F. The Developers invite external stakeholders to the Sprint Planning to ask them how to turn a Product Backlog item into an Increment via a complete and detailed Sprint Backlog. Feedback: - The Daily Scrum is for the Developers. It should not be used by external stakeholders to check progress. - During Sprint Planning the Scrum Team should be crafting the Sprint Goal based on the set of Product Backlog items selected for the Sprint. The Developers identify the necessary work to meet the Sprint Goal. - Scrum Team members do not have titles, and no sub-teams; such as testing, architecture, or operations are recognized. Accountability belongs with the Scrum Team as a whole, regardless of whether team members have specialized skills.
When many Scrum Teams are working on a single product, what best describes the Definition of Done? A. Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known. B. It depends. C. All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful.
C. All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful. Feedback: The Increment must be valuable and useful. This means that when many Scrum Teams are working on a single product, they are expected to adhere to a single Definition of Done for the Increment.
Who is responsible for managing the progress of work during a Sprint? A. The Product Owner. B. The most junior member of the team. C. The Developers. D. The Scrum Master.
C. The Developers. Feedback: The Developers use the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.
During a Sprint, a Developer determines that the Scrum Team will not be able to complete the items in their forecast. Who should be present to review and adjust the Product Backlog items selected? A. The Scrum Master, the project manager, and the Developers B. The Developers. C. The Product Owner and the Developers. D. The Product Owner and all stakeholders.
C. The Product Owner and the Developers. Feedback: During the Sprint, scope may be clarified and re-negotiated between the Product Owner and the Developers as more is learned. It is important to be transparent when challenges arise since ultimately the entire Scrum Team is accountable for creating a valuable, useful Increment.
Why is the Daily Scrum held at the same time and same place? A. The Product Owner demands it. B. The place can be named. C. The consistency reduces complexity. D. Rooms are hard to book and this lets it be booked in advance.
C. The consistency reduces complexity. Feedback: The Daily Scrum is held at the same time and place each day to reduce complexity.
What is the typical size for a Scrum Team? A. 9. B. Minimum of 7. C. 7 plus or minus 2. D. 10 or fewer.
D. 10 or fewer. Feedback: A Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. Generally smaller teams communicate better and are more productive
The time-box for a Daily Scrum is? A. 15 minutes for a 4-week sprint. For shorter Sprints it is usually shorter. B. 4 hours. C. The same time of day every day. D. 15 minutes. E. Two minutes per person.
D. 15 minutes. Feedback: The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. The Scrum Master serves the Scrum Team by ensuring that all Scrum events take place and are positive, productive, and kept within the timebox.
When should the Developers on a Scrum Team be replaced? A. Every Sprint to promote shared learning. B. As needed, with no special allowance for changes in productivity. C. Never, it reduces productivity. D. As needed, while taking into account a short-term reduction in productivity.
D. As needed, while taking into account a short-term reduction in productivity. Feedback: Scrum Teams typically go through some steps before achieving a state of increased performance. Changing membership typically reduces cohesion, affecting performance and productivity in the short term.
How much work must the Developers complete for each Product Backlog item they select for a Sprint? A. Analysis, design, programming, testing and documentation. B. As much as it can fit into the Sprint. C. All development work and at least some testing. D. Enough so that each Product Backlog item they select meets the Definition of Done.
D. Enough so that each Product Backlog item they select meets the Definition of Done. Feedback: The purpose of each Sprint is to deliver useful and valuable Increments that adhere to the Scrum Team's current Definition of Done.
Who creates the Definition of Done? A. The Scrum Team, in a collaborative effort where the result is the common denominator of all members' definitions. B. The Scrum Master since they are responsible for the productivity of the Developers. C. The Product Owner since they are responsible for the product's success. D. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.
D. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. Feedback: If the Definition of Done for an Increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.
Who has the final say on the order of the Product Backlog? A. The CEO. B. The Scrum Master. C. The Stakeholders. D. The Product Owner. E. The Developers.
D. The Product Owner. Feedback: The Product Owner is the sole person responsible for ordering the Product Backlog.
The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity. (Which one the following answers is FALSE?) A. As a decomposition of the selected Product Backlog items, the Sprint Backlog changes and may grow as the work emerges. B. The Product Owner can help clarify or optimize the Sprint when asked by the Developers. C. The Developers may work with the Product Owner to add or remove work if they find themselves with more or less capacity than expected. D. The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.
D. The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint. Feedback: The Sprint Backlog makes visible all of the work that the Developers identify as necessary to meet the Sprint Goal. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.
Which of the following services is appropriate for a Scrum Master in regard to the Daily Scrum? A. Facilitate in a way that ensures each team member has a chance to speak. B. Lead the discussions of the Developers. C. Ensure that all 3 questions have been answered. D. All answers apply. E. Teach the Developers to keep the Daily Scrum within the 15-minute time-box.
E. Teach the Developers to keep the Daily Scrum within the 15 minute time-box. Feedback: The Scrum Master ensures that the Developers have the event, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep the Daily Scrum within the 15-minute timebox. The Scrum Master enforces the rule that only members participate in the Daily Scrum.
Who is required to attend the Daily Scrum? A. The Developers and Product Owner. B. The Scrum Master and Product Owner. C. The Scrum Team. D. The Developers and Scrum Master. E. The Developers.
E. The Developers. Feedback: Only the people doing the work described on the Sprint Backlog need to inspect and adapt at the Daily Scrum. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers, they will need to be at the Daily Scrum.
The Product Backlog is ordered by: A. Size, where small items are at the top and large items are at the bottom. B. Items are randomly arranged. C. Risk, where safer items are at the top, and riskier items are at the bottom. D. Least valuable items at the top to most valuable at the bottom. E. Whatever is deemed most appropriate by the Product Owner.
E. Whatever is deemed most appropriate by the Product Owner. Feedback: The Product Owner is accountable for effective Product Backlog management. The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.
True or False: The Scrum Team must choose at least one high priority process improvement item, identified during the Sprint Retrospective, and place it in the Sprint Backlog.
False Feedback: An earlier version of the Scrum Guide prescribed the practice of placing one improvement in the Sprint Backlog. This was removed in the 2020 update to the Scrum Guide because it was felt to be too prescriptive. However, if this practice provides value to you then you should adopt it. It is simply not prescribed anymore, but can still be valuable.
True or False: It is mandatory that the product Increment be released to production at the end of each Sprint.
False Feedback: The product Increment should be usable and releasable at the end of every Sprint, but it does not have to be released.
What is the function or purpose of Management in Scrum? A. Identify and remove people that are not working hard enough. B. Monitor the progress of the Developers on the Scrum Team. C. Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to encourage organizational change that fosters empiricism, self-management, bottom-up intelligence, and intelligent product delivery. D. Continually monitor staffing levels of the Scrum Team.
C. Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to encourage organizational change that fosters empiricism, self-management, bottom-up intelligence, and intelligent product delivery. Feedback: Management has no official role or accountability on a Scrum Team. However, management external to the Scrum Team is relevant in setting the vision and strategy to guide the overall direction of the organization.
An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done? A. Without a new vocabulary as a reminder of the change, very little change may actually happen. B. The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. C. Management may feel less anxious. D. All of the above.
A: All of the above
Which Scrum events are time-boxed? A. Refinement. B. Release Retrospective. C. Sprint Review. D. Sprint Planning. E. Sprint Retrospective. F. Release Testing. G. Sprint Testing.
C. Sprint Review. D. Sprint Planning. E. Sprint Retrospective. Feedback: The Scrum Guide states that the Sprint Planning, Sprint Retrospectives, and Sprint Reviews are time-boxed events. Sprints are fixed-length events of one month or less to create consistency, and the Daily Scrum is a 15-minute event.
The timebox for the Sprint Planning event is? A. Whenever it is done. B. 4 hours. C. Monthly. D. 8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
D. 8 hours for a monthly Sprint. For shorter Sprints it is usually shorter. Feedback: Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
True or False: Scrum has a role called "project manager."
False Feedback: A Scrum Team has a Scrum Master, a Product Owner and Developers. As a whole they have all controls needed.
The Developers should have all the skills needed to: A. Do all of the development work, except for specialized testing that requires additional tools and environments. B. Complete the project as estimated when the date and cost are committed to the Product Owner. C. Turn the Product Backlog items they select into an Increment of useful and valuable product functionality.
C. Turn the Product Backlog items they select into an Increment of useful and valuable product functionality. Feedback: The Developers are a group of professionals who do the work of delivering an Increment of done product at the end of each Sprint. As a team, Developers have all of the skills necessary to create a product Increment.
The length of a Sprint should be: A. Short enough to keep the business risk acceptable to the Product Owner. B. Short enough to be able to synchronize the development work with other business events. C. One month or less. D. All of the above.
D. All of the above Feedback: All of these choices are appropriate considerations in determining the length of a Sprint.
Which statement best describes the Sprint Review? A. It is a mechanism to control Developer activity during a Sprint. B. It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next. C. It is a demo at the end of the Sprint for everyone in the organization to check on the work done.
B. It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next. Feedback: Every event in Scrum, besides the Sprint, which is a container for the other events, is an opportunity to Inspect and Adapt.
When does a Developer become the sole owner of an item on the Sprint Backlog? A. Never. All Sprint Backlog items are "owned" by the Developers on the Scrum Team. B. During the Daily Scrum. C. Whenever a team member can accommodate more work. D. At the Sprint Planning event.
A. Never. All Sprint Backlog items are "owned" by the Developers on the Scrum Team. Feedback: The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint, and the set of Product Backlog items selected for the Sprint are collectively owned by the Developers. No individual Developer can claim ownership over an item as this would block communication and collaboration. The Sprint Backlog is updated by the Developers throughout the Sprint as more is learned.
What does it mean to say that an event has a time-box? A. The event can take no more than a maximum amount of time. B. The event must happen at a set time. C. The event must take at least a minimum amount of time. D. The event must happen by a given time.
A. The event can take no more than a maximum amount of time. Feedback: Timeboxed events are events that have a maximum duration.
When does the next Sprint begin? A. When the Product Owner is ready. B. Immediately after the conclusion of the previous Sprint. C. Next Monday. D. Immediately following the next Sprint Planning.
D. Immediately after the conclusion of the previous Sprint. Feedback: A new Sprint starts immediately after the conclusion of the previous Sprint.
When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint? A. Whenever a team member can accommodate more work. B. At the Sprint Planning Event. C. During the Daily Scrum. D. Never. The entire Scrum Team is accountable for creating value every Sprint.
D. Never. The entire Scrum Team is accountable for creating value every Sprint. Feedback: All members of the Scrum Team share in the accountability for creating value every Sprint.
True or False: The purpose of a Sprint is to produce a valuable and useful Increment of working product.
True Feedback: The heart of Scrum is a Sprint, a timebox of one month or less during which a done, useful, and valuable working product Increment is created.
What is the main reason for the Scrum Master to be at the Daily Scrum? A. To make sure every team member answers the three questions. B. To gather status and progress information to report to management. C. They do not have to be there; they only need to ensure the Developers have a Daily Scrum. D. To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.
C. They do not have to be there; they only need to ensure the Developers have a Daily Scrum. Feedback: The Scrum Master only ensures that all Scrum events take place and are positive, productive, and kept within the timebox.
True or False: When multiple Scrum Teams work together on the same product, each team should maintain a separate Product Backlog.
False Feedback: Products have one Product Backlog, regardless of how many Scrum Teams are used. Any other setup makes it difficult for the Developers to determine what they should work on.
Which statement best describes Scrum? A. A cookbook that defines best practices for software development. B. A defined and predictive process that conforms to the principles of Scientific Management. C. A framework for creating complex products in complex environments. D. A complete methodology that defines how to develop software.
C. A framework for creating complex products in complex environments. Feedback: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
The timebox for the Sprint Review is: A. As long as needed. B. 1 day. C. 2 hours. D. 4 hours for a monthly Sprint. For shorter Sprints it is usually shorter. E. 4 hours and longer as needed.
D. 4 hours for a monthly Sprint. For shorter Sprints it is usually shorter. Feedback: Sprint Review is a maximum four-hour timeboxed event for one-month Sprints. For shorter Sprints, the event is usually shorter.
Who is on the Scrum Team? (choose the best three answers) A. The Product Owner. B. The Scrum Master. C. Developers. D. Project Manager.
A. The Product Owner. B. The Scrum Master. C. Developers. Feedback: The Scrum Team consists of the Scrum Master, the Product Owner and Developers. The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
The three pillars of empiricism are: A. Planning, Inspection, Adaptation. B. Transparency, Eliminating Waste, Kaizen. C. Inspection, Transparency, Adaptation. D. Planning, Demonstration, Retrospective. E. Respect For People, Kaizen, Eliminating Waste.
C. Inspection, Transparency, Adaptation. Feedback: 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.
The time-box for the Sprint Planning event is? A. Monthly. B. Whenever it is done. C. 8 hours for a monthly Sprint. For shorter Sprints it is usually shorter. D. 4 hours.
C. 8 hours for a monthly Sprint. For shorter Sprints it is usually shorter. Feedback: Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
Which two things should the Scrum Team do during the first Sprint? A. Determine the complete architecture and infrastructure for the product. B. Develop a plan for the rest of the release. C. Develop and deliver at least one piece of functionality. D. Deliver an Increment of useful and valuable product. E. Create the complete Product Backlog to be developed in subsequent Sprints.
C. Develop and deliver at least one piece of functionality. D. Deliver an Increment of useful and valuable product. Feedback: The heart of Scrum is a Sprint, which is one month or less during which a done, usable, valuable product Increment is created. This applies to every Sprint.
Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly? A. The Scrum Master B. The Project Manager C. The Product Owner D. The Developers
C. The Product Owner Feedback: The Product Owner is the sole person responsible for ordering the Product Backlog. Their responsibilities include making the Product Backlog visible, transparent, and clear to all.
When does a Sprint conclude? A. When the Sprint Retrospective is complete. B. When all the tasks are completed by the Developers. C. When the Product Owner decides enough has been delivered to meet the Sprint Goal. D. When all Product Backlog items meet their Definition of Done.
A. When the Sprint Retrospective is complete. Feedback: The Sprint is a container for the following time-boxed events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Sprints are fixed length events of one month or less to create consistency, and a new Sprint starts immediately after the conclusion of the previous Sprint. The Sprint Retrospective concludes the Sprint, and is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter Though not typical, a Sprint can end if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to end the Sprint prematurely.