Scrum PSM-III Practice Exam Questions & Answers

Technical systems are often decomposed into smaller elements such as activities, workflows, functions, features, or components to manage complexity. While decomposition is necessary for understanding and building large systems, it has significant implications for Scrum Teams, especially in scaled environments.

1. Risk of Component-Centric Team Structures

When system decomposition drives team structure, organizations often create component or specialist teams aligned to technical layers or functions. In scaled Scrum, this increases:

Dependencies between teams,

Coordination overhead,

Integration risk.

Such structures make it difficult for teams to deliver end-to-end, integrated Increments each Sprint, weakening empiricism and delaying feedback.

2. Impact on Value Delivery and Inspection

Scrum relies on frequent inspection of working product Increments. If work is decomposed into narrowly defined technical components, individual teams may only deliver partial outputs rather than usable value. This reduces transparency and makes meaningful inspection at the product level harder, especially when multiple teams are involved.

3. Preference for Feature-Oriented Decomposition

Scrum favors decomposing work into vertical, value-oriented slices (features or capabilities) rather than horizontal technical layers. This allows each Scrum Team to be:

Cross-functional,

Capable of delivering usable Increments independently,

Less dependent on other teams.

In scaled projects, feature-oriented decomposition reduces dependencies and improves flow.

4. Effects on Integration and Empiricism

Poor decomposition increases the cost of integration and often leads to late or infrequent integration. Scrum requires that integration happens early and often, as unintegrated work is not ''Done.'' In scaled Scrum, decomposition choices directly influence whether integration is continuous or deferred, with major implications for risk control.

5. Organizational and Learning Implications

System decomposition also affects learning and adaptability. When teams own complete features rather than isolated components, they gain a better understanding of:

Customer needs,

System behavior,

Trade-offs across the product.

This broader understanding improves decision-making and supports continuous improvement across the system.

When Developers raise the lack of certain knowledge or expertise as an impediment, the Scrum Master must address the situation in a way that reinforces Scrum principles, especially cross-functionality, empiricism, and self-management, while also supporting value delivery.

First, it is essential to verify whether this is truly an impediment. In Scrum, an impediment is something the team cannot resolve on its own. As a Scrum Master, I would facilitate a discussion with the Developers and, if appropriate, the Product Owner to inspect whether the expertise is genuinely required to achieve the desired outcome. In some cases, the scope or approach can be adapted, or the Product Backlog Item can be refined so that alternative solutions are viable. This conversation may reveal that the need for specialized knowledge is less critical than initially assumed.

Second, if the expertise is indeed necessary, the Scrum Master should encourage the team to address the issue as a cross-functional Scrum Team. Scrum expects teams to have, or acquire, all skills needed to deliver value. Therefore, I would ask the Developers how they could learn or acquire the necessary knowledge themselves. Possible options include allocating time for learning, research, training, experimenting, or building a prototype. These activities can be planned as part of the Sprint Backlog and support long-term team capability.

Third, the Scrum Master can help the team make effective use of outside expertise without undermining self-management. During Sprint Planning or refinement, the team may consult internal or external experts to gain insights, validate approaches, or reduce uncertainty, while still retaining ownership of the work and the Sprint Backlog.

Finally, if none of these options resolve the impediment, the Scrum Master has a responsibility to help the organization support the Scrum Team. This may involve facilitating access to expertise from elsewhere in the organization or, if necessary, from outside the organization. The Scrum Master does not solve the problem personally but works to remove organizational barriers so the team can proceed.

When many Development Teams are working on a single product, there must be one shared Definition of Done (DoD) that applies to all teams and to the entire product Increment.

Single, Shared Definition of Done

Scrum requires that each Increment be usable and potentially releasable. When multiple teams contribute to one product, this means:

There is one product, not multiple team products,

There must therefore be one Definition of Done that ensures consistency, quality, and transparency across all teams.

Having different Definitions of Done per team would result in:

Inconsistent quality,

Integration problems,

Loss of transparency,

Increments that are ''Done'' in isolation but not at the product level.

Integrated Increment-Level Definition of Done

The shared Definition of Done must include integration criteria, ensuring that:

Work from all teams is integrated,

The combined Increment meets quality and compliance standards,

The product can be inspected and potentially released.

In scaled Scrum (e.g., Nexus), unintegrated work is explicitly not considered Done, regardless of whether individual teams believe their work is complete.

