The timebox for a Daily Scrum is?
(choose the best answer)
4 hours.
The same time of day every day.
Two minutes per person.
15 minutes.
The Scrum Guide states that "The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours."1Â The Daily Scrum is a quick and simple planning meeting designed to keep everyone in the loop with how other team members are getting on. It ensures that team members are fully aligned with each other and on track to hit the Sprint Goal.
References:
Who is accountable for managing the progress of work during a Sprint?
(choose the best answer)
The Developers.
The most junior member of the team.
The Scrum Master.
The Product Owner.
The Developers are accountable for managing the progress of work during a Sprint, as they are the ones who plan, execute, and deliver the work. The Scrum Guide states that "The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."1 The Developers are also responsible for conducting the Daily Scrum, a 15-minute event for the Developers to synchronize activities and create a plan for the next 24 hours.1 The Developers are self-managing, which means they decide how best to accomplish their work, rather than being directed by others outside the Scrum Team.1
References:
In order to maximize the value of the product, a Product Owner needs awareness of the following: (choose the best answer)
Competitive research.
Customer feedback.
Product vision.
Forecasting & feasibility.
All of the above.
None of the above.
 In order to maximize the value of the product, a Product Owner needs awareness of the following:
References:
True or False: A Product Owner with multiple teams working on one product should maintain separate Product Backlogs for each team.
True
False
References:
When multiple Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint?
(choose the best answer)
Yes, in order to accurately inspect what is done.
Yes, but only for Scrum Teams whose work has dependencies.
No, each Scrum Team stands alone.
No, that is far too hard and must be done in a hardening Sprint.
When multiple Scrum Teams are working on the same product, they should integrate their Increments every Sprint because:
References:
Which of the following practices might help the Product Owner minimize waste in developing
and sustaining the Product Backlog?
(choose the best two answers)
Avoid distracting the Scrum Team by maintaining newly gathered Product
Backlog items in a separate Product Backlog until they are fully understood.
Hand off ownership of the Product Backlog to someone else.
Remove items from the Product Backlog that have not been addressed in a long
time.
Only fully describe Product Backlog items when it seems likely they will be
implemented.
The practices that might help the Product Owner minimize waste in developing and sustaining the Product Backlog are:
Other options, such as avoiding distracting the Scrum Team by maintaining newly gathered Product Backlog items in a separate Product Backlog until they are fully understood or handing off ownership of the Product Backlog to someone else, are not practices that might help minimize waste in developing and sustaining the Product Backlog. They may actually create more waste by reducing transparency, collaboration, alignment, or ownership.
References:
Which topics should be discussed in the Sprint Review?
(choose the best answer)
The Scrum process, and how it was used during the Sprint.
Coding and engineering practices.
The product Increment.
All of the above.
The main topic of discussion is the product Increment, which is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints1. The product Increment is demonstrated and inspected by the attendees, and feedback is collected to inform the next Sprint Planning12. The Sprint Review may also include other topics, such as the Product Backlog, the Product Goal, the market conditions, the budget, and the timeline, but the product Increment is the essential topic1234. The Scrum process, and how it was used during the Sprint, is not a topic for the Sprint Review, but rather for the Sprint Retrospective, which is a separate event where the Scrum Team inspects and adapts its way of working1. Coding and engineering practices are also not relevant for the Sprint Review, as they are internal aspects of the Development Team that do not affect the value of the product Increment1. Therefore, the correct answer is C. The product Increment.
Which of the following might the Scrum Team discuss during a Sprint Retrospective?
(choose the best answer)
Methods of communication.
The way the Scrum Team does Sprint Planning.
Skills needed to improve the Developers ability to deliver.
The Definition of Done.
All of the above.
Scrum
During the Sprint Retrospective, the Scrum Team discusses how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done123. This includes methods of communication, the way the Scrum Team does Sprint Planning, skills needed to improve the Developers’ ability to deliver, and the Definition of Done123.
Which three of the following are true about Scrum?
(choose the best three answers)
Scrum implements self-management by replacing Project Managers with Scrum
Masters.
Scrum is based on empiricism and lean thinking.
Scrum is a framework for developing and sustaining complex products.
Scrum is a methodology where you can pick and choose which parts of Scrum
you think will work for your environment.
Each component of Scrum serves a specific purpose and is essential to Scrum's
success and your usage of Scrum to develop complex products.
The following are true about Scrum:
References:
Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency?
(choose the best answer)
The Product Backlog is only updated at the Sprint Review, when both the Scrum
Team and the stakeholders are available.
Product Backlog items should hold no more than 8 points of work, which is the
average in the range of acceptable sizes of 1, 2, 3, 5, 8, and 13.
Product Backlog items must be sized such that the highest ordered items are no bigger than a Sprint.
The Product Backlog is only updated at a release planning meeting with the
stakeholders and the change control board present.
The Product Backlog is continually kept up to date with the most recent insights.
The Scrum Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because:
References:
During the Sprint Retrospective a Scrum Team has identified several high priority process
improvements. Which of the following statements is most accurate?
(choose the best answer)
The Scrum Team may add the items to the Sprint Backlog for the next Sprint.
The Scrum Team should decline to add a process improvement to the Sprint Backlog
when things are running smoothly.
The Scrum Team should choose at least one high priority process improvement to
place in the Product Backlog.
The Scrum Master selects the most important process improvement and places it in
the Sprint Backlog
The Scrum Guide states that "By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself."1 This means that the Scrum Team may add the high priority process improvements to the Sprint Backlog for the next Sprint, as part of their plan to deliver the Increment and achieve the Sprint Goal. The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.1
References:
Who is on the Scrum Team?
(choose all that apply)
Scrum Master.
Product Owner.
Developers.
Project Manager.
None of the above.
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. 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 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. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a “Done†Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.
References:
What is the timebox for the Sprint Planning event?
(choose the best answer)
Monthly.
Whenever it is done.
8 hours for a one-month Sprint.
4 hours for a one-month Sprint.
References:
What typically happens if the Product Backlog is not sufficiently clear at Sprint Planning?
(choose the best answer)
The Product Owner should select the Sprint Goal for the Scrum Team so that work can begin.
The Developers will find it difficult to create a Sprint forecast they are confident they can meet.
Nothing in particular.
The Scrum Master should not allow this to happen. Look for a new Scrum Master and re-start the Sprint.
Sprint Planning is canceled so refinement can be done first.
 If the Product Backlog is not sufficiently clear at Sprint Planning, the Developers will find it difficult to create a Sprint forecast they are confident they can meet. This is because:
