A Development Team is consistently under pressure from middle management to provide detailed, fixed-date estimates for features that are still vaguely defined in the Product Backlog. This conflicts with Scrum's empirical nature and leads to frustration within the team. The Scrum Master observes this recurring pattern. Which Scrum Master stance is most effective in addressing this conflict?
- AServant Leader, by taking on the responsibility of creating detailed estimates for management to relieve pressure on the team.
- BCoach, by helping the Development Team find ways to quickly provide 'gut-feel' estimates to management to satisfy their requests temporarily.
- CTeacher, by explaining to middle management the principles of empiricism, the cone of uncertainty, and the futility of fixed-date estimates for poorly defined work.
- DImpediment Remover, by simply refusing to provide any estimates to management, thereby shielding the team.
Show answer & explanationAnswer & explanation
Correct answer: C. Teacher, by explaining to middle management the principles of empiricism, the cone of uncertainty, and the futility of fixed-date estimates for poorly defined work.
The core problem is a misunderstanding by middle management of Scrum's empirical process and the realities of software estimation. As a Teacher, the Scrum Master needs to educate management on these principles, explaining why fixed-date estimates for vague work are counterproductive and how Scrum's approach provides better predictability through inspection and adaptation.
Why the other options are wrong
- A. Creating estimates for the team undermines their self-organization and accountability, and doesn't solve the systemic issue of management's unrealistic expectations.
- B. Temporarily satisfying requests with 'gut-feel' estimates doesn't educate management or change their expectations, potentially leading to more frustration later when those estimates prove inaccurate.
- D. While shielding the team is part of being a Servant Leader, simply refusing without explanation doesn't address the underlying management expectation or educate them.
Scrum Master as Organizational Teacher
The Scrum Master educates the entire organization, including management, on how to interact with Scrum Teams, understanding Agile principles, and fostering an empirical mindset.
- Educates management on Scrum.
- Explains empirical process control.
- Helps align organizational expectations.
Memory trick: The Teacher illuminates the path for the entire organization, especially management.