PSM-III Exam Dumps and Practice Questions

If not all Development Team members are present at the Daily Scrum, several risks are introduced that undermine empiricism, collaboration, and the team's ability to achieve the Sprint Goal.

First, transparency is reduced. The Daily Scrum exists to create a shared understanding of progress, plans, and impediments. When some Developers are absent, their work, discoveries, risks, or impediments are not fully visible to the rest of the team. This results in an incomplete or inaccurate picture of the Sprint Backlog's current state.

Second, inspection becomes ineffective. The Daily Scrum is the primary event where Developers inspect progress toward the Sprint Goal. Missing perspectives means that inspection is based on partial information, increasing the likelihood that important issues---such as integration problems, dependencies, or quality concerns---go unnoticed until later in the Sprint.

Third, adaptation is delayed or suboptimal. Without full participation, the team may make planning adjustments that do not account for all constraints or opportunities. This can lead to rework, misalignment, or duplicated effort, and increases the risk of failing to meet the Sprint Goal.

Fourth, the absence of team members weakens collective ownership and accountability. The Daily Scrum reinforces that the Developers are jointly responsible for the Sprint Goal. Regular absence can create silos, reduce collaboration, and signal that shared planning and alignment are optional.

Finally, over time, inconsistent attendance can turn the Daily Scrum into a status meeting for those present, rather than a collaborative planning event for the whole team. This undermines Scrum Values, particularly Commitment, Respect, and Openness.

In Scrum, inspection is effective only when it is performed by knowledgeable and skilled inspectors. The Product Owner plays a critical leadership role in inspection, particularly when it comes to product value and direction. Two key ways in which the Product Owner takes the lead in the inspection process are outlined below.

1. Leading Inspection of Product Value Through the Product Backlog

The Product Owner takes the lead in inspection by continuously inspecting the Product Backlog in light of new information, feedback, and changing conditions. By ordering and refining the Product Backlog, the Product Owner inspects whether:

The backlog reflects the current understanding of customer needs,

Items are aligned with the Product Goal,

The highest-value work is being prioritized.

This inspection ensures that future work is based on evidence rather than assumptions and that the Scrum Team is always working on the most valuable items.

2. Leading Product Inspection During the Sprint Review

The Product Owner also leads inspection during the Sprint Review. While the event is collaborative, the Product Owner frames the conversation by:

Explaining the Product Goal and current priorities,

Helping stakeholders inspect the Increment against desired outcomes,

Guiding discussions about what to do next based on feedback and evidence.

By facilitating value-focused inspection rather than feature-based approval, the Product Owner ensures that learning from the Increment directly informs Product Backlog adaptation.

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.

Leadership plays a critical role in enabling self-organizing teams to succeed with Scrum. While Scrum Teams are self-managing, organizational leadership must create the conditions in which Scrum can thrive. This support is expressed through behaviors that reinforce empiricism, accountability, and continuous improvement, rather than through command-and-control practices.

First, leadership can help by actively supporting self-organization and Scrum adoption. This includes trusting teams to decide how they do their work, resisting the urge to micromanage, and reinforcing Scrum practices and values across the organization. Leaders who understand and support Scrum help protect teams from external pressure that undermines self-management.

Second, leaders should learn about Agile and Scrum and understand how to interact with Scrum Teams effectively. This knowledge enables leadership to engage in ways that are helpful rather than disruptive---for example, collaborating through Scrum events instead of bypassing the Product Owner or directly assigning work to Developers. Informed interaction strengthens alignment while preserving team autonomy.

Third, leadership must respect Scrum accountabilities, especially the authority of the Product Owner. Respecting Product Owner decisions on ordering the Product Backlog ensures clear accountability for maximizing value. When leadership overrides or bypasses the Product Owner, it undermines transparency, focus, and trust within the Scrum Team.

Fourth, leadership can significantly support teams by removing impediments that are beyond the team's control. These may include organizational policies, structural constraints, tooling limitations, or conflicting incentives. By actively addressing such impediments, leadership enables teams to improve their effectiveness and deliver value more consistently.

Finally, leadership should provide a clear organizational vision and strategy. A compelling vision and coherent strategy give Scrum Teams a sense of purpose and direction, helping them understand how their work contributes to broader organizational goals. This clarity supports better decision-making, alignment, and motivation at the team level without prescribing detailed solutions.

Scrum defines three core artifacts that provide transparency into the work being done and the value being delivered: the Product Backlog, the Sprint Backlog, and the Product Increment. Each artifact is inspected at specific Scrum Events to support empiricism through transparency, inspection, and adaptation.

Product Backlog

The Product Backlog is an ordered list of everything that is known to be needed in the product and is the single source of work for the Scrum Team.

It is inspected during Sprint Planning, where the Scrum Team selects Product Backlog Items to work on and aligns them with the Sprint Goal.

It is also inspected during the Sprint Review, where stakeholders and the Scrum Team review progress and adapt the Product Backlog based on feedback and new insights.

In addition, the Product Backlog is continuously inspected and adapted during Backlog Management (often called refinement). While this activity is essential, it is not a Scrum event in the strict sense.

Sprint Backlog

The Sprint Backlog consists of the Sprint Goal, the selected Product Backlog Items for the Sprint, and a plan for delivering them.

It is created and inspected during Sprint Planning, where the Developers forecast the work needed to achieve the Sprint Goal.

It is inspected daily during the Daily Scrum, as Developers assess progress toward the Sprint Goal and adapt their plan accordingly.

It may also be inspected during the Sprint Review to provide transparency into what was planned versus what was accomplished.

Product Increment

The Product Increment is the sum of all completed Product Backlog Items during the Sprint and previous Sprints that meet the Definition of Done.

It is inspected during Sprint Planning, to understand the current state of the product and determine what can be built next.

It is inspected during the Sprint Review, where stakeholders evaluate the Increment and provide feedback.

The Increment may also be inspected at any time to support transparency and decision-making.

Continuous Inspection Beyond Events

While Scrum defines specific events where artifacts are commonly inspected, the Scrum Guide emphasizes that artifacts may be inspected at any time, as long as the inspection does not hinder progress. Scrum encourages frequent inspection to enable timely adaptation and reduce risk.