In Scrum, what value is demonstrated when a Developer refuses to implement an unplanned feature requested by a stakeholder?

When a Developer refuses to implement an unplanned feature requested by a stakeholder, this action demonstrates courage. In Scrum, the role of the Developer includes maintaining the integrity of the Definition of Done and the commitment to delivering valuable and potentially releasable increments of software.

By standing firm against implementing features that were not part of the agreed-upon plan, the Developer shows the courage to prioritize the team's focus on delivering the work that has been committed to in the Sprint. This also involves having the confidence to engage in difficult conversations with stakeholders, expressing the reasoning behind their decision, and protecting the team from scope creep that could undermine the Sprint goal. The Developer takes a stance for what is best for the team and the product, which is a crucial aspect of being effective in a Scrum environment.

This action not only supports the Scrum values but also fosters an environment where the team can focus on the work that adds the most value, rather than being distracted by every new request that comes their way.