The Demo for the Boss Review
What is it?
The Sprint Review becomes a formal, one-way event where the team presents only what has worked perfectly, often out of fear of criticism or negative feedback, losing the opportunity for inspection and adaptation.
Common symptoms (how does it manifest?)
- Only "perfect" work is shown, and problems are hidden.
- The team is nervous and fears negative feedback.
- Little or no real interaction with the Increment by stakeholders.
- Feedback is superficial or non-existent.
Impact and consequences (why is it a problem?)
- The crucial opportunity to get real feedback on the product is lost.
- The Product Backlog is not adapted based on learning.
- A false sense of progress is generated.
- Increased risk of building a product that does not meet needs.
Frequent root causes (why does it happen?)
- Organizational culture that punishes mistakes or "failure".
- Lack of trust between the team and stakeholders.
- The purpose of the Review is understood as an evaluation, not inspection and adaptation.
- Stakeholders who do not understand their active role in the Review.