Correct Answer:

TheCone of Uncertaintydescribes how the level of uncertainty in a product's requirements, technology, and value is highest at the beginning of a product's lifetime and gradually decreases as knowledge is gained. This concept strongly influences the type of work a development team performs throughout the product's development lifecycle and aligns well with Scrum's empirical approach.
Early Stage: High Uncertainty and Discovery Work
At the start of a product's development lifetime, manyunknownsexist. These may relate to customer needs, technical feasibility, usability, or business value. According to Scrum's empirical nature, teams should not assume certainty where it does not exist. Therefore, early development work focuses primarily ondiscovery.
During this stage, the Development Team works to reduce uncertainty by:
* Conducting research and experiments,
* Building prototypes or spikes,
* Testing assumptions with users,
* Validating technical and business hypotheses.
This type of work helps the team learn quickly and avoid premature commitment to detailed solutions. The goal is not maximizing feature output, butmaximizing learningand reducing risk.
Middle Stage: Reduced Uncertainty and Feature Development
As important unknowns are discovered and addressed, the Cone of Uncertainty narrows. The team gains confidence in what to build and how to build it. At this point, work increasingly shifts toward delivering functional stories and featuresthat provide direct value to users.
Development during this phase focuses on:
* Building usable, integrated product increments,
* Expanding functionality based on validated learning,
* Refining features through feedback and inspection.
Scrum supports this transition by enabling frequent inspection and adaptation through Sprints, ensuring that learning continues while value delivery accelerates.
Late Stage: Low Uncertainty and Operational Work
Toward the end of a product's development lifetime, most significant uncertainties have been resolved.
According toEvidence-Based Management (EBM),Unrealized Value becomes low, whileCurrent Value is high. At this stage, the volume of new feature development typically decreases.
The team's work becomes moreoperationalin nature, such as:
* Maintenance and optimization,
* Improving performance or stability,
* Addressing technical debt,
* Supporting existing users.
Investment decisions increasingly focus on sustaining value rather than discovering new opportunities.

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.

Correct Answer:

An example of unethical behaviour by a Development Team member in Scrum isknowingly delivering low- quality or non-secure softwarewhile being aware of the potential negative impact on users, stakeholders, or the organization. Such behaviour contradicts the ethical expectations embedded in Scrum and violates multiple Scrum Values.
For instance, a developer may intentionally ignore known defects, security vulnerabilities, or technical debt in order to finish work faster or appear more productive. Releasing software that is known to be insecure or unstable places end-users at risk and misrepresents the true state of the product. This underminesCommitment to quality andCourage, as the individual avoids addressing difficult issues or raising concerns.
Another unethical example iswithholding important informationfrom the Scrum Team or stakeholders. This may include hiding risks, downplaying impediments, or not being transparent about progress or challenges.
Such behaviour violatesOpennessand damages trust, which is essential for empiricism and effective collaboration.
Unethical behaviour may also be expressed throughfailing to support team members. For example, refusing to help others, dismissing or disrespecting colleagues' opinions, or working in ways that harm team cohesion contradicts the Scrum Value ofRespect. Scrum expects team members to collaborate and support each other in achieving the Sprint Goal.
Finally,going against agreements made by the Scrum Team, such as ignoring the Definition of Done or agreed working agreements, is unethical. This damages accountability and can mislead stakeholders about the quality and completeness of the work.

Correct Answer:

When a Product Owner raises concerns about the team's commitment and productivity based on comparisons ofvelocitywith other teams, this signals a need for coaching onempiricism, transparency, and appropriate use of Scrum metrics. As a Scrum Master, my response would focus on reframing the discussion fromoutput comparisontovalue delivery and continuous improvement.
First, I would explain thatvelocity 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 articulatewhat 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 ofempiricism 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 onScrum Values, particularlyRespect 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 inidentifying 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.