If I had to point an event that most scrum teams run away from is this one. Some don’t even do it.
I was a developer and I remember the feeling. The item is not, but its not perfect, if I just had 30 more minutes. Let us not show it now now, let us do it next week. But then next week it would be something else.
Team should be proud to show both their success and their failures. The team worked a full iteration on a couple of items, show them with pride. Let everyone know what you worked on, and most importantly, get feedback and learn from it.
It is only a failure if you learn nothing from it
Scrum is a collaborative process that requires the stakeholders to work with the team. Without interaction with the key stakeholders, the communication line is broken, it always needs to pass via the P.O.
You can say as much as you want, that’s his/her job, but at the end of the day, P.O’s are also human, and they commit mistakes. They forget things. Or they misinterpret things because they don’t have the technical knowledge.
Nothings of this are malicious, it just happens. Refusing to accept it will not change it.
So what we can do? Do the sprint review.
Bring the key stakeholders to the table with the developers.
Start creating rapport and relationship between them.
Coach the stakeholders that this does not mean that now they should contact the developers directly.
Coach the developers that they should not accept requests from the stakeholders directly.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.agilemanifesto.org