Ownership and Evolution

While Developers collectively create and adhere to the Definition of Done, it applies at the product level, not the team level. As the product and organization mature, the Definition of Done may be expanded, but it must always remain shared and transparent.

When a Product Owner raises concerns about the team's commitment and productivity based on comparisons of velocity with other teams, this signals a need for coaching on empiricism, transparency, and appropriate use of Scrum metrics. As a Scrum Master, my response would focus on reframing the discussion from output comparison to value delivery and continuous improvement.

First, I would explain that velocity is a team-specific, contextual measure. Velocity reflects how much work a specific team completes within a given context, using its own Definition of Done, skills, tooling, and domain complexity. The Scrum Guide does not define velocity as a performance or comparison metric. Comparing velocity across teams is misleading and risks encouraging dysfunctional behavior, such as inflating estimates, cutting quality, or gaming the system. Therefore, a higher velocity does not automatically indicate higher productivity, commitment, or value delivery.

Second, I would explore the Product Owner's underlying concern rather than focusing on velocity itself. Often, concerns about velocity are proxies for deeper issues such as:

Missed Sprint Goals,

Unmet stakeholder expectations,

Slow value delivery,

Quality problems or unpredictability.

As a Scrum Master, I would help the Product Owner articulate what outcome they are truly worried about, and then guide the discussion toward metrics and observations that better reflect those concerns, such as progress toward Product Goals, customer feedback, Increment quality, or predictability over time.

Third, I would reinforce the importance of empiricism and transparency. If there are genuine concerns about commitment or effectiveness, these should be inspected using transparent evidence within the team's own context. The Sprint Review and Sprint Retrospective provide structured opportunities to inspect outcomes and ways of working. Rather than privately judging the team based on external comparisons, these concerns should be addressed openly and constructively with the Scrum Team.

Fourth, I would coach the Product Owner on Scrum Values, particularly Respect and Openness. Assuming lower commitment based on velocity comparisons risks undermining trust and psychological safety. Scrum encourages respecting the team as capable professionals and being open to learning what is actually limiting their effectiveness. Blame-oriented comparisons reduce the likelihood of honest inspection and improvement.

Finally, if improvement is needed, the Scrum Master should support the Scrum Team in identifying and addressing impediments. This may involve examining workload, technical debt, unclear backlog items, excessive dependencies, or organizational constraints. The focus should be on enabling the team to improve sustainably, not on pushing them to match another team's numbers.

From a Scrum Master's perspective, replacing the Daily Scrum with a weekly update meeting is not consistent with Scrum and would significantly weaken the team's ability to inspect and adapt effectively, regardless of the Sprint length.

First, Scrum explicitly defines the Daily Scrum as a required event. The Scrum Guide states that the Daily Scrum is a 15-minute event held every working day of the Sprint for the Developers. The length of the Sprint---whether one week or one month---does not change the purpose or necessity of this event. Therefore, by choosing not to have a Daily Scrum, the team would no longer be practicing Scrum, but rather a Scrum-like process.

Second, the Daily Scrum is not a status meeting. Its primary purpose is to allow the Developers to inspect progress toward the Sprint Goal, synchronize their work, and adapt the Sprint Backlog as needed. A weekly meeting dramatically reduces the frequency of inspection and adaptation, delaying the discovery of issues such as integration problems, misalignment, or risks to the Sprint Goal.

Third, removing the Daily Scrum negatively impacts transparency, one of Scrum's three pillars of empiricism. Without daily synchronization, important information about progress, impediments, and discoveries becomes stale or hidden. This reduced transparency increases the likelihood that work will drift away from agreed standards, fail to integrate properly, or no longer support the Sprint Goal by the end of the Sprint.

Fourth, the argument that a one-month Sprint justifies less frequent inspection reflects a misunderstanding of empiricism. Longer Sprints increase risk, which makes frequent inspection and adaptation more important, not less. The Daily Scrum provides a regular opportunity to realign the team and respond early to emerging problems, thereby reducing waste and rework.

Finally, as a Scrum Master, my role is to teach and coach the Scrum Team on the purpose and value of Scrum events. Rather than removing the Daily Scrum, I would help the Developers improve how they use it---for example, ensuring it focuses on progress toward the Sprint Goal and actionable planning for the next 24 hours, instead of turning into a reporting session.