Other options, such as the Product Owner selecting the Sprint Goal for the Scrum Team so that work can begin, nothing in particular happening, the Scrum Master not allowing this to happen or looking for a new Scrum Master and re-starting the Sprint, or Sprint Planning being canceled so refinement can be done first, are not valid answers as they do not reflect what typically happens or what should happen in Scrum.
References:
Which statement best describes Scrum?
(choose the best answer)
A defined and predictive process that conforms to the principles of Scientific Management.
A complete methodology that defines how to develop software.
A framework to generate value through adaptive solutions for complex problems.
A cookbook that defines best practices for software development.
You are the Scrum Master of a new, to be developed Product. Development is going to require
45 people. What is a good first question for you to suggest the group thinks about when forming into teams?
(choose the best answer)
What is the right mixture of senior and junior people on each team?
Who are the subject matter experts on each team?
Who are going to be the team leads?
How will we make sure all teams have the right amount of expertise?
When forming a Scrum team, it is important to ensure that the team has all the skills and knowledge necessary to deliver a working product12. The Scrum team should be cross-functional and self-managing, without relying on external experts or team leads34. Therefore, the question of how to make sure all teams have the right amount of expertise is a good first question to consider when forming into teams.
Which is NOT a valid consideration when ordering a Product Backlog?
(choose the best answer)
Dependencies on other Product Backlog items.
Importance to customers.
Alignment with business strategy and goals.
Tools and techniques.
Risk.
References:
Who owns the Sprint Backlog?
(choose the best answer)
The Scrum Master.
The Scrum Team.
The Product Owner.
The Developers.
According to Scrum.org, the Developers own the Sprint Backlog12. The Sprint Backlog is a plan by and for the Developers1. 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 Goal1. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned1.
A Scrum Team is a cohesive unit of professionals that consists of which of the following?
(choose the best three answers)
One Product Owner.
Developers.
Customers.
One Scrum Master.
Users.
The Scrum Guide defines a Scrum Team as “a cohesive unit of professionals focused on one objective at a time, the Product Goalâ€. It also states that “the Scrum Team consists of one Scrum Master, one Product Owner, and Developersâ€. Therefore, the correct answer is A, B, and D. Customers and users are not part of the Scrum Team, but they are important stakeholders who provide feedback and input to the Product Owner and the Developers.
References:
The Product Owner is the person who will be held accountable if a product does not achieve its
goals or deliver value. Does this mean that the Product Owner has final say over the Definition
of Done?
(choose the best answer)
Yes, the Product Owner decides the Definition of Done. The Developers may be
consulted.
No, the Scrum Team decides the Definition of Done, if it is not a standard of the
organization. The Product Owner is just one member of the Scrum Team.
The Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that "The Developers are required to conform to the Definition of Done, as defined by the Scrum Team. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done."1 This means that the Product Owner does not have the final say over the Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.
References:
True or False: The Product Owner makes sure the Developers select enough from the Product
Backlog for a Sprint to satisfy the stakeholders.
True
False
The Product Owner does not make sure the Developers select enough from the Product Backlog for a Sprint. The Product Owner is responsible for maximizing the value of the product and the work of the Developers, but the Developers are self-managing and decide how much work they can do in a Sprint1. The Product Owner and the Developers collaborate on the scope of the Sprint during Sprint Planning, but the final decision is up to the Developers2. The Product Owner should not interfere with the Developers’ work during the Sprint, but should provide feedback and guidance on the product value[3][3].
References:
1:Â The Scrum Guide, November 2020, p. 6
2:Â The Scrum Guide, November 2020, p. 10
[3][3]:Â Professional Scrum Product Owner I Certification, Scrum.org, accessed on December 16, 2023
Which of the following are true about the Product Owner?
(choose the best two answers)
The Product Owner is one person.
The Scrum Team can have multiple Product Owners.
The Product Owner can be represented by a committee or a team of people.
The Product Owner is accountable for ordering the Product Backlog.
References:
Which of these may a Scrum Team deliver at the end of a Sprint?
(choose the best answer)
Failing unit tests, to identify acceptance tests for the next Sprint.
A single document, if that is what management asked for.
An Increment of software with minor known bugs in it.
A valuable, useful Increment that meets the Definition of Done.
The Scrum Guide states that “the Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprintsâ€. It also states that “at the end of a Sprint, the new Increment must be ‘Done’, which means it must be in useable condition and meet the Scrum Team’s definition of ‘Done’â€. Therefore, the Scrum Team must deliver a valuable, useful Increment that meets the Definition of Done at the end of a Sprint. The other options are not acceptable, as they do not meet the criteria of being valuable, useful, or done.
References:
The Product Owner is the person who will be held accountable if a product does not achieve its goals or deliver value. Does this mean that the Product Owner has the final say over the Definition of Done?
(choose the best answer)
Yes, the Product Owner decides the Definition of Done. The Developers may be
consulted.
No, the Scrum Team decides the Definition of Done, if it is not a standard of the organization. The Product Owner is just one member of the Scrum Team.
References:
Which of the following is required by Scrum?
(choose the best answer)
Sprint Retrospective.
Developers must stand up at the Daily Scrum.
Sprint Burndown Chart.
Release Planning.
All of the above.
The Sprint Retrospective is one of the five events defined by Scrum. It is a formal opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The purpose of the Sprint Retrospective is to adapt the way of working so that it becomes more effective and enjoyable. The other options are not required by Scrum, but may be useful practices depending on the context. Developers do not have to stand up at the Daily Scrum, they can choose any format that works for them. A Sprint Burndown Chart is a common way to visualize the remaining work in a Sprint, but it is not mandated by Scrum. Release Planning is a topic that falls under the broader competency of Managing Products with Agility, but it is not a prescribed event in Scrum.
References:
One of the Scrum events is the Daily Scrum. What are two intended outcomes of the Daily
Scrum?
(choose the best two answers)
An update of completed tasks and of the remaining work so the Scrum Master
can plan the next day.
An updated Scrum board to make Sprint progress transparent for the
stakeholders.
A status report for the upper management indicating what each individual has
done, will be doing, and what is impeding him/her.
Identification of impediments that may prevent the Developers from achieving
the Sprint Goal.
A shared understanding of the most important work to be undertaken next to
achieve the best possible progress toward the Sprint goal.
The Daily Scrum is a 15-minute event for the Developers to synchronize activities and create a plan for the next 24 hours. This meeting is designed to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary. The intended outcomes are to identify any impediments that may prevent the Developers from achieving the Sprint Goal (D) and to foster a shared understanding among the Developers of what work is most important to undertake next in order to make the best possible progress toward the Sprint Goal (E). It is not a status update meeting for the Scrum Master or upper management, nor is it primarily about updating Scrum boards for stakeholder transparency.
References: The Scrum Guide and the resources provided by Scrum.org on the Daily Scrum emphasize these outcomes as essential to the effectiveness of the Daily Scrum event12.
How is management that is external to the Scrum Team involved in the Daily Scrum?
(choose the best answer)
The Product Owner represents their opinions.
The Scrum Master speaks on their behalf.
Managers are not required at the Daily Scrum.
Management gives an update at the start of each Daily Scrum.
 Management that is external to the Scrum Team is not involved in the Daily Scrum because:
