Project Management

Please login or join to subscribe to this thread

How do you handle sprint retrospective meetings in Scrum?

linkedin twitter facebook   Agile   Information Technology   Scrum  
avatar
Clemens Bauer CEO| Think3 Consulting GmbH Graz, Austria
Since our company moved to scrum development (two weeks sprints), we also do regular sprint retrospective meetings (approx 1 1/2h) to figure out what the team did well, what needs to be improved or what was not that good? However, our scrum master does in a game like way. Therefore, he prepares games for each meeting in order to make the retrospective more fun.
How are you doing retrospective meetings? Do there exist some best pratice examples? Do there exist better and efficient ways of doing that?
Sort By:
< 1 2 >
avatar
Thomas Walenta Global Project Economy Expert Hackenheim, Germany
Clemens,

team building and continuous improvement should not be restricted to meetings. If you deem meetings appropriate for these purposes and maybe be others, make sure the team appreciates them too.

Games can be included in any kind of meetings and even day2day activities, if they serve the purpose to enable collaboration and trust. Kanban, estimating or OKRs are also kind of games
(for a good overview of gaming techniques, see octalysis).

Yet many games are not suited for all people and teams, and like Sergio, I do not like them, especially if they are artificially imposed. The Scrum Master could be inexperienced and use tools that were taught to him, but in inappropriate settings.
avatar
Latha Thamma reddi Sr Product and Portfolio Management (Automation Innovation)| DXC Technology Mckinney, Tx, United States
Thank You!.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

ADVERTISEMENT

Sponsors