Agile Software Development, Scrum, Extreme Programing, XP, Test Driven Development, TDD, Feature Driven Development, FDD, Lean, DSDM, Behavior Driven Development, BDD, Refactoring, Pair Programming, Kanban
 

Common Mistakes in Scrum Sprint Review Meetings

Many Scrum teams make the mistake of using the Sprint Review meeting for feedback from the Product Owner to the development team. Then the Sprint Review becomes a kind of ‘acceptance’ event. The Sprint Review meeting is, however, not intended for acceptance by the Product Owner.

It should primarily be used as a meeting in which feedback from stakeholders is collected on the product and the product backlog. The Sprint Review is not the meeting FOR the Product Owner, but it is the meeting BY the Product Owner. In this meeting, the Product Owner exposes the results and plans to his/her stakeholders and gets (with the team present!) specific feedback on the software and the current product backlog. And that’s good. Because the sooner you get feedback, the faster you will be.

[youtube -IrkeDIQq-M]

Video Producer: http://www.rinivansolingen.com/