PSPO-I Professional Scrum Product Owner (PSPO I) Exam Questions and Answers

 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.”

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.

A Sprint is a timebox of one month or less within which a “Done” product Increment is created. A Sprint consists of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective. A Sprint is also a feedback loop that allows the Scrum Team and the stakeholders to inspect and adapt the product and the process.

The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint.

In the middle of a Sprint, if a customer decides that there are two new features she wants, there are two possible ways that a Product Owner could handle this situation:

Ask the Developers to consider whether they can add these features to the current Sprint without endangering the Sprint Goal: The Product Owner could discuss with the Developers if they have enough capacity and skills to accommodate these new features in their current Sprint Backlog. The Product Owner could also explain why these features are valuable or urgent for the customer or user. The Developers could then decide if they can or want to add these features to their current work plan, or if they prefer to defer them to a future Sprint. The Developers should not compromise on quality or scope to fit these features in their current Sprint. The Developers should also ensure that these features are aligned with or support the current Sprint Goal.

Add these features to the Product Backlog: The Product Owner could add these new features to the Product Backlog as new items. The Product Owner could then order these items based on their value, risk, priority, dependency, feedback, or market conditions. The Product Owner could also refine these items with more details or acceptance criteria. The Product Owner could then plan to include these items in a future Sprint, depending on their order and availability.

The other options are not valid or relevant ways that a Product Owner could handle this situation. They are either too disruptive, impractical, or irrelevant. They are:

Introduce these features at the next Daily Scrum: This is not a valid way for a Product Owner to handle this situation. The Daily Scrum is an event for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24 hours. The Daily Scrum is not a status meeting or a reporting session for anyone else. The Product Owner may attend the Daily Scrum as an observer or as an invited participant if they have something valuable to contribute or if they need some clarification from the Developers. However, introducing new features at this event would be disruptive and inappropriate for both parties.

Have the Scrum Master add these features to the current Sprint: This is not a valid way for a Product Owner to handle this situation. The Scrum Master is not responsible for adding or removing any work from the current Sprint. 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 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.

The “cone of uncertainty” is a graphical representation of the degree of uncertainty in a project estimate over time. It shows that the range of possible outcomes is wider at the beginning of the project and narrows down as the project progresses and more information becomes available.

The “cone of uncertainty” can be used to illustrate that as a project forecast lengthens, it is increasingly less certain. This means that the longer the time horizon for a project, the more variability and risk there is in the estimate. This also implies that shorter iterations and frequent feedback can help reduce uncertainty and improve accuracy.

The “cone of uncertainty” cannot be used to determine whether to cut quality, similar to the “Iron Triangle” of project management. The “Iron Triangle” is a model that shows the trade-offs between scope, time, and cost in a project. Quality is often considered as a fourth dimension that is affected by these three factors. Cutting quality is not a desirable option for any project, especially for Scrum projects that value delivering high-quality products that meet customer needs.

The “cone of uncertainty” cannot be used to determine the cost of a project before it begins. The cost of a project depends on many factors, such as the scope, the resources, the complexity, the risks, and the market conditions. The “cone of uncertainty” only shows the range of possible outcomes based on the available information at a given point in time. It does not provide a definitive or accurate estimate of the cost before the project starts.

The “cone of uncertainty” cannot be used to determine the length of the next Sprint. The length of the next Sprint is determined by the Scrum Team based on their empirical experience and their ability to deliver a potentially releasable Increment of value. The “cone of uncertainty” does not provide any guidance on how long a Sprint should be or how much work can be done in a Sprint.

Sprint 0 is a term that some organizations use to describe a phase of work before the first official Sprint, where they do some upfront planning, design, architecture, or analysis1. However, this term is not consistent with the Scrum framework, which does not prescribe any pre-Sprint activities or phases2. Scrum starts with a Product Backlog that contains at least one valuable and feasible Product Goal, and enough Product Backlog items to initiate the first Sprint[3][3] . The Product Owner is accountable for maximizing the value of the product and the work of the Developers, and for managing the Product Backlog4. The Product Owner does not have any specific accountability during Sprint 0, because Sprint 0 is not a part of Scrum.

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.