References:
Which of the following are the Developers accountable for?
(choose the best two answers)
Organizing the work required to meet the Sprint Goal.
Selecting the Product Owner.
Reporting productivity.
Creating a plan for the Sprint, the Sprint Backlog.
The Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. The Developers are accountable for organizing and managing their work. Only the Developers can decide how to perform the work during the Sprint1. The Developers plan the work necessary to create an Increment that meets the Definition of Done during the Sprint Planning event. 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. The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal1. The Developers are responsible for creating and maintaining the Sprint Backlog1. The Developers are not accountable for selecting the Product Owner, reporting productivity, or any other activities that are not related to creating a Done Increment that meets the Sprint Goal123. References:
True or False: During the Sprint Review the stakeholder's role is to reorder the Product Backlog.
True
False
During the Sprint Review, the stakeholder’s role is not to reorder the Product Backlog, but rather to provide feedback and suggestions on the product and the process. Therefore, the answer is false because:
References:
What might indicate to a Product Owner that she needs to work more with the Scrum Team?
(choose the best answer)
The acceptance criteria do not appear to be complete.
She is not working full time with the Scrum team.
People leave the Scrum Team.
The Increment presented at the Sprint Review does not reflect what she thought she had asked for.
References:
What is the purpose of a Sprint Review?
(choose the best answer)
To build team spirit.
To take time to judge the validity of the project.
To inspect the product Increment with the stakeholders and collect feedback on next steps.
To review the Scrum Team's activities and processes during the Sprint.
References:
Who is responsible for the sizing of Product Backlog items?
(choose the best answer)
The Product Owner with input from the Developers.
The Scrum Master.
The Developers, alone.
The Developers after clarifying requirements with the Product Owner.
The most senior people in the organization, including architects and subject matter
experts.
According to Scrum.org, the Developers who will be doing the work are responsible for the sizing of Product Backlog items1. The Product Owner may influence the Developers by helping them understand and select trade-offs1. This implies that the Developers size the items after clarifying requirements with the Product Owner1.
Your management has asked you to take the lead in the development of a new product. Six teams new to Scrum will build this product.
You have gathered a number of requirements and ideas into an early form of a Product Backlog. How would you minimize dependencies between the Scrum Teams?
(choose the best answer)
You create an independent Product Backlog per Scrum Team.
You divide Product Backlog items among the six Product Owners.
You identify the dependencies and re-order the Product Backlog for the other five
Product Owners.
You work with the Developers on how to best analyze and break apart the work.
You raise this as an impediment with the Scrum Master.
 The best way to minimize dependencies between the Scrum Teams is to work with the Developers on how to best analyze and break apart the work. This is because:
