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.
The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment.
The timebox for the Sprint Planning event is proportional to the length of the Sprint. For a one-month Sprint, the timebox is 8 hours. For shorter Sprints, the timebox is usually shorter. The Scrum Team may decide how much time to spend on each topic within the timebox, depending on their needs and preferences.
The timebox for the Sprint Planning event ensures that the Scrum Team does not spend too much or too little time on planning their work for the Sprint. The timebox also ensures that the Scrum Team has enough clarity and alignment on what and how they want to achieve during the Sprint.
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 fiveProduct 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:
The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
The Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.
The Developers are cross-functional, meaning they have all the skills and competencies needed to accomplish the work without depending on others who are not part of the team.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.
The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it.
The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment.
When there are multiple teams working on one product, it is important to minimize dependencies between them to avoid delays, conflicts, or waste. Dependencies may arise due to technical, functional, or organizational factors that affect how the teams can deliver value independently and effectively.
To minimize dependencies, the Product Owner should work with the Developers on how to best analyze and break apart the work into smaller and more manageable pieces that can be delivered by each team without relying on others. This may involve applying techniques such as feature slicing, component splitting, or domain-driven design. The Product Owner should also communicate and coordinate with other Product Owners and stakeholders to align expectations and priorities across teams.
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.
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:
Scrum Guide
What is a Developer?
Who Determines How Work Is Performed During The Sprint?
[What is Sprint Planning?]
Which of the following are appropriate topics for discussion during a Sprint Retrospective?
(choose the best two answers)
Identifying high priority process improvements for the next Sprint.
The order of items in the Product Backlog.
How the team collaborates.
Documenting acceptance criteria for items in the next Sprint.
The Sprint Retrospective is an event for the Scrum Team to inspect how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done1. The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness for the next Sprint2. Therefore, appropriate topics for discussion during a Sprint Retrospective are:
Identifying high priority process improvements for the next Sprint. The Scrum Team should identify the most important things that went well and the potential improvements, and create a plan for implementing some of them in the next Sprint[3][3] . This way, the Scrum Team can continuously improve their performance and deliver more value.
How the team collaborates. The Scrum Team should reflect on how they work together as a self-managing unit, and how they can enhance their skills, tools, and relationships4. This way, the Scrum Team can foster a culture of trust, respect, and collaboration.
The other options are not appropriate topics for discussion during a Sprint Retrospective, as they are either related to the Product Backlog or the Sprint Backlog, which are not the focus of the Sprint Retrospective. The order of items in the Product Backlog is the responsibility of the Product Owner, who manages the Product Backlog based on the value, risk, and dependencies of the items5. The Product Owner may seek input from the Scrum Team or the stakeholders, but the final decision is up to the Product Owner. Documenting acceptance criteria for items in the next Sprint is part of the Product Backlog refinement, which is an ongoing activity throughout the Sprint, not a specific event. The Scrum Team should collaborate on refining the Product Backlog items and adding more details, such as acceptance criteria, as they become more clear and ready for selection in a Sprint Planning.
Who should make sure everyone on the Scrum Team does their tasks for the Sprint?
(choose the best answer)
The Project Manager.
The Product Owner.
The Scrum Master.
The Scrum Team.
All of the above.
The Scrum Team is a self-organizing and cross-functional team that delivers valuable products in an agile way. The Scrum Team consists of one Product Owner, one Scrum Master, and Developers. They are all accountable for creating a valuable, useful, and potentially releasable product Increment each Sprint.
The Scrum Team is responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Scrum Team does not rely on any external authority, manager, or leader to assign or monitor their work. The Scrum Team collaborates and coordinates their work as one unit, without any hand-offs or silos. The Scrum Team also inspects and adapts their work based on empirical evidence and feedback.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. The Scrum Master does this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.
The other options are not valid or relevant answers for who should make sure everyone on the Scrum Team does their tasks for the Sprint. They are either nonexistent or irrelevant roles in Scrum. They are:
The Project Manager: There is no “Project Manager” role in Scrum. Scrum is a framework for developing, delivering, and sustaining complex products, not projects. A project is a temporary endeavor with a fixed scope, time, and cost. A product is a valuable solution that evolves over time to meet customer needs and market conditions. A project manager is a role in traditional project management, a discipline for planning, executing, and controlling projects. A project manager coordinates and controls the activities of the project team and the stakeholders and ensures that the project meets the quality standards and expectations.
The Product Owner: The Product Owner is not responsible for making sure everyone on the Scrum Team does their tasks for the Sprint. The Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner does not assign or monitor tasks to the Developers. The Product Owner collaborates with them to clarify and refine the Product Backlog items and their acceptance criteria.
All of the above: This is not a valid answer because it includes two invalid options: The Project Manager and The Product Owner.
A Scrum Master is working with a Scrum Team that has Developers in different physical
locations. The Developers meet in a variety of meeting rooms and have much to do logistically
(for example: reserve meeting rooms and set up conference calls) before the Daily Scrum.
What action should the Scrum Master take?
(choose the best answer)
Allow the Developers to self-manage and determine for themselves what to do.
Ask the Developers to alternate who is responsible for meeting setup.
Set up the meeting and tell the Scrum Team that is how it will be done.
Inform management and ask them to solve it.
The Scrum Master should allow the Developers to self-manage and determine for themselves what to do because:
It respects the autonomy and empowerment of the Developers. The Developers are accountable for organizing and managing their own work, and they are the best people to decide how to conduct their Daily Scrum. The Scrum Master should not impose or dictate how the meeting should be set up or run, as that would undermine the self-organization and collaboration of the Developers.
It supports the continuous improvement and adaptation of the Developers. The Developers are expected to inspect and adapt their process and practices, and to find ways to overcome any challenges or impediments they face. The Scrum Master should not solve the problems for them, but rather facilitate their problem-solving and learning abilities.
It aligns with the role and responsibilities of the Scrum Master. The Scrum Master is responsible for promoting and supporting Scrum, and for helping everyone understand and enact Scrum theory, values, principles, and practices. The Scrum Master is not a manager or a leader of the Developers, but rather a servant-leader who enables them to work effectively.
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.
The Scrum Guide
Understanding and Applying the Scrum Framework
Professional Scrum Product Owner™ I Certification
What should the Scrum Team do during the first Sprint?
(Choose the best answer)
Make up a plan for the rest of the project.
Define the major product features and a release plan architecture.
Create at least one valuable and useful Increment.
Analyze, describe, and document the requirements for the subsequent Sprints.
The correct answer isC.
The purpose of every Sprint, including the first Sprint, is to create a valuable, useful Increment. Scrum is based on empiricism, meaning teams learn through doing, inspecting results, and adapting. Therefore, the first Sprint should produce something tangible and valuable rather than focusing only on long-term planning or documentation.
Why the other options are incorrect:
A. Make up a plan for the rest of the project— Scrum does not require full up-front planning for the whole project. Plans emerge and adapt over time.
B. Define the major product features and a release plan architecture— this may happen in some organizations, but it is not the main purpose of the first Sprint.
D. Analyze, describe, and document the requirements for the subsequent Sprints— Scrum is not a phase-based requirements process. The goal is to deliver value each Sprint.
True or False: A Product Owner with multiple teams working on one product should maintain separate Product Backlogs for each team.
True
False
In Scrum, there is only one product and one Product Backlog for a given product. The Product Backlog is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product. The Product Backlog is ordered by the Product Owner based on the product vision, goals, and value.
Having multiple Product Backlogs for one product would create confusion, duplication, inconsistency, and waste. It would also make it harder to align the Scrum Teams and the stakeholders on the same product direction and priorities. Therefore, a Product Owner with multiple teams working on one product should not maintain separate Product Backlogs for each team.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
In some cases, when there are multiple Scrum Teams working on one product, it may be necessary to have some form of scaling or coordination mechanism to ensure alignment and collaboration among the teams. However, this does not mean that there should be multiple Product Owners or Product Backlogs. Instead, there should be ways to facilitate communication, feedback, integration, and transparency among the teams and with the Product Owner. For example, some frameworks or practices that can help with scaling Scrum are Nexus, LeSS, SAFe, or Scrum of Scrums.
Who determines how many Product Backlog items the Developers select for a Sprint?
(choose the best answer)
The Scrum Team
The Developers.
The Product Owner.
The Scrum Master.
The stakeholders attending Sprint Planning.
The Developers are the ones who determine how many Product Backlog items they select for a Sprint. 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, the Scrum Master, and the stakeholders do not have the authority to tell the Developers how many Product Backlog items they should select, as this would violate the principle of self-management[3][3] .
Who creates the Definition of Done?
(choose the best answer)
The Scrum Master
The Scrum Team
The Product Owner
The Developers
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 Definition of Done is created by the Scrum Team, not just the Developers. The Scrum Team must have a shared understanding of what it means for work to be complete, to ensure transparency. The Definition of Done is used to assess when work is complete on the product Increment. The Definition of Done may vary significantly per Scrum Team, depending on the context. The Definition of Done evolves over time and is updated whenever the Scrum Team learns more about the product and the environment in which it operates.
The Scrum Guide
Understanding and Applying the Scrum Framework
Professional Scrum Product Owner™ I Certification
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:
Managed by the Product Owner. The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it.
An inventory of things to be done for the Product. The Product Backlog contains all the features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases. The Product Backlog items have a description, an order, an estimate, and a value.
Ordered based on priority, value, dependencies, and risk. The Product Owner orders the Product Backlog items based on various factors that affect their importance and urgency for the product. These may include customer needs, business value, stakeholder feedback, technical dependencies, or market opportunities.
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.
What activities would a Product Owner typically undertake in the period between the end of the
current Sprint and the start of the next Sprint?
(choose the best answer)
There are no such activities. The next Sprint starts immediately after the currentSprint.
Refine the Product Backlog.
Update the project plan with stakeholders.
Work with the Quality Assurance departments on the Increment of the current Sprint.
the Product Owner is responsible for refining the Product Backlog, which is an ongoing activity that can occur at any time, including between Sprints.The other options are not typical activities for the Product Owner between Sprints, as the next Sprint starts immediately after the current Sprint1, the project plan is replaced by the Product Backlog2, and the Quality Assurance is done by the Developers of the Scrum Team within the Sprint1.
1:The Scrum Guide | Scrum.org2:What is a Product Backlog? | Scrum.org
When can Developers cancel a Sprint?
(choose the best answer)
When functional expectations are not well understood.
When the selected Product Backlog items for the Sprint become unachievable.
They cannot. Only Product Owners can cancel Sprints.
When the Product Owner is absent too often.
When a technical dependency cannot be resolved.
According to the Scrum Guide, a Sprint can be canceled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be canceled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be canceled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense. Developers cannot cancel a Sprint on their own, even if they face challenges or difficulties with the selected Product Backlog items, the functional expectations, the technical dependencies, or the Product Owner’s availability. Instead, they should collaborate with the Product Owner and the Scrum Master to find the best way to deliver value within the Sprint and adapt to the changing situation.
The Scrum Guide
Understanding and Applying the Scrum Framework
Professional Scrum Product Owner™ I Certification
How much of the Sprint Backlog must be defined during the Sprint Planning event?
(choose the best answer)
Just enough to understand design and architectural implications.
Enough so the Developers can create their forecast of what work they can do.
The entire Sprint Backlog must be identified and estimated by the end of Sprint Planning.
Just enough tasks for the Scrum Master to be confident in the Developers ' understanding of the Sprint.
The amount of the Sprint Backlog that must be defined during the Sprint Planning event is enough so the Developers can create their forecast of what work they can do. This is because:
Sprint Planning is an event where the Scrum Team plans for the upcoming Sprint. The purpose of Sprint Planning is to align the entire Scrum Team around a common goal and a plan for delivering an Increment that meets that goal.
The Developers are accountable for creating a Sprint forecast, which is a selection of Product Backlog items that they intend to work on during the Sprint. The Sprint forecast should be realistic, achievable, and valuable.
The Developers are also accountable for creating a plan for how they will deliver the selected Product Backlog items as a “Done” Increment. The plan may include tasks, dependencies, risks, estimates, or other information that helps them organize and manage their work.
The amount of the Sprint Backlog that must be defined during Sprint Planning may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that the Developers can create their forecast of what work they can do and have a clear direction for the first few days of the Sprint.
Other options, such as just enough to understand design and architectural implications, the entire Sprint Backlog being identified and estimated by the end of Sprint Planning, or just enough tasks for the Scrum Master to be confident in the Developers’ understanding of the Sprint, are not valid answers as they do not reflect what must be defined during Sprint Planning or what is required for creating a Sprint forecast.
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
1: The Scrum Guide2, page 7
2: The Scrum Guide
True or False: Multiple Scrum Teams working on the same product or system all select work
from the same Product Backlog.
True
False
Five new Scrum Teams have been created to build one product. A few of the Developers on one of the Scrum Teams ask the Scrum Master how to coordinate their work with the other teams. What should the Scrum Master do?
(choose the best answer)
Teach them that it is their responsibility to work with the other teams to create anintegrated Increment that is inclusive of all five team ' s work.
Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.
Visit the five teams each day to inspect that their Sprint Backlogs are aligned.
Teach the Product Owner to work with the lead developers on ordering ProductBacklog in a way to avoid too much overlap during a Sprint.
Correct Answer: A. Teach them that it is their responsibility to work with the other teams to create an integrated Increment that is inclusive of all five team’s work.
According to the Scrum Guide, the Scrum Team is responsible for all product-related activities, including coordination and integration with other teams. The Scrum Master should teach the Developers how to work with the other teams to create a potentially releasable product increment that meets the Definition of Done and the Product Goal. One way to facilitate this coordination is to use a Scrum of Scrums meeting, which is a daily or periodic meeting where representatives from each team share their progress, plans, and impediments. The Scrum of Scrums meeting is not mandatory, but it can help the teams align their work and resolve dependencies.
The other options are not correct because they violate the principles of Scrum, such as self-management, empiricism, and transparency:
B. Collecting the Sprint tasks from the teams and merging them into a consolidated plan for the entire Sprint is a centralized and controlled way of coordination that undermines the self-management and autonomy of the teams. The Scrum Master should not act as a project manager or a coordinator, but as a servant-leader and a coach who enables the teams to manage their own work.
C. Visiting the five teams each day to inspect that their Sprint Backlogs are aligned is a micromanagement and inspection approach that does not respect the trust and transparency of the teams. The Scrum Master should not interfere with the work of the teams, but support them in creating a shared understanding of the product vision, goals, and requirements.
D. Teaching the Product Owner to work with the lead developers on ordering Product Backlog in a way to avoid too much overlap during a Sprint is a suboptimal and inefficient way of coordination that does not leverage the collective intelligence and creativity of the teams. The Product Owner should not rely on a few individuals to order the Product Backlog, but collaborate with all the teams and stakeholders to maximize value delivery.
[Scrum Guide], section 2.2: “The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required.”
Scrum Of Scrums - Guide to Agile Scaling Frameworks - Agilest®: “The coordination of the various teams is done in a Scrum of Scrums meeting which can be held daily, twice a week, or at a minimum, once a week. Each Scrum team has its ScrumMaster or a designated team member attend the Scrum of Scrum meeting as its representative.”
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.
One of the possible indicators that a Product Owner needs to work more with the Scrum Team is when the Increment presented at the Sprint Review does not reflect what she thought she had asked for. This means that there is a gap or a misunderstanding between the Product Owner and the Developers regarding the Product Backlog items, the acceptance criteria, the Definition of Done, or the product vision and goals.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets her expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders.
If the Increment presented at the Sprint Review does not reflect what the Product Owner thought she had asked for, it may indicate that there was insufficient or ineffective communication, collaboration, or alignment between the Product Owner and the Developers during the Sprint. This may result in wasted effort, rework, delays, or dissatisfaction for both parties. To avoid or resolve this situation, the Product Owner needs to work more with the Scrum Team by doing some of the following actions:
Engage in frequent and regular interactions with the Developers throughout the Sprint to clarify, refine, and review the Product Backlog items and their acceptance criteria.
Provide clear and concise descriptions of what is needed and why it is valuable for each Product Backlog item.
Involve key stakeholders in defining and prioritizing the Product Backlog items and their acceptance criteria.
Empower and trust the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards.
Solicit and incorporate feedback from the Developers on how to improve or simplify the Product Backlog items or their acceptance criteria.
Inspect and adapt based on empirical evidence from testing, data, or customer feedback.
True or False: Product Owners must specify complete acceptance criteria for a Product
Backlog item before the Developers can select the item in Sprint Planning.
True
False
Answer: False
Very Short Explanation: According to Scrum.org, the Product Owner is not required to create clear and unambiguous acceptance criteria for each item in the product’s backlog before it can be selected in Sprint Planning1.Acceptance Criteria is optional and is not prescribed by Scrum12.It can be valuable, but it’s not a must12.The Developers can inspect and adapt the Sprint Backlog in any way they see fit, in order to help meet the Sprint Goal2.
Which three of the following are true about Scrum?
(choose the best three answers)
Scrum implements self-management by replacing Project Managers with ScrumMasters.
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 Scrumyou think will work for your environment.
Each component of Scrum serves a specific purpose and is essential to Scrum ' ssuccess and your usage of Scrum to develop complex products.
The following are true about Scrum:
Scrum is based on empiricism and lean thinking. Empiricism is the principle of making decisions based on what is observed and experienced, rather than on theory or speculation. Lean thinking is the philosophy of eliminating waste and maximizing value in any process or system. Scrum applies these concepts by providing a framework for inspecting and adapting the product and the process, and by focusing on delivering the most valuable features to the customers and stakeholders.
Scrum is a framework for developing and sustaining complex products. A complex product is one that has unpredictable or unknown aspects that require creativity, experimentation, and adaptation to deliver. A framework is a set of minimal and essential rules and roles that provide structure and guidance, but leave room for flexibility and innovation. Scrum provides such a framework for teams to collaborate and deliver complex products iteratively and incrementally, while embracing change and feedback.
Each component of Scrum serves a specific purpose and is essential to Scrum’s success and your usage of Scrum to develop complex products. Scrum consists of three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). Each of these components has a clear definition, accountability, and goal that contributes to the overall effectiveness and value of Scrum. Removing or changing any of these components may cause the benefits of Scrum to be lost or diminished.
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 updatethe 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 outcomeof 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.
1: The Scrum Guide, November 2020, p. 7
2: The Scrum Guide, November 2020, p. 11
[3][3] : The Scrum Guide, November 2020, p. 10
4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023
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 beconsulted.
No, the Scrum Team decides the Definition of Done, if it is not a standard of theorganization. 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.
1: The Scrum Guide2, page 14
2: The Scrum Guide
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.
Who has the final decision about the order of items in the Product Backlog?
(choose the best answer)
The Scrum Master.
The Stakeholders.
The Scrum Team.
The Developers.
The Product Owner.
In Scrum, the Product Owner is responsible for maximizing the value of the product resulting from the work of the Development Team. One of the primary ways the Product Owner does this is by managing the Product Backlog, which includes clearly expressing Product Backlog items, ordering the items to best achieve goals and missions, and ensuring that the Product Backlog is visible, transparent, and clear to all. This means that the Product Owner has the final authority on the order of items in the Product Backlog, as they are best positioned to understand the strategic and market value of the work to be done.
The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) study materials, specifically the sections on ‘Managing Products with Agility’ and ‘Understanding and Applying the Scrum Framework’, which outline the accountabilities of the Product Owner in managing the Product Backlog
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 ProjectManager has access.
Have a discussion with the Project Manager; share the current impediments andforecast 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:
Promote transparency by sharing the Product Backlog and ensuring the Project Manager has access. This helps communicate what is needed to improve the product, what is planned for each Sprint, and what has been done so far. It also helps align expectations and priorities among different stakeholders.
Have a discussion with the Project Manager; share the current impediments and forecast for the Sprint. This helps address any issues or risks that may affect the delivery of value and the achievement of the Sprint Goal. It also helps provide feedback and adaptation based on the empirical evidence and data.
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.
True or False: The value delivered by a product can only be determined by revenue.
True
False
The value delivered by a product can not be determined by revenue alone, because:
Revenue is only one aspect of value, and it may not reflect the true impact or benefit of the product for the stakeholders, the users, and the society. For example, a product may generate high revenue, but also cause environmental damage, ethical issues, or customer dissatisfaction.
Value is a subjective and relative concept, and it may vary depending on the context, the perspective, and the criteria of the evaluation. For example, a product may have different value for different segments of customers, or for different markets or regions.
Value is dynamic and emergent, and it may change over time due to various factors, such as feedback, competition, innovation, or regulation. For example, a product may lose its value as new alternatives or solutions become available, or as customer needs or preferences evolve.
When is the Sprint Backlog created?
(choose the best answer)
Prior to Sprint Planning.
During refinement.
During the Sprint Retrospective.
During Sprint Planning.
The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that " 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). " 1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.
1: The Scrum Guide2, page 15
2: The Scrum Guide
The Scrum Team should have all the skills needed to:
(choose the best answer)
Complete the project within the date and cost as calculated by the Product Owner.
Do all of the development work, except for specialized testing that requires additionaltools and environments.
Turn Product Backlog items into a valuable, useful Increment.
The Scrum Team should have all the skills needed to turn Product Backlog items into a valuable, useful Increment, as this is the primary goal of each Sprint. The Scrum Guide states that " 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. " 1 The Scrum Team should be cross-functional, which means that the Developers have all the skills necessary to create a product Increment.1 The Scrum Team should also be self-managing, which means that they decide how best to accomplish their work, rather than being directed by others outside the Scrum Team.1
1: The Scrum Guide2, page 6
2: The Scrum Guide
Which statement best describes the Sprint Backlog as the output of the Sprint Planning?
(choose the best answer)
It is a complete list of all work to be done in a Sprint.
Every item has a designated owner.
Each task is estimated in hours.
It is the Developers plan for the Sprint.
It is ordered by the Product Owner.
The Sprint Backlog is the output of the Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that " 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). " 1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned. The Sprint Backlog makes visible all the work that the Developers identify as necessary to meet the Sprint Goal.1
1: The Scrum Guide2, page 15
2: The Scrum Guide
What are two effective ways for a Scrum Team to ensure security concerns are satisfied? (choose the best two answers)
Add security concerns to the Definition of Done.
Delegate the work to the security department.
Have the Scrum Team create Product Backlog items for each concern.
Add a Sprint to specifically resolve all security concerns.
Postpone the work until a specialist can perform a security audit and create a list of security-related Product Backlog items.
These are the best answers because they ensure that security concerns are addressed in a transparent and consistent way. By adding security criteria to the Definition of Done, the Scrum Team can make sure that every Increment meets a high standard of quality and security. By creating Product Backlog items for specific security concerns, the Scrum Team can prioritize and plan them in collaboration with the Product Owner and stakeholders. References:
Scrum Guide, page 14: “The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.”
Scrum Guide, page 15: “The Product Backlog is an emergent, ordered list of what is needed to improve the product.”
If Product Backlog refinement is needed, when is the ideal time for refinement to take place and
who should participate?
(choose the best two answers)
The Scrum Team during the current Sprint, if they have been unable duringpreceding Sprints to define Product Backlog items with enough precision tobegin work.
Business analysts in the organization should do this work for the Scrum Team 1- 2 Sprints ahead of the development Sprints.
The Product Owner must do this as essential work in Sprint O.
The Product Owner takes the time between the end of one Sprint and the startof the next Sprint to complete refinement.
The Scrum Team on an ongoing basis, defining Product Backlog items intosmaller more precise items that are ready for selection.
The ideal time for refinement to take place and who should participate are the Scrum Team during the current Sprint, if they have been unable during preceding Sprints to define Product Backlog items with enough precision to begin work, and the Scrum Team on an ongoing basis, defining Product Backlog items into smaller more precise items that are ready for selection. This is because:
Product Backlog refinement is the act of adding detail, estimates, and order to Product Backlog items. It is an ongoing and collaborative process that involves the whole Scrum Team.
The Scrum Team should refine the Product Backlog as needed to ensure that there are enough items that are sufficiently clear and ready for selection in Sprint Planning. The amount of time spent on refinement usually varies from one Scrum Team to another, but it is recommended not to exceed 10% of the capacity of the Developers.
The Scrum Team may also use a Sprint to refine the Product Backlog if they have not been able to do so in previous Sprints. This may happen when the product is new or complex, or when there is a significant change in the product vision or direction. However, this should be an exception rather than a rule, as it may delay the delivery of value and feedback.
Other options, such as business analysts doing the refinement work for the Scrum Team, the Product Owner doing the refinement alone in Sprint 0 or between Sprints, or handing off the ownership of the Product Backlog to someone else, are not consistent with the principles and values of Scrum. They may lead to misunderstandings, misalignment, or loss of ownership and accountability.
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:
The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.
The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment.
The amount of time that the Product Owner must spend with the Developers may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that both parties are confident that the Increment will meet the intended value.
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.
Who is accountable for clearly expressing Product Backlog items?
(Choose the best answer)
The Product Owner.
The business analyst who represents the Product Owner.
The Scrum Master.
The Scrum Master, or the Scrum Master may have the Developers do it.
The correct answer isA.
According to the Scrum Guide, the Product Owner is accountable for effective Product Backlog management, including creating and clearly communicating Product Backlog items. This accountability belongs to the Product Owner alone, even though others may help with refinement or clarification.
Why the other options are incorrect:
B. The business analyst who represents the Product Owner— Scrum does not define this as an accountability. Support may exist, but accountability remains with the Product Owner.
C. The Scrum Master— the Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and helping team and organization effectiveness, not for expressing Product Backlog items.
D. The Scrum Master, or the Scrum Master may have the Developers do it— accountability cannot be delegated this way.
Who is accountable for creating a valuable and usable Increment each Sprint?
(choose the best answer)
The Scrum Master.
The CEO.
The Developers.
The Scrum Team.
The Product Owner.
The Developers are accountable for creating a valuable and usable Increment each Sprint. They are the people in the Scrum Team who 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.
The Scrum Guide
The Developers
Understanding and Applying the Scrum Framework
A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for the Product Backlog. However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog
should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?
• Stability requirements
• Performance requirements
• Product Functionality
• Documentation
• Fixes
(choose the best answer)
Yes, they all belong on the Product Backlog. The Product Backlog is supposed to be the " single source of truth " for all the work for the product.
No. Product Backlog is a tool for the Product Owner. The Product Owner represents the users and stakeholders. Other types of requirements should be managedseparately by the Developers. They are not the Product Owner ' s concern.
The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
All types of requirements are acceptable on a Product Backlog, as long as they are aligned with the product vision and goals, and they are transparent, clear, and valuable. The Product Backlog can include stability requirements, performance requirements, product functionality, documentation, fixes, or any other aspects that contribute to the quality and usability of the product.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
Which approach is best for Scrum Teams in order to produce valuable Increments?
(choose the best answer)
Each Developer works on the component where they feel that they can contribute.
Each Scrum Team works on an independent set of components.
Each Scrum Team is accountable for developing functionality from beginning to end.
Each Scrum Member works only as an independent layer of the system.
The best approach for Scrum Teams to produce valuable Increments is to be accountable for developing functionality from beginning to end, as this enables them to deliver potentially releasable products that meet the definition of “Done”. 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 This means that the Developers are not limited by the boundaries of components, layers, or technologies, but rather they collaborate and coordinate to deliver a complete and integrated product that satisfies the Sprint Goal and the Product Owner’s expectations.
1: The Scrum Guide2, page 7
2: The Scrum Guide
A new Developer is having continuing conflicts with existing members of the Scrum Team,
which is impacting the delivery of the Increment. If necessary, who is responsible for removing
the Developer from the Scrum Team?
(choose the best answer)
The Product Owner is responsible, they control the return on investment (ROI).
The Scrum Team is responsible.
The Scrum Master is responsible, they remove impediments.
The hiring manager is responsible, they hired the Developer.
The Scrum Team is a self-managing unit that organizes its own work and delivers a valuable product1. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers2. The Scrum Team is accountable for creating a valuable, useful Increment every Sprint[3][3] . If a Developer is having conflicts with other team members that affect the delivery of the Increment, the Scrum Team is responsible for resolving the issue and deciding whether to remove the Developer from the team or not. The Product Owner, the Scrum Master, and the hiring manager do not have the authority to remove a Developer from the Scrum Team, as this would violate the principle of self-management4.
The Daily Scrum is an event that happens every day. What would be three key concerns if the
frequency were to be lowered to every two or three days?
(choose the best three answers)
The Sprint Backlog may become inaccurate.
Too much work is spent updating the Scrum board before the meeting.
The Scrum Master loses the ability to update the Gantt chart properly.
The Product Owner cannot accurately report progress to the stakeholders.
Opportunities to inspect and adapt the Sprint Backlog are lost.
Impediments are raised and resolved more slowly.
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 necessary1. It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments2. If the frequency of the Daily Scrum were to be lowered to every two or three days, three key concerns would be:
The Sprint Backlog may become inaccurate. The Sprint Backlog is the plan for how the Developers will achieve the Sprint Goal, and it is updated throughout the Sprint as more is learned[3][3] . The Daily Scrum is a chance for the Developers to inspect the Sprint Backlog and make adjustments based on the current situation4. If the Daily Scrum is less frequent, the Sprint Backlog may not reflect the reality of the work, and the Developers may lose track of their progress and alignment with the Sprint Goal.
Opportunities to inspect and adapt the Sprint Backlog are lost. Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed5. The Daily Scrum is an essential event for the Developers to apply empiricism to their work, by inspecting the Sprint Backlog and adapting it to optimize the value and quality of the Increment. If the Daily Scrum is less frequent, the Developers may miss opportunities to inspect and adapt their work, and may not be able to deliver a valuable, useful Increment every Sprint.
Impediments are raised and resolved more slowly. An impediment is anything that prevents the Scrum Team from delivering a product Increment. The Daily Scrum is a forum for the Developers to identify and communicate any impediments that affect their work, and to seek help from the Scrum Master or other team members. If the Daily Scrum is less frequent, the impediments may not be raised and resolved in a timely manner, and may cause delays or quality issues in the product delivery.
Why does the Product Owner want the Developers to adhere to its Definition of Done?
(choose the best answer)
To predict the team ' s productivity over time.
To have complete transparency into what has been done at the end of each Sprint.
To know what the team will deliver over the next three Sprints.
To be able to reprimand the team when they do not meet their velocity goal for the Sprint.
The Product Owner wants the Developers to adhere to its Definition of Done to have complete transparency into what has been done at the end of each Sprint. This is because:
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what “Done” means for any Product Backlog item that is selected for a Sprint.
The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.
Having a clear and consistent Definition of Done helps the Product Owner have complete transparency into what has been done at the end of each Sprint. It also helps them make informed decisions about releasing, adapting, or continuing the product development.
Other options, such as predicting the team’s productivity over time, knowing what the team will deliver over the next three Sprints, or reprimanding the team when they do not meet their velocity goal for the Sprint, are not valid reasons for wanting the Developers to adhere to its Definition of Done. They may reflect a misunderstanding of what a Definition of Done is or how Scrum works.
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.
What are the two responsibilities of testers in a Scrum Team?
(choose the best two answers)
Tracking quality metrics.
Scrum has no " tester " role.
Verifying the work of programmers.
The Developers are responsible for quality.
Finding bugs.
Scrum is a framework for developing, delivering, and sustaining complex products. Scrum defines three roles: the Product Owner, the Scrum Master, and the Developers. Scrum does not have any other roles or titles, such as “tester”, “analyst”, “designer”, or “architect”.
The Developers are the people in the Scrum Team who are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
The Developers are responsible for quality, not just for programming. Quality is not something that can be added or verified after the product is built. Quality is something that must be built into the product from the start, by following good practices, standards, and principles. Quality is also something that must be inspected and adapted continuously, by applying feedback loops, testing methods, and improvement actions.
The Developers are not divided into sub-teams or sub-roles based on their skills or specialties. The Developers are a cross-functional and self-organizing team that has all the skills and capabilities needed to create a valuable product Increment. The Developers collaborate and coordinate their work as one unit, without any hand-offs or silos.
The Developers may have different backgrounds or expertise, such as testing, analysis, design, or architecture. However, these are not separate roles or responsibilities in Scrum. They are part of the collective accountability and responsibility of the Developers as a whole. The Developers may perform different tasks or activities based on their skills or preferences, but they are all equally responsible for delivering a high-quality product Increment.
What may be included in the Sprint Backlog?
(choose the best answer)
User Stories.
Tasks.
Use Cases.
Tests.
Any of the above (or others) which are a decomposition of the selected ProductBacklog items.
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 Sprint Backlog is aforecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment1. The Sprint Backlog makes visible all the work that the Developers identify as necessary to meet the Sprint Goal1. The Sprint Backlog can include any items that the Developers deem necessary to achieve the Sprint Goal, such as user stories, tasks, use cases, tests, or others. The SprintBacklog is a plan with enough detail that changes in progress can be understood in the Daily Scrum1.
The Scrum Guide, section 3.3. Sprint Backlog
Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2.The Product Owner and the Sprint
Professional Scrum Product Owner I (PSPO I) Sample Questions, question 11
Why is it important that there is only one Product Owner per product?
(choose the best three answers)
The Scrum Master knows who acts as their backup while on vacation.
It would confuse the stakeholders if they had to work with more than one person.
It is clear who is accountable for the ultimate value of the product.
It helps avoid barriers to effective communication and rapid decision-making.
The Scrum Team always knows who determines the order of the ProductBacklog.
The reasons why it is important that there is only one Product Owner per product are:
It is clear who is accountable for the ultimate value of the product. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.
It helps avoid barriers to effective communication and rapid decision-making. The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must also collaborate with the Developers and the stakeholders to refine, order, and prioritize the Product Backlog items based on value and impact.
The Scrum Team always knows who determines the order of the Product Backlog. The Product Owner has the final authority to decide what items are more important and valuable for the product. They must communicate this order clearly and consistently to the Scrum Team and the stakeholders. They must also respect and support the self-management of the Developers in choosing how best to accomplish their work.
Other options, such as the Scrum Master knowing who acts as their backup while on vacation or it would confuse the stakeholders if they had to work with more than one person, are not valid reasons why it is important that there is only one Product Owner per product. They may reflect a misunderstanding of the roles and accountabilities of the Scrum Team or the stakeholders.
Who determines when it is appropriate to update the Sprint Backlog during a Sprint?
(choose the best answer)
The Project Manager.
The Scrum Team.
The Developers.
The Product Owner.
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 Goal. The Sprint Backlog is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint, and it belongs solely to the Developers.
The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
The Developers are also responsible for updating the Sprint Backlog throughout the Sprint. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Developers work through the plan and learn more about the work needed to achieve the Sprint Goal.
As new work is required, the Developers add it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnecessary, they are removed. Only the Developers can change its content and order during a Sprint.
The job of a Product Owner focuses on the following:
(choose the best two answers)
Working with customers and stakeholders to identify the most valuable productrequirements.
Writing clear, transparent User Stories.
Being with the Scrum Team all the time, just in case they need me to clarify arequirement.
Clearly communicating project or release status and strategies to customers andstakeholders.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
The job of a Product Owner focuses on the following aspects:
Working with customers and stakeholders to identify the most valuable product requirements: The Product Owner engages in frequent and regular interactions with the people who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. The Product Owner solicits and incorporates their input, feedback, and insights to understand their needs and expectations, discover new opportunities or ideas, align and collaborate on the product direction and priorities, and validate and deliver value to them. The Product Owner translates these requirements into Product Backlog items that can deliver value to customers or users.
Clearly communicating project or release status and strategies to customers and stakeholders: The Product Owner communicates effectively and transparently with the customers and stakeholders about the progress, outcomes, and plans of the product development. The Product Owner shares relevant information and data about the product vision, goals, value proposition, roadmap, backlog, increment, feedback, or metrics. The Product Owner also communicates the strategies and decisions for delivering value to customers or users, such as release frequency, scope, quality, or risk management.
The other options are not valid or relevant aspects of a Product Owner’s job. They are either too narrow, unrealistic, or unrelated to the product value delivery. They are:
Writing clear, transparent User Stories: This is not a valid aspect of a Product Owner’s job. User Stories are a common format for expressing product requirements in an agile way. They consist of a brief description of a feature or function from the perspective of a user or customer. They usually follow a template such as “As a < role > , I want < goal > , so that < benefit > ”. However, User Stories are not mandatory or universal in Scrum. The Product Owner can use any format or method to express product requirements, as long as they are clear, concise, and valuable. The format or method does not affect the value or quality of the product or service delivered.
Being with the Scrum Team all the time, just in case they need me to clarify a requirement: This is not a realistic aspect of a Product Owner’s job. The Product Owner does not have to be physically present with the Scrum Team all the time. The Product Owner can work remotely or asynchronously with the Scrum Team, as long as they maintain effective communication and collaboration. The Product Owner should also empower and trust the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards. The Product Owner should also ensure that the Product Backlog items are sufficiently clear and refined before they are selected for a Sprint.
Which of the following are true about the length of the Sprint?
(choose the best answer)
The length of the Sprint should be proportional to the work that is done in betweenSprints.
All Sprints must be one month or less.
Sprint length is determined during Sprint Planning, and should hold the time it willtake to build the planned features in the upcoming Sprint, but does not include timefor any testing.
Sprint length is determined during Sprint Planning, and should be long enough tomake sure the Scrum Team can deliver what is to be accomplished in the upcomingSprint
The Scrum Guide states that “Sprints are the heart of Scrum where ideas are turned into value”. It also states that “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint”. Furthermore, it states that “Sprints are limited to one calendar month. When a Sprint’s horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase”. Therefore, the correct answer is B. The other options are not acceptable, as they contradict the Scrum principles of empiricism, self-organization, and adaptation.
The Scrum Guide, section 3.1. Sprints
Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2.The Product Owner and the Sprint
True or False: Scrum has a role called " Project Manager " .
True
False
Scrum does not have the role of Project Manager. The work is completed by the three roles in the Scrum Team: Product Owner, Development Team, and Scrum Master123. Project Managers can work on any type of project, while Scrum Masters are exclusive to Scrum projects and Scrum teams2.
Who does the work to make sure Product Backlog items conform to the Definition of Done?
(choose the best answer)
The Product Owner.
The Quality Assurance Team.
The Scrum Team.
The Developers.
The Scrum Master.
The work to make sure Product Backlog items conform to the Definition of Done is done by the Developers. This is because:
The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what “Done” means for any Product Backlog item that is selected for a Sprint.
The Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.
Other options, such as the Product Owner, the Quality Assurance Team, the Scrum Team, or the Scrum Master, are not responsible for making sure Product Backlog items conform to the Definition of Done. They may have different roles and accountabilities in Scrum, but they do not do the actual work of creating a “Done” Increment.
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:
The consistency reduces complexity. By having a fixed time and place for the Daily Scrum, the Developers can avoid wasting time and energy on scheduling, logistics, or coordination issues. They can also establish a routine and a rhythm that helps them focus on their work and their Sprint Goal.
The consistency increases transparency. By having a fixed time and place for the Daily Scrum, the Developers can ensure that everyone is aware of when and where the meeting takes place, and that everyone has an opportunity to participate and share their progress, plans, and challenges. They can also invite other stakeholders or observers, if they find it useful, to provide feedback or support.
The consistency enhances collaboration. By having a fixed time and place for the Daily Scrum, the Developers can create a safe and comfortable space for them to communicate, interact, and collaborate with each other. They can also build trust, rapport, and accountability among themselves, and foster a sense of team spirit and ownership.
Copyright © 2021-2026 CertsTopics. All Rights Reserved