The reason for choosing this answer is that it is consistent with the Scrum Guide1 and the Professional Scrum Product Owner™ (PSPO I) objectives and content2. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product3. It applies to all Scrum Teams that are involved in creating an integrated Increment, regardless of their size, complexity, or skills12. The Definition of Done ensures that the product meets the expectations and needs of the stakeholders and customers12.

The other answers are not as accurate or appropriate for this question:

A. Each Scrum Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.

B. The Scrum Masters from each Scrum Team define a common Definition of Done.

C. Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known.

These answers imply that there is no need for a common or shared Definition of Done among multiple Scrum Teams working on a single product12. However, this can lead to confusion, inconsistency, and conflicts in terms of quality standards, expectations, and feedback12. Moreover, having different Definitions of Done can compromise the integrity and value of the product as a whole12.

I hope this answer helps you understand how to apply your knowledge of Professional Scrum Product Owner™ (PSPO I) objectives and content in this question. If you have any further questions or feedback, please let me know. Thank you for using Bing!????

Scrum is a framework that is designed to be lightweight and easy to adopt. To get started with Scrum, the minimal requirements are indeed a Product Owner with enough ideas for a first Sprint, a Development Team to implement those ideas, and a Scrum Master to facilitate and guide the process. This aligns with the core principles of Scrum, which emphasize self-organization, collaboration, and the ability to deliver increments of value quickly and frequently.

The Scrum Guide outlines the roles within a Scrum Team and the necessity of having a Product Backlog with enough ‘Ready’ items to fill a Sprint. The guide also emphasizes the importance of having a clear definition of ‘Done’ before starting the first Sprint

 The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:

The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration.

The timebox for each Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month.

The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter.

The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value.

Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.

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, each Scrum Team should not have a separate Product Backlog.

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, there should be only one Product Owner for one product.

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.

 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 and 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.

In Scrum, feedback loops are essential mechanisms that allow for inspection and adaptation at regular intervals. The three feedback loops from the options provided are:

Sprint Review (A): This is a feedback loop that occurs at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. It involves stakeholders and provides an opportunity to inspect the progress towards the Product Goal.

Daily Scrum ©: This is a daily feedback loop for the Developers to synchronize their work and plan for the next 24 hours. It helps in identifying challenges and creating a plan to achieve the Sprint Goal.

Sprint Retrospective (D): This feedback loop occurs after the Sprint Review and before the next Sprint Planning. It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

The Refinement Meeting (B) is not considered a feedback loop but rather an ongoing process of adding details to Product Backlog items. Release Planning (E) is not a formal event in Scrum and thus not a prescribed feedback loop.

The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) materials describe these events as integral parts of the Scrum framework that serve as feedback loops1

Scrum

The two primary ways a Scrum Master helps a Scrum Team work at its highest level of productivity are by facilitating Scrum Team decisions and by removing impediments that hinder the Scrum Team12.The Scrum Master is a facilitator and a coach, helping the team remove impediments and facilitating team decisions12.This enables the team to focus on their work and maintain their productivity12.

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.

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 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 used to assess when work is complete on the product Increment.

The amount of work required of the Developers to complete a Product Backlog item selected during the Sprint Planning depends on the Definition of Done. The Definition of Done may vary from one Scrum Team to another, depending on the context and domain of work. However, it must be consistent within one team. If there are multiple Scrum Teams working on one product, they must share a common Definition of Done. If there is an organizational standard for a Definition of Done, all Scrum Teams must follow it as a minimum.

The Developers must ensure that each Product Backlog item they complete during a Sprint meets the Definition of Done. This means that they must perform all the necessary tasks and activities to deliver a high-quality product functionality that is usable, valuable, and potentially releasable. This may include analysis, design, development, testing, documentation, integration, deployment, or any other aspects that contribute to the quality and usability of the product.

The other options are not valid or relevant measures for the amount of work required of the Developers to complete a Product Backlog item. They are either too vague, arbitrary, or unrealistic. They are:

As much as they can fit into the Sprint, with remaining work deferred to the next Sprint: This is a too vague and unrealistic measure for the amount of work required of the Developers. It does not account for the quality or value of the product functionality delivered. It also does not respect the timebox or scope of the Sprint. It may lead to incomplete or unfinished work, technical debt, or scope creep.

All development work and at least some testing: This is a too arbitrary and insufficient measure for the amount of work required of the Developers. It does not account for the quality or value of the product functionality delivered. It also does not respect the Definition of Done or the potentially releasable nature of the Increment. It may lead to low-quality or unusable work, defects, or rework.

A proportional amount of time on analysis, design, development, and testing: This is a too restrictive and prescriptive measure for the amount of work required of the Developers. It does not account for the complexity or variability of the product functionality delivered. It also does not respect the self-organization or cross-functionality of the Developers. It may lead to over-engineering or waste.

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.

If a stakeholder is unhappy with the quality of the product, the Scrum Master can coach the Product Owner on how to effectively communicate this concern to the Developers1.The Scrum Master can also encourage the Product Owner to put quality specifications on the Product Backlog1.This allows the Developers to understand the stakeholder’s expectations and work towards meeting them1.The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality1.

The Sprint Goal is a short statement that gives the Sprint a purpose, direction, and focus. It is created by the entire Scrum Team during Sprint Planning, based on the Product Owner’s draft and the Developers’ input. The Sprint Goal is then added to the Sprint Backlog and guides the Developers’ work during the Sprint.

What is a Sprint Goal?

The Sprint Goal

How to Write and Use a Sprint Goal (With 5 Templates)

The main topic of discussion is the product Increment, which is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints1.The product Increment is demonstrated and inspected by the attendees, and feedback is collected to inform the next Sprint Planning12.The Sprint Review may also include other topics, such as the Product Backlog, the Product Goal, the market conditions, the budget, and the timeline, but the product Increment is the essential topic1234.The Scrum process, and how it was used during the Sprint, is not a topic for the Sprint Review, but rather for the Sprint Retrospective, which is a separate event where the Scrum Team inspects and adapts its way of working1.Coding and engineering practices are also not relevant for the Sprint Review, as they are internal aspects of the Development Team that do not affect the value of the product Increment1. Therefore, the correct answer is C. The product Increment.

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.

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.

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 Daily Scrum is an event for and by the Developers.They can choose whatever structure and technique they want, as long as they focus on the progress toward the Sprint Goal and produce an actionable plan for the next day of work12. The Scrum Master, the Product Owner, and the person coming in last are not necessarily the ones who should start the Daily Scrum.The person who has the token is a possible technique, but not the only one3.

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.

Correct Answer: True

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 Backlogitems, 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.

[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.”

A Product Owner orders a Product Backlog in any way they think will maximize the value of the product1. They take various factors into consideration when ordering the Product Backlog such as business value, risk, return on investment (ROI), dependencies and impact1. Dependencies between Product Backlog items and their relevance to achieving theProduct Goal are two of these factors12. The availability of the Scrum Master and the number of stakeholders who approve of the item are not valid criteria for ordering the Product Backlog3.

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.

A Product Owner is accountable for maximizing the value of the product that is the result of the work of the Scrum Team. However, they can delegate some of their responsibilities to others, while still remaining accountable for the work. Two of the responsibilities that can be delegated to others are:

Attending the Sprint Retrospective. The Sprint Retrospective is an event where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The purpose of the Sprint Retrospective is to plan ways to improve quality and effectiveness. The Product Owner may attend the Sprint Retrospective as one of the Scrum Team members who has a stake in the outcome of the product development. However, they can also choose not to attend or delegate their attendance to someone else who can represent their interests and perspectives.

Attending the Sprint Review. The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration. The Product Owner is accountable for ensuring that key stakeholders attend the Sprint Review and that they understand what has been done and what can be done next. However, they can also delegate some of their tasks to others who can facilitate or present the Increment on their behalf.

Other options, such as ordering Product Backlog items or developing and communicating the Product Goal, are not responsibilities that can be delegated to others by the Product Owner. They are essential accountabilities that only the Product Owner can perform.

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

The Product Owner and the Scrum Master are essential roles in the Scrum Team. They have distinct accountabilities and responsibilities that contribute to the success of the product and the team. The Product Owner is responsible for maximizing the value of the product and the work of the Developers. The Scrum Master is responsible for promoting and supporting Scrum and the Scrum Team. Both roles need to be fully engaged and available to the Scrum Team throughout the Sprint.

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.

The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful.The other options are not accurate descriptions of the Product Backlog, as it does not contain all foreseeable tasks and requirements, it does not provide just enough information to start the design phase, and it is not baselined to follow change management processes23.

1:What is a Product Backlog? | Scrum.org2:What is a Product Backlog? | Agile Alliance3:Product Backlog: Definition, Examples and Techniques | Wrike Guide

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a “Done” Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.

The Scrum Guide

The Scrum Team

Professional Scrum Product Owner™ I Certification

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.

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

Sprints are fixed-length events of one month or less that serve as a container for the other Scrum events and activities. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. There is no gap or downtime between Sprints. The second Sprint starts right after the first Sprint, regardless of the customer acceptance testing, the architectural changes, or the Product Backlog items.

The Scrum Guide

Understanding and Applying the Scrum Framework

Professional Scrum Product Owner™ I Certification

The metrics that will help a Product Owner determine if a product is delivering value are customer satisfaction and time to market. This is because:

Customer satisfaction is a measure of how well the product meets the needs and expectations of the customers5. It reflects the value proposition of the product and the feedback from the users.

Time to market is a measure of how quickly the product can be delivered to the market. It reflects the agility and responsiveness of the Scrum Team and the ability to deliver value early and often.

Other metrics, such as productivity, velocity, and percentage of scope implemented, are not directly related to value delivery. They may indicate how efficiently or effectively the Scrum Team is working, but they do not necessarily reflect how valuable or desirable the product is for the customers or stakeholders.

Multiple Scrum Teams working on the same product do not have to have the same Sprint start date. The Scrum Guide does not prescribe any synchronization of Sprints across multiple teams1. However, it is recommended that the teams align their Sprint cadence and duration, and coordinate their dependencies and integration through a shared Product Backlog, a common Definition of Done, and frequent communication2. This way, the teams can deliver a coherent and valuable product Increment every Sprint[3][3] .

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.

Scrum does not require that the Product Owner must use any of the following items:

Burndown chart: A burndown chart is a graphical representation of work left to do versus time. It can be used to track progress and forecast completion dates of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.

Feature burn-up: A feature burn-up chart is a graphical representation of features completed versus time. It can be used to track progress and forecast scope changes of projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to monitor and communicate product development.

Critical Path Analysis: Critical Path Analysis is a project management technique that identifies the sequence of tasks that must be completed on time for a project or Sprint to finish on schedule. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.

Project Gantt chart: A project Gantt chart is a graphical representation of tasks, dependencies, durations, and milestones of a project or Sprint. It can be used to plan, monitor, and control complex projects or Sprints. However, it is not mandatory or prescribed in Scrum. It is one of the possible techniques that a Product Owner may use to manage product development.

Therefore, the correct answer is none of the above.

The advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team are:

It provides a good overall direction so Sprints will feel less like isolated pieces of work. The Product Goal is a long-term objective for the product that guides all the activities of the Scrum Team. It helps the Scrum Team align their efforts and focus on delivering value that contributes to the product vision.

It helps the Scrum Team keep focus and they can weigh any decision against the Product Goal. The Product Goal serves as a filter for deciding what to work on and what not to work on. It helps the Scrum Team prioritize and optimize their work based on value and impact.

It is easier to inspect incremental progress at the Sprint Review. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate on the product and inspect how it meets the Product Goal. The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress towards the Product Goal.

Other options, such as helping the Developers estimate the date that the Product Backlog will be complete or being not mandatory in Scrum, are not valid advantages of having a Product Goal. They may reflect a misunderstanding of what a Product Goal is or how Scrum works.

The concept of a “Release Sprint” is not found in the Scrum Guide or the Professional Scrum Product Owner™ (PSPO I) materials. Scrum does not require a separate Sprint for releasing an Increment. According to Scrum, each Increment must be usable and potentially releasable at the end of every Sprint, which means the product should be in a releasable state irrespective of whether the Product Owner decides to release it or not. The idea of a Release Sprint is not aligned with Scrum’s principle of continuous delivery and the definition of “Done”.

The Scrum Guide and the Professional Scrum Product Owner™ (PSPO I) study materials emphasize the importance of the Increment being releasable after every Sprint without the need for an additional Release Sprint12.

 An Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.1 An Increment is a concrete, tangible, and usable outcome of the work done by the Developers in a Sprint. It is not a plan, a mock-up, a design, or a roll-out plan, as these are not valuable or useful products in themselves. An Increment must meet the definition of “Done”, which means it must adhere tothe quality standards agreed upon by the Scrum Team and the stakeholders.1 An Increment must also be potentially releasable, which means it must be in a state that it could be delivered to the customer or user if the Product Owner decides so.1

1: The Scrum Guide2, page 14

2: The Scrum Guide

Transparency is one of the three pillars of Scrum, along with inspection and adaptation. Transparency means that all aspects of the Scrum process and the product are visible and understandable to everyone who needs to work on or with them. Transparency enables effective inspection and adaptation, which are essential for delivering valuable products and improving the Scrum Team’s performance.

All Scrum artifacts must be transparent to ensure sufficient accuracy of inspection. Scrum artifacts include the Product Backlog, the Sprint Backlog, and the Increment. 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.

Two measures that ensure that the Product Backlog is transparent are:

The Product Backlog is ordered: The Product Owner orders the items in the Product Backlog based on factors such as value, risk, priority, dependency, feedback, or market conditions. The order of the Product Backlog items provides a clear and consistent indication of what is most important and urgent for the product. The order of the Product Backlog items also helps the Scrum Team and the stakeholders to plan and forecast effectively.

The Product Backlog is available to all stakeholders: The Product Owner makes the Product Backlog visible and accessible to everyone who has a stake in the product, such as customers, users, sponsors, managers, or other teams. The availability of the Product Backlog enables transparency, collaboration, feedback, and alignment among all parties involved in the product development.

The other options are not valid or relevant measures to ensure that the Product Backlog is transparent. They are either too restrictive, arbitrary, or unrelated to the Product Backlog’s transparency. They are:

Each Product Backlog item has a MoSCoW priority: MoSCoW is a technique for prioritizing requirements based on their importance: Must have, Should have, Could have, or Won’t have. While this technique can be useful for some products or contexts, it is not a mandatory or universal way to order the Product Backlog items. The Product Owner may use other factors or methods to order the Product Backlog items based on their value and relevance for the product.

The Product Backlog only has work for the next 2 Sprints: This is a too limiting and unrealistic measure for the Product Backlog. The Product Backlog should contain all the work that is known to be needed in the product, not just for the next 2 Sprints. The Product Backlog is a living artifact that evolves as the product and the market change. The Product Owner should continuously refine and update the Product Backlog to reflect the current and future needs and expectations of the customers and users.

The Product Backlog is managed using a web-based tool: This is an irrelevant measure for the Product Backlog’s transparency. The Product Owner can use any tool or format to manage the Product Backlog, as long as it is clear, concise, and valuable. The tool or format does not affect the transparency of the Product Backlog itself. What matters more is how the Product Owner communicates and collaborates with the Scrum Team and the stakeholders using the Product Backlog.

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

 New work or further decomposition of work is added to the Sprint Backlog as soon as possible after it is identified because:

It reflects the current state of the Sprint. The Sprint Backlog is a plan that the Developers create and update throughout the Sprint, based on their progress, learnings, and changes. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that the Sprint Backlog is transparent, accurate, and up-to-date.

It enables the Developers to self-manage their work. The Developers are accountable for organizing and managing their own work, and they have the authority to change the Sprint Backlog as needed. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can exercise their autonomy and empowerment, and adjust their plan accordingly.

It supports the achievement of the Sprint Goal. The Sprint Goal is a single objective that provides guidance and focus for the Developers throughout the Sprint. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that their work is aligned with and contributes to the Sprint Goal.

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.