Other options, such as creating an independent Product Backlog per Scrum Team, dividing Product Backlog items among six Product Owners, identifying the dependencies and re-ordering the Product Backlog for the other five Product Owners, or raising this as an impediment with the Scrum Master, are not valid answers as they do not reflect how to minimize dependencies between the Scrum Teams or how to apply the Scrum values and principles.
References:
Which best describes the Product Backlog?
(choose the best answer)
It is allowed to grow and change as more is learned about the product and its
customers.
It contains all foreseeable tasks and requirements from which the Scrum Team can
develop and maintain a complete project plan.
It provides just enough information to enable a Scrum Team to start the design phase
of a product.
It is baselined to follow change management processes.
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. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. The other options are not accurate descriptions of the Product Backlog, as it does not contain all foreseeable tasks and requirements, it does not provide just enough information to start the design phase, and it is not baselined to follow change management processes23.
1: What is a Product Backlog? | Scrum.org 2: What is a Product Backlog? | Agile Alliance 3: Product Backlog: Definition, Examples & Techniques | Wrike Guide
How much work is required of the Developers to complete a Product Backlog item selected during the Sprint Planning?
(choose the best answer)
As much as they can fit into the Sprint, with remaining work deferred to the next Sprint.
As much as is required to meet the Scrum Team's Definition of Done.
All development work and at least some testing.
A proportional amount of time on analysis, design, development, and testing.
References:
What is a Product Owner typically responsible for during a Sprint?
(choose the best two answers)
Attending every Daily Scrum to answer questions about the Sprint Backlog
items.
Creating financial reporting upon the spent hours reported by the Developers.
Nothing.
Updating the work plan for the Developers on a daily basis.
Collaborating with stakeholders, users, and customers.
Working with the Scrum Team on Product Backlog refinement.
The Product Owner is typically responsible for collaborating with stakeholders, users, and customers to understand their needs and expectations, and to validate the value of the product. The Product Owner is also responsible for working with the Scrum Team on Product Backlog refinement, which is the act of adding detail, estimates, and order to Product Backlog items.1 These two responsibilities help the Product Owner to maximize the value of the product and the work of the Developers.
References:
A Product Backlog is:
(choose the best three answers)
An exhaustive list of upfront approved requirements to be implemented.
Managed by the Product Owner.
An inventory of things to be done for the Product.
Ordered based on priority, value, dependencies, and risk.
Only visible to the Product Owner and stakeholders.
A Product Backlog is:
Other options, such as an exhaustive list of upfront approved requirements to be implemented or only visible to the Product Owner and stakeholders, are not valid descriptions of a Product Backlog. They may reflect a misunderstanding of what a Product Backlog is or how Scrum works.
References:
Which statement best describes the Sprint Review?
(choose the best answer)
It is a mechanism to control the Developers activities during a Sprint.
It is used to congratulate the Developers if they complete their forecast or to punish
the Developers if they fail to meet their forecast.
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.
A sprint review is a collaborative event where the Scrum Team and stakeholders inspect the outcome of a Sprint and determine future adaptations12. It is not a mechanism to control, reward, or punish the Developers, nor is it just a demo of the work done.
Why is the Daily Scrum held at the same time and same place?
(choose the best answer)
The Product Owner demands it.
Rooms are hard to book and must be booked in advance.
The place can be named.
The consistency reduces complexity.
The Daily Scrum is held at the same time and same place because:
References:
True or False: Multiple Scrum Teams working on the same product or system all select work
from the same Product Backlog.
True
False
Who starts the Daily Scrum?
(choose the best answer)
The Scrum Master. This ensures that the Developers have the event, and it stays
within the timebox.
The person coming in last. This encourages people to be on time and helps to stay
within the timebox.
The Product Owner.
Whoever the Developers decide should start.
The person who has the token.
The Daily Scrum is an event for and by the Developers. They can choose whatever structure and technique they want, as long as they focus on the progress toward the Sprint Goal and produce an actionable plan for the next day of work12. The Scrum Master, the Product Owner, and the person coming in last are not necessarily the ones who should start the Daily Scrum. The person who has the token is a possible technique, but not the only one3.
When Developers are having trouble delivering an Increment because they do not understand a
functional requirement, what should they do?
(choose the best answer)
Partially complete the functionality, and discuss the remaining work at the Sprint
Review.
Add a specialist to the Development Team.
Collaborate with the Product Owner to determine what is possible and acceptable.
Defer the work to a more appropriate Sprint.
In Scrum, when Developers encounter difficulties in delivering an Increment due to a lack of understanding of a functional requirement, they should collaborate with the Product Owner. This collaboration is crucial as the Product Owner has the responsibility to clarify the items in the Product Backlog and to ensure that the Development Team understands the work to be done. The Product Owner is accountable for maximizing the value of the product and must work with the Development Team to find out what is feasible and acceptable for the Increment being developed. This approach aligns with the Scrum principle of collaboration and self-organization within the Scrum Team.
References: The Scrum Guide and the Professional Scrum Product Ownerâ„¢ (PSPO I) materials emphasize the importance of collaboration between the Product Owner and the Development Team to ensure a clear understanding of the Product Backlog items and to optimize the value of the work being done
During a Sprint Retrospective, the Developers propose moving the Daily Scrum to only occur
on Tuesdays and Thursdays. Which two are the most appropriate responses for the Scrum
Master to recommend?
(choose the best two answers)
Have the Developers vote.
Acknowledge and support the self-managing team's decision.
Coach the team on why the Daily Scrum is important as an opportunity to update
the plan.
Consider the request and decide on which days the Daily Scrum should occur.
Learn why the Developers want this and work with them to improve the outcome
of the Daily Scrum.
The Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices1. The Scrum Master also facilitates Scrum events as requested or needed2. The Daily Scrum is a 15-minute event for the Developers to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments4. The Scrum Master should coach the team on the purpose and value of the Daily Scrum, and help them find ways to make it more effective and enjoyable. The Scrum Master should also learn why the Developers want to reduce the frequency of the Daily Scrum, and work with them to address any underlying issues or concerns. The Scrum Master should not impose a decision on the team, nor delegate the decision to a vote, as these actions would undermine the self-management and empowerment of the Developers5.
References:
True or False: A Scrum Master fulfills the same role as a traditional Project Manager.
True
False
A Scrum Master does not fulfill the same role as a traditional Project Manager. A Project Manager is typically responsible for planning, executing, monitoring, controlling, and closing a project, as well as managing the scope, schedule, budget, quality, risks, and stakeholders of the project1. A Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices, and removes impediments to the team’s progress2. A Scrum Master does not manage the project, the scope, the schedule, the budget, or the team, as these are either shared responsibilities or emergent outcomes of the Scrum framework[3][3]. A Scrum Master also does not have authority over the team or the stakeholders, but rather facilitates collaboration and empowerment among them4.
References:
1:Â What is Project Management?, Project Management Institute, accessed on December 16, 2023
2:Â The Scrum Guide, November 2020, p. 7
[3][3]:Â Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
4:Â Developing People and Teams, Scrum.org, accessed on December 16, 2023
A Project Manager working with your Scrum Team has raised concerns about progress and money spent. What are the two best responses?
(choose the best two answers)
Promote transparency by sharing the Product Backlog and ensuring the Project
Manager has access.
Have a discussion with the Project Manager; share the current impediments and
forecast for the Sprint.
Show the Earned Value Analysis (EVA) report.
Scrum does not have Project Managers so disregard their concerns.
Share the last stakeholder briefing document prepared by the Product Owner.
The two best responses to a Project Manager who has raised concerns about progress and money spent are:
Other options, such as showing the Earned Value Analysis (EVA) report, Scrum does not have Project Managers so disregard their concerns, or sharing the last stakeholder briefing document prepared by the Product Owner, are not the best responses as they do not reflect how to effectively collaborate and communicate with the Project Manager or how to apply the Scrum values and principles.
References:
What is the timebox for the Sprint Review?
(choose the best answer)
2 hours for a one-month Sprint.
1 day.
4 hours for a one-month Sprint.
As long as needed.
 The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:
Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.
References:
In the middle of the Sprint, the customer decides that there are two new features she wants.
The Product Owner could:
(choose the best two answers)
Introduce these features at the next Daily Scrum.
Ask the Developers to consider whether they can add these features to the
current Sprint without endangering the Sprint Goal.
Add these features to the Product Backlog.
Have the Scrum Master add these features to the current Sprint.
References:
How much time must a Product Owner spend with the Developers?
(choose the best answer)
Enough so that the Product Owner is confident the Increment will meet the intended value.
40%, or more if the stakeholders agree.
As much time as the Developers tell the Product Owner to be present.
100%
 The Product Owner must spend enough time with the Developers so that they are confident the Increment will meet the intended value. This is because:
Other options, such as 40%, as much time as the Developers tell them to be present, or 100%, are not valid answers as they imply a fixed or arbitrary amount of time that does not reflect the actual needs and dynamics of the product development.
References:
Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done?
(choose the best two answers)
The Product Owner should not concern themselves with meeting the Definition
of Done, it is the Developer's responsibility.
To be able to punish the team when they do not meet their velocity goal for the Sprint.
To forecast the team's productivity over time.
The Definition of Done can affect the product's total cost of ownership.
To have complete transparency into what has been done at the end of each
Sprint.
The Product Owner should care that the Scrum Team adheres to its Definition of Done because:
References:
Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder
just started using the product. The stakeholder is unhappy with the quality of the product. What
are two good options for the Scrum Master?
(choose the best two answers)
Coach the Product Owner on how to talk with the Developers about this
concern.
Wait to bring this up until the Sprint Retrospective.
Explain to the Product Owner that it is up to the Developers to decide on
acceptable quality standards.
Encourage the Product Owner to put quality specifications on the Product
Backlog and express the stakeholder's concern to the Developers.
Bring the concern to the testers to improve how the Product is verified.
If a stakeholder is unhappy with the quality of the product, the Scrum Master can coach the Product Owner on how to effectively communicate this concern to the Developers1. The Scrum Master can also encourage the Product Owner to put quality specifications on the Product Backlog1. This allows the Developers to understand the stakeholder’s expectations and work towards meeting them1. The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality1.