Correct Answer:

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 forScrum Teams, especially inscaled environments.
1. Risk of Component-Centric Team Structures
When system decomposition drives team structure, organizations often createcomponent 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 deliverend-to-end, integrated Incrementseach Sprint, weakening empiricism and delaying feedback.
2. Impact on Value Delivery and Inspection
Scrum relies on frequent inspection ofworking 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 intovertical, 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 happensearly 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.

Correct Answer:

TheSprint Reviewis a key Scrum Event that directly enablesempiricism, which is the foundation of Scrum.
Empiricism is based on making decisions using what is known, observed, and learned, supported by the pillars oftransparency, inspection, and adaptation. The Sprint Review operationalizes these pillars at the product level.
How the Sprint Review Enables Empiricism
First, the Sprint Review createstransparencyby making the current state of the product visible. During the event, the Scrum Team presents a"Done" Product Incrementthat meets the Definition of Done. Stakeholders can see and often use the actual product rather than relying on reports or assumptions. This shared visibility ensures that discussions are grounded in reality.
Second, the Sprint Review enablesinspection. The Scrum Team and stakeholders jointly inspect the Increment and assess progress toward product goals. The Developers provide context about what was delivered, what was not, and what challenges were encountered. This inspection is focused on outcomes and value, not individual performance.
Third, the Sprint Review supportsadaptation. Based on the inspection and feedback, new insights emerge about customer needs, market conditions, risks, and opportunities. The Product Owner uses this information to adapt the Product Backlog, reordering items, adding new work, or refining existing items. This completes the empirical feedback loop by ensuring future decisions are based on the latest evidence.
Impact of Development Team Members Not Attending the Sprint Review
If some Developers are not present at the Sprint Review, empiricism is weakened.
First,transparency decreases. Developers possess critical, first-hand knowledge about implementation details, technical trade-offs, constraints, and risks. Without their presence, stakeholders receive an incomplete picture of the Increment and its implications.
Second,inspection becomes less effective. Stakeholders may ask questions about behavior, limitations, or quality that only Developers can accurately answer. The absence of Developers limits meaningful dialogue and reduces the quality of inspection.
Third,adaptation suffers. Decisions about what to do next-such as changes to scope, priorities, or technical direction-depend on accurate understanding. Without Developers participating, adaptations to the Product Backlog may be based on assumptions rather than evidence, increasing the risk of poor decisions.
Finally, excluding Developers underminesScrum Values, particularlyRespect and Openness, by treating the Sprint Review as a reporting event rather than a collaborative working session. This can lead to disengagement and reduced shared ownership of product outcomes.

Correct Answer:

When a Development Team is distributed across different physical locations and faces logistical overhead just to start theDaily Scrum, this situation represents animpediment to effective inspection and adaptation. As a Scrum Master, the appropriate action is toenable the team to inspect and adapt more effectively, not to control or manage logistics on their behalf.
1. Help the Team Establish a Stable and Simple Daily Scrum Setup
The Scrum Master should work with the Development Team toinspect and improve how the Daily Scrum is conducted. This may include:
* Agreeing on afixed time and virtual location,
* Standardizing tools (e.g., always the same conferencing solution),
* Reducing setup effort so the event can start on time and remain within its 15-minute timebox.
This supports transparency and reduces unnecessary waste.
2. Remove or Reduce Organizational and Technical Impediments
If logistical difficulties stem from organizational constraints-such as lack of proper tooling, inadequate rooms, or unreliable communication infrastructure-the Scrum Master shouldaddress these as impediments.
This may involve working with IT or management to provide stable tools that enable smooth collaboration.
3. Coach the Team Toward Self-Management
Rather than running the Daily Scrum or handling logistics personally, the Scrum Master shouldcoach the Developers to self-managehow they organize the event. The goal is for the team to own and continuously improve the Daily Scrum in a way that fits their distributed context.

Correct Answer:

A distant Product Owner represents arisk to value delivery, transparency, and empiricism. While the Product Owner has provided a Product Backlog for the Sprint, lack of collaboration during the Sprint undermines learning and informed decision-making. As a Scrum Master, the focus should be oncoaching, enabling collaboration, and addressing systemic impediments, not substituting for the Product Owner.
1. Make the Impact Transparent
The Scrum Master should help make the impact of the Product Owner's absencevisible:
* Reduced ability to clarify Product Backlog Items,
* Slower decision-making when discoveries occur,
* Increased risk to the Sprint Goal and product value.
This transparency should be established through respectful conversations with the Product Owner and, if needed, through Scrum events such as the Sprint Retrospective.
2. Coach the Product Owner on Accountability
The Scrum Guide states that the Product Owner is accountable formaximizing valueandProduct Backlog management, which requires ongoing collaboration with Developers. The Scrum Master should coach the Product Owner to understand that handing over a backlog at Sprint Planning isnot sufficientand that availability during the Sprint is essential for empiricism.
3. Enable Better Collaboration Without Replacing the Product Owner
The Scrum Master should help create opportunities for collaboration, such as:
* Encouraging regular clarification moments during the Sprint,
* Improving Product Backlog refinement so fewer questions remain unanswered,
* Helping Developers prepare focused questions to use limited Product Owner availability effectively.
However, the Scrum Master mustnot take over Product Owner responsibilities, as this would blur accountabilities.
4. Address Organizational Causes
If the Product Owner's distance is due to workload, role confusion, or organizational pressure, this becomes an organizational impediment. The Scrum Master should raise this issue with leadership and help the organization understand the risk of an unavailable Product Owner to product outcomes.