Project Management Central

Please login or join to subscribe to this thread

Topics: Agile, IT Project Management, Scrum
How do you handle sprint retrospective meetings in Scrum?
Network:268



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:
Network:11



I am definitely not an expert. I took over a high profile complex scrum effort and found it best to separate team building from retrospective. I used games in my team building meetings which I held monthly and utilized our retrospective meetings at the end of each sprint for coming up with improvements in our approach. The main reason was just the balance of time. We had 4-7 team members that also had assignments outside our scrum development effort as well as the need to conduct meetings for user story refinement for the sprint that usually took an hour and half as well. I am interested in hearing what others do.
...
1 reply by Clemens Bauer
Feb 17, 2018 11:02 AM
Clemens Bauer
...
Thanks for your input.
Network:98570



I tend to agree with Sally's point of view - I'd rather follow a certain agenda to at least address the main things and then probably can do one or two games to see how team work and collaboration works.

The retrospective is the main meeting for the team themselves to inspect and adapt.
...
1 reply by Clemens Bauer
Feb 17, 2018 11:04 AM
Clemens Bauer
...
Thanks for sharing your oppinion.
Network:1944



Retrospectives ideally would be a dynamic process through trial & error and adapting as the team grows. Starting from a generic format, then modifying as needed. It's a natural process.
...
1 reply by Clemens Bauer
Feb 17, 2018 11:04 AM
Clemens Bauer
...
Thanks for your input.
Network:1017



Clemens -

Inspect & adapt should be the mantra for all agile teams.

What this means is that while you might start with a very standard approach to your retrospectives (while at the "Shu" level of agile maturity), after a few sprints, the team should consider doing a retrospective on their retrospectives to find out if there are better ways to gain value from the ceremony (moving to the "Ha" level).

This is where some teams might alter the approach taken to elicit high value outcomes. I've seen games used, creative materials (e.g. Playdoh, Lego) and other approaches to help teams shake off the rust of using the same approach sprint after sprint.

Kiron
...
1 reply by Clemens Bauer
Feb 17, 2018 11:05 AM
Clemens Bauer
...
Thanks for sharing your perspecitve. How do you use Lego in such meeting?
Network:268



Feb 16, 2018 10:59 AM
Replying to Sally Wolfe
...
I am definitely not an expert. I took over a high profile complex scrum effort and found it best to separate team building from retrospective. I used games in my team building meetings which I held monthly and utilized our retrospective meetings at the end of each sprint for coming up with improvements in our approach. The main reason was just the balance of time. We had 4-7 team members that also had assignments outside our scrum development effort as well as the need to conduct meetings for user story refinement for the sprint that usually took an hour and half as well. I am interested in hearing what others do.
Thanks for your input.
Network:268



Feb 16, 2018 11:32 AM
Replying to Rami Kaibni
...
I tend to agree with Sally's point of view - I'd rather follow a certain agenda to at least address the main things and then probably can do one or two games to see how team work and collaboration works.

The retrospective is the main meeting for the team themselves to inspect and adapt.
Thanks for sharing your oppinion.
Network:268



Feb 16, 2018 12:27 PM
Replying to Andrew Craig
...
Retrospectives ideally would be a dynamic process through trial & error and adapting as the team grows. Starting from a generic format, then modifying as needed. It's a natural process.
Thanks for your input.
Network:268



Feb 16, 2018 3:06 PM
Replying to Kiron Bondale
...
Clemens -

Inspect & adapt should be the mantra for all agile teams.

What this means is that while you might start with a very standard approach to your retrospectives (while at the "Shu" level of agile maturity), after a few sprints, the team should consider doing a retrospective on their retrospectives to find out if there are better ways to gain value from the ceremony (moving to the "Ha" level).

This is where some teams might alter the approach taken to elicit high value outcomes. I've seen games used, creative materials (e.g. Playdoh, Lego) and other approaches to help teams shake off the rust of using the same approach sprint after sprint.

Kiron
Thanks for sharing your perspecitve. How do you use Lego in such meeting?

Please login or join to reply

Content ID:
ADVERTISEMENTS

Work like you don't need the money, love like you've never been hurt, and dance like there's nobody watching.

ADVERTISEMENT

Sponsors