Explanation: Dependencies are relationships between Product Backlog items that affect their order of implementation. For example, a Product Backlog item may depend on another one to be completed first, or it may have a dependency on a third-party system or resource. Dependencies could influence how the Product Owner orders Product Backlog items, as they may introduce risks, constraints, or uncertainties that affect the value delivery. The Product Owner should try to minimize dependencies and order the Product Backlog items in a way that maximizes value and minimizes waste.
References:
* [Professional Scrum Product Owner], chapter 6: “Dependencies are relationships between Product Backlog items that affect their order of implementation.”
* [Managing Dependencies on Agile Projects]: “Dependencies can have a significant impact on the delivery of value.”

separately by the Developers. They are not the Product Owner’s concern.
Explanation:
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.
Reference:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog

According to the Scrum Guide, if a Product Backlog item does not meet the Definition of Done, it should not be included in the Increment for the Sprint1. The item is considered unfinished and therefore cannot be part of the Increment that may be released or presented as ‘Done’. The undone work should be re-estimated and put back on the Product Backlog for the Product Owner to prioritize for future Sprints2. This ensures transparency and maintains the integrity of the Increment’s quality.
The Scrum Guide provides clear guidance on handling undone work and emphasizes the importance of the Definition of Done as a quality standard for the Increment1. The Professional Scrum Product Owner™ (PSPO I) materials also align with this approach, underscoring the Product Owner’s role in managing the Product Backlog and ensuring that only ‘Done’ items are considered for release

The typical size for a Scrum Team is 10 or fewer people, including the Product Owner, the Scrum Master, and the Developers. The Scrum Guide states that ” The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three people decrease interaction and results in smaller productivity gains. Having more than ten people requires too much coordination. Large teams generate too much complexity for an empirical process to be useful. ” 1 This means that the optimal Scrum Team size is between 3 and 10 people, depending on the context and the nature of the work.
1: The Scrum Guide2, page 6
2: The Scrum Guide

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.
References:
* [Scrum Guide], page 14, section “Sprint Planning”
* [Scrum Guide], page 7, section “Developers”
* [Scrum Guide], page 15, section “Sprint Backlog”
* [Scrum Guide], page 14, section “Sprint Planning”

Non-functional requirements are the criteria that define the quality, performance, security, usability, and other aspects of a product1. They are often implicit or assumed, but they are important to make visible and explicit, as they affect the value and satisfaction of the product2. One effective way to make non-functional requirements visible is to add them to the Product Backlog, which is an ordered list of everything that is known to be needed in the product[3][3]. By adding non-functional requirements to the Product Backlog, the Product Owner and the Developers can prioritize, refine, and estimate them, and make them transparent to the stakeholders4. Another effective way to make non-functional requirements visible is to add them to the Definition of Done, which is a shared understanding of what it means for work to be complete, and ensures transparency of the quality of the work done5. By adding non-functional requirements to the Definition of Done, the Developers can ensure that every Product Backlog item and Increment meets the expected quality standards, and that the work is taken care of every Sprint.
Reference:
1: Non-functional requirement, Wikipedia, accessed on December 16, 2023
2: Managing Products with Agility, Scrum.org, accessed on December 16, 2023
[3][3]: The Scrum Guide, November 2020, p. 6
4: The Scrum Guide, November 2020, p. 7
5: The Scrum Guide, November 2020, p. 13
6: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

Explanation
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:
* 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

Explanation
The Product Owner is one person, not a committee or a team of people. 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.
Having multiple Product Owners for one product would create conflicts, overlaps, gaps, and inefficiencies. It would also make it harder to maintain a clear and consistent product vision, strategy, roadmap, and backlog. Therefore, the Scrum Team can not have multiple Product Owners.
The Product Owner is accountable for ordering the Product Backlog. 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. The Product Owner orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions.
References:
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog

Explanation
To say that an event has a timebox means that the event has a fixed duration that cannot be exceeded. The Scrum Guide states that “All events are time-boxed events, such that every event has a maximum duration.
Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.”1 This means that the timebox sets an upper limit for the event, but the event can end sooner if the goal is met.
References:
1: The Scrum Guide2, page 10
2: The Scrum Guide

The Product Owner does not make sure the Developers select enough from the Product Backlog for a Sprint to satisfy the stakeholders. The Developers are the ones who determine how many Product Backlog items they select for a Sprint, based on their capacity and the Sprint Goal1. 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 is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog[3][3]. The Product Owner does not have the authority to tell the Developers how much work they should do, as this would violate the principle of self-management4.
Reference:
1: The Scrum Guide, November 2020, p. 6
2: The Scrum Guide, November 2020, p. 10
[3][3]: The Scrum Guide, November 2020, p. 6
4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

Explanation
* 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.
References:
* Scrum Guide: https://www.scrumguides.org/scrum-guide.html
* Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
* User Stories: https://www.agilealliance.org/glossary/user-stories

The Scrum Master should talk to the IT manager and explain that progress in Scrum comes from inspecting an Increment at the Sprint Review. This is because:
The Scrum Team is self-managing and does not need to report to anyone outside the team1.
The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect the Increment2.
The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value delivery3.
The IT manager can attend the Sprint Review as a stakeholder and provide feedback on the product and the process4.
Reference:
Scrum Guide, page 7, section “The Scrum Team”
Scrum Guide, page 13, section “Sprint Review”
Scrum Guide, page 10, section “Increment”
Scrum Guide, page 14, section “Sprint Review”

Explanation
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.
References:
* Scrum Guide 2020, page 12: “The Daily Scrum is held at the same time and place each day to reduce complexity.”
* Scrum Guide 2020, page 12: “The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.”
* Scrum Guide 2020, page 13: “The Daily Scrum is an internal meeting for the Developers. If others are present, the Scrum Master ensures that they do not disrupt the meeting.”

Explanation
In order to maximize the value of the product, a Product Owner needs awareness of the following:
* Competitive research. The Product Owner should be aware of the competitive landscape and the market trends that affect the product. They should know who are the competitors, what are their strengths and weaknesses, how do they differentiate themselves, and what are their strategies and goals. This can help the Product Owner to identify opportunities, threats, and gaps in the market, and to position the product accordingly.
* Customer feedback. The Product Owner should be aware of the customer needs, preferences, expectations, and satisfaction with the product. They should collect and analyze feedback from various sources, such as surveys, interviews, reviews, analytics, etc. This can help the Product Owner to validate assumptions, test hypotheses, measure outcomes, and discover insights that can inform the product decisions and priorities.
* Product vision. The Product Owner should be aware of the product vision, which is a clear and compelling statement of the desired future state of the product. The product vision describes the purpose, value proposition, target audience, and key features of the product. It also aligns with the organizational vision and mission. This can help the Product Owner to communicate and inspire the stakeholders, to guide and focus the Scrum Team, and to evaluate and adjust the product direction.
* Forecasting & feasibility. The Product Owner should be aware of the forecasting and feasibility of the product. They should estimate and plan the scope, time, cost, quality, and risk of delivering the product.
They should also assess the technical, operational, legal, ethical, and social feasibility of developing and releasing the product. This can help the Product Owner to optimize the value of the work of the Scrum Team, to manage expectations and dependencies, and to handle uncertainties and changes.
References:
* Scrum Guide 2020, page 6: “The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.”
* Scrum Guide 2020, page 11: “The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against.”
* Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog management, which includes … optimizing the value of the work the Scrum Team performs.”