Agile Project Management - Confession 4: Stand-Up Versus Sprint Review

The transcript discusses a team's experience with Scrum meetings, focusing on the anxiety surrounding the Sprint Review due to incomplete data and stakeholder expectations. The project aimed to create an engaging news website, but faced challenges with test data. Leadership dynamics, particularly John's influence, affected team morale. The Scrum Master emphasized the importance of stand-up meetings despite team resistance. After the Sprint Review, reflections highlighted the need for better preparation and communication. Lessons learned included ensuring code is shippable, using live data, and addressing team tensions.

What were the main causes of anxiety for the team before the Sprint Review meeting?

How did John influence the team's perception of the Sprint Review?

What strategies did the scrum master consider to maintain the stand-up meeting despite the team's reluctance?

How did the team feel after the Sprint Review, and what was the scrum master's reflection on the event?

What lessons did the scrum master learn regarding the preparation for the Sprint Review?

What could have been done differently to reduce tension before the Sprint Review?

What role does live or as-live test data play in preparing for a Sprint Review?