Scrum PSM-III Exam Dumps

The situation described directly touches on several core Scrum Values, which guide behavior and collaboration within Scrum Teams. In particular, the values of Courage, Respect, and Openness are most prominently involved.

First, the value of Courage is demonstrated by the junior developer. Speaking up about feeling unheard, especially in front of more experienced colleagues, requires personal courage. Scrum encourages team members to be brave in raising difficult or uncomfortable issues so that problems can be addressed rather than ignored. Without courage, important impediments to collaboration and effectiveness would remain hidden.

Second, the situation highlights a lack of Respect in team interactions. Scrum emphasizes that Scrum Team members respect each other as capable, independent individuals. Interrupting a colleague or disregarding their input---regardless of seniority---undermines this value. Respect is essential for effective collaboration and for creating an environment where all team members can contribute fully.

Third, the value of Openness is central to this scenario. Scrum Teams are expected to be open about challenges, feedback, and differing perspectives. Openness also means being receptive to ideas from all team members, independent of role, experience level, or background. Disregarding input from a junior developer contradicts Scrum's emphasis on openness and reduces the quality of decision-making.

When the Product Owner becomes unexpectedly unavailable, the Scrum Team must respond in a way that preserves continuity, transparency, and value delivery, while respecting Scrum accountabilities.

Short-Term Response

In the short term, covering the current Sprint and possibly the next Sprint, the Scrum Team should be able to continue working. Scrum is designed to be resilient to short-term disruptions. The team can proceed by relying on:

The Product Vision previously communicated by the Product Owner,

The current state and ordering of the Product Backlog, which should already reflect the Product Owner's value decisions.

During this period, the Developers continue to work toward the Sprint Goal, and the Scrum Master ensures that Scrum events take place and remain productive. No one should assume the Product Owner role informally, as this would undermine accountability.

Longer-Term Impact

If the Product Owner's absence extends beyond a short period, it becomes an impediment to the Scrum Team. The Product Owner is accountable for maximizing product value and managing the Product Backlog. Prolonged absence prevents effective backlog ordering, stakeholder collaboration, and value-based decision-making.

In this case, the Scrum Master must make the impediment visible to the organization. This includes explaining the impact on value delivery and helping leadership understand the need for a clear Product Owner accountability. The organization should then appoint a new Product Owner to ensure continuity of decision-making and accountability.

According to Scrum, the Product Owner is accountable for maximizing the value of the product and for effective Product Backlog management. Two key activities that are explicitly part of this role are:

1. Ordering the Product Backlog to Maximize Value

The Product Owner is responsible for ordering the Product Backlog so that the most valuable work is done first. This ordering reflects:

Business and customer value,

Risk and uncertainty,

Strategic goals and learning from previous Sprints.

Through this activity, the Product Owner ensures that the Scrum Team is always working on what matters most.

2. Ensuring Product Backlog Items Are Transparent, Clear, and Understood

The Product Owner ensures that Product Backlog Items are:

Clearly expressed,

Transparent to the Scrum Team and stakeholders,

Understood well enough for Developers to select them during Sprint Planning.

This does not mean writing detailed requirements alone, but collaborating so that shared understanding exists.

Scrum encourages ethical behaviour in software development by creating a framework that promotes transparency, accountability, quality, and respect for stakeholders, all of which are grounded in the Scrum Values. Rather than prescribing ethical rules, Scrum embeds ethical behaviour into the way work is organized and delivered.

First, Scrum promotes ethics through its focus on delivering valuable, high-quality working products. The Scrum Guide emphasizes delivering usable Increments that meet a shared Definition of Done. By prioritizing quality and value for both the organization and end-users, Scrum discourages practices such as cutting corners, hiding technical debt, or delivering misleading progress, which are ethically questionable.

Second, Scrum strongly supports transparency, a core pillar of empiricism. All significant aspects of the work---such as progress, impediments, risks, and uncertainties---are made visible through artifacts and events. This transparency encourages honesty about what can and cannot be achieved and prevents unethical behaviour such as misreporting status or concealing problems until it is too late.

Third, Scrum encourages accountability at both individual and team levels. Clear accountabilities for the Product Owner, Developers, and Scrum Master ensure that responsibility is not diffused or avoided. Teams are accountable for delivering value, improving their way of working, and meeting their commitments. This accountability fosters ethical decision-making and ownership of outcomes.

Fourth, Scrum supports ethical behaviour through continuous learning and improvement. Sprint Retrospectives create a structured opportunity to reflect on mistakes, share knowledge, and improve processes and practices. This openness to learning promotes humility, integrity, and a willingness to correct issues rather than ignoring or rationalizing them.

Finally, Scrum is explicitly guided by the Scrum Values of Commitment, Courage, Focus, Respect, and Openness, which form its ethical foundation.

Commitment encourages teams to do what they say they will do.

Courage enables individuals to raise concerns, admit problems, and challenge unethical practices.

Focus helps teams concentrate on delivering real value rather than superficial outputs.

Respect ensures consideration for colleagues, stakeholders, and end-users.

Openness promotes honesty about progress, challenges, and uncertainty.

From a Scrum Master's perspective, this situation must be approached by balancing respect for Scrum accountabilities, protection of empiricism, and long-term value delivery, rather than reacting solely to short-term urgency.

First, it is important to reaffirm that the Development Team owns the Sprint Backlog. According to the Scrum Guide, once the Sprint has started, changes to the Sprint Backlog are negotiated only between the Product Owner and the Development Team, and the Development Team has the final say on whether additional work can be taken on. Therefore, the Product Owner cannot unilaterally force the urgent item into the Sprint, even if it represents the highest customer priority. If the Development Team believes it can incorporate the item without jeopardizing the Sprint Goal, it may choose to do so---but this remains their decision.

Second, the Scrum Master should help the Product Owner understand that not all priorities are equal within a Sprint. The Sprint Goal provides focus and stability, and work that is not related to the Sprint Goal introduces risk. While satisfying the customer is important, Scrum explicitly values sustainable improvement and learning. The process improvement goal agreed upon during the Sprint Retrospective represents a deliberate investment in the team's effectiveness. Sacrificing this improvement for short-term delivery may create a local optimization that harms long-term customer value.

Third, the Scrum Master should coach both the Product Owner and the Development Team on the systemic impact of slowing process improvements. Continuous improvement is a core expectation of Scrum, and the Scrum Guide states that the Scrum Team should plan ways to increase quality and effectiveness. When improvement goals are repeatedly deprioritized, delivery predictability, quality, and morale eventually decline---directly affecting customers. Therefore, the Product Owner's argument that customer needs always outweigh improvement work reflects a short-term mindset that the Scrum Master should challenge through education and coaching.

Fourth, this situation should be inspected during the Sprint Retrospective. The team should reflect on why urgent, unplanned work appears late in the Sprint, whether it represents a recurring pattern, and how this impacts Sprint Goals and improvement commitments. The Scrum Master should facilitate this discussion to ensure transparency and learning, rather than blame.

Finally, if this behavior becomes a pattern, the Scrum Master must take a more active stance. This includes teaching and reminding the Scrum Team that at least one improvement from the Sprint Retrospective should be planned into the upcoming Sprint. This protects the intent of the Retrospective and ensures that improvement is not treated as optional or expendable work.