The definition of "Done" describes the work that must be completed for every Product Backlog item before it can be deemed releasable. What should the Development Team do when, during the Sprint, it finds out that a problem outside of their control blocks them from doing all this work?
Correct Answer:
When the Development Team discovers during a Sprint that a problemoutside of their controlprevents them from completing all work required by theDefinition of Done, this situation must be addressed through transparency, inspection, and adaptation, rather than by lowering standards. 1. Make the Impediment Transparent Immediately The Development Team shouldmake the issue visible as soon as it is discovered. This includes: * Raising it in theDaily Scrum, * Clearly stating how it impacts the Sprint Goal and the Definition of Done. Transparency is critical so that inspection and adaptation are based on reality, not assumptions. 2. Do Not Compromise the Definition of Done The Definition of Done mustnot be relaxed or bypassedto "get something done." Lowering quality destroys transparency and creates false progress. If the Definition of Done cannot be met, the work isnot Doneand should not be considered releasable. 3. Collaborate to Adapt the Sprint Backlog The Development Team should collaborate with theProduct Ownerto inspect the impact and adapt the Sprint Backlog. This may include: * Removing or adjusting affected Product Backlog Items, * Focusing on work that can still meet the Definition of Done, * Preserving theSprint Goal, if possible. 4. Escalate the Impediment Through the Scrum Master Because the problem is outside the team's control, it qualifies as animpediment. The Scrum Master must help remove or mitigate it by working with the organization or external parties. If the impediment cannot be resolved quickly, its impact should be addressed in planning and stakeholder communication.
Question 2
In what ways does the Scrum Master attend the Sprint Retrospective?
Correct Answer:
The Sprint Retrospective is a formal Scrum event where the Scrum Team inspects how the last Sprint went with respect toindividuals, interactions, processes, tools, and their Definition of Done, and identifies improvements for future Sprints. The Scrum Master attends the Sprint Retrospective inmultiple, complementary ways, consistent with the Scrum Guide. First, the Scrum Masterjoins the Sprint Retrospective as a Scrum Team member. The Scrum Guide defines the Scrum Team as consisting of the Product Owner, Developers, and the Scrum Master. Therefore, the Scrum Master is not an external observer but afull participantin the event. As such, the Scrum Master activelyinspects people, processes, and tools, and contributes insights based on their perspective and experience, while remaining respectful of the team's self-management. Second, the Scrum Master oftenfacilitates the Sprint Retrospective. According to the Scrum Guide, the Scrum Master is accountable for ensuring that Scrum events take place and are productive. Facilitation may include helping the team create a safe environment, encouraging openness, ensuring balanced participation, keeping the discussion focused on improvement, and helping the team stay within the timebox. However, facilitation does not imply control; the Scrum Master facilitatesto serve the team, not to direct outcomes. Third, the Scrum Mastersupports empiricism during the Retrospective. By fostering transparency, encouraging honest inspection, and helping the team identify actionable improvements, the Scrum Master strengthens the Scrum pillars oftransparency, inspection, and adaptation. The Scrum Master may also help the team turn improvement ideas into concrete actions that can be planned for the next Sprint. Finally, the Scrum Master helps ensure that the Sprint Retrospective results inmeaningful adaptation. While the Scrum Team decides what improvements to implement, the Scrum Master supports the team in identifying impediments, coaching on improvement techniques, and helping remove organizational or systemic obstacles that are beyond the team's direct control. In summary, the Scrum Master attends the Sprint Retrospective byjoining as a full Scrum Team member, participating in inspection,often facilitating the event, andsupporting continuous improvement and empiricism. This balanced participation ensures that the Retrospective remains a powerful mechanism for learning and adaptation rather than a ritualistic meeting.
Question 3
"Technical debt is the sole concern of the development team". As a Scrum Master, do you agree with this statement? Whyor why not?.
Correct Answer:
As a Scrum Master, I donot agreewith the statement that technical debt is the sole concern of the Development Team. While Developers are responsible for recognizing and understanding technical debt, its impact extends far beyond the team and affectsagility, quality, and deliveryat the product and organizational level. First, technical debt directly influences a team'sability to remain agile. As technical debt accumulates, the cost and effort required to change the product increase. This slows down development, reduces predictability, and eventually makes it difficult-or even impossible-to deliver working software within reasonable timeframes. When agility is reduced, the entireorganizationsuffers, not just the Development Team. Second, technical debt has a significant impact onproduct quality and delivery. High levels of technical debt often lead to defects, instability, and integration problems. This undermines the Scrum principle of delivering a "Done" Increment each Sprint. When the product cannot be reliably delivered or inspected, customers and stakeholders are directly affected, making technical debt a shared concern. Third, while Developers are best positioned toidentify when technical debt occurs, addressing it requires collaboration across the Scrum Team. The Product Owner must understand that not all work in a Sprint will result in new functionality. Investing in reducing technical debt is an investment in future value, sustainability, and delivery capability. Stakeholders also need transparency about this trade-off. Fourth, Scrum encourages making technical debt visible andaddressing it continuously, rather than postponing it indefinitely. This may involve adding technical debt-related work to the Product Backlog and prioritizing it alongside functional work. Treating technical debt as "invisible" or purely technical undermines empiricism and long-term value creation.
Question 4
How the organization discusses and plans the work of creating software will be reflected in the implementation of that software. Technical systems can be decomposed to composite elements, from the large to the small. Basic components may be represented as activities, workflows, functions, features, capabilities, and other similar nomenclature. How does this system decomposition affect Scrum Teams on scaled projects?
Correct Answer:
How an organization discusses, plans, and decomposes work is inevitably reflected in the software it produces. When technical systems are decomposed into elements such as activities, workflows, functions, features, or components, these decomposition choices have adirect and systemic impact on Scrum Teams, especially inscaled Scrum environments. 1. Decomposition Influences Team Structure (Conway's Law) In scaled projects, system decomposition often drives how teams are formed. When work is decomposed along technical components or functions, organizations tend to createspecialist or component teams(e.g., front- end teams, back-end teams). This results in: * Increaseddependencies between teams, * More handoffs and coordination, * Reduced autonomy of individual teams. Scrum, however, expects teams to becross-functionaland capable of delivering usable Increments independently. Component-based decomposition therefore hinders effective Scrum adoption at scale. 2. Effect on Value Delivery and Transparency Scrum relies on frequent inspection ofintegrated, working product Increments. When decomposition focuses on small technical parts rather thanend-to-end features or capabilities, teams may deliver partial outputs instead of usable value. This negatively affects: * Transparency, as progress is reported through intermediate artifacts rather than working software, * Inspection, since stakeholders cannot meaningfully evaluate value, * Adaptation, because feedback is delayed until integration occurs. In scaled Scrum, this often results in "almost done" work that is not truly Done. 3. Feature-Oriented Decomposition Supports Scrum Scrum scales more effectively when system decomposition emphasizesvertical slices of value, such as features or capabilities, rather than horizontal technical layers. Feature-oriented decomposition enables: * Cross-functional teams, * Reduced dependencies, * Faster feedback cycles, * Independent delivery of value by each team. This approach aligns with Scrum's expectation that every Sprint produces ausable Increment. 4. Impact on Integration and Risk Decomposition decisions strongly affectintegration frequency. Poor decomposition increases integration complexity and encourages late integration, which raises risk and reduces learning. In Scrum-especially at scale-integration must happen early and often. Unintegrated work is not considered Done, and delayed integration undermines empiricism by hiding real system behavior until late in development. 5. Learning and System Optimization When Scrum Teams work on complete features rather than isolated components, they gain broader insight into: * Customer needs, * System-wide trade-offs, * End-to-end product behavior. This shared understanding improves decision-making and supportscontinuous improvement at the system level, rather than local optimization within silos.
Question 5
During a retrospective, one of the more junior developers confesses he has a hard time getting his opinion heard. Whendiscussing the work to be done, the more experienced developers often don't let him finish his sentences or disregard what hehas to say. What Scrum Values are touched upon here?
Correct Answer:
The situation described directly touches on several coreScrum Values, which guide behavior and collaboration within Scrum Teams. In particular, the values ofCourage, Respect, and Opennessare most prominently involved. First, the value ofCourageis 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 ofRespectin 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 ofOpennessis 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.
