🔴 Retrospective Examples for Fun & Effective Sprints

[@SunilKhiataniHK]

This is a great video that describes the essential components of a retrospective and why the retro is useful

[@ScrumMastered]

Thank you for watching!

[@shavonne4831]

Lovely and amazing input as always!

[@zadoksworld8905]

Daria is a great teacher

[@Solidini]

Hi Daria, great explainer video! One thought: a common challenge with retrospectives is that there's a big recency bias. What do you think of tools embedded in Jira (or whatever other system, but Jira is most widely used) that help users create notes for retrospectives while doing their work? This way feedback is collected at the right time and there's less of a bias when preparing for a retrospective.

[@ScrumMastered]

@Solidini, whatever tool works for the team is great. I think if your teams are using Slack, you can also have a retro ideas collection channel in there

[@berrysliwa1]

Thank you!

[@sorabhsood]

Thanks for the video

[@annaa4956]

Thanks a lot! Good tips

[@ashishjain3016]

Really admire the content around scrum, very useful, Thanks

[@ScrumMastered]

Glad to hear it!

[@Iseedstarz]

I think this is great

[@ScrumMastered]

Thanks! I glad you liked it.

[@NancyChanin-p1f]

Great video

[@ScrumMastered]

Thanks!

[@alebigna]

Great video!

[@jaychandwani2063]

She is amazing ❤️

[@sabrinacz]

1. Why you got together 7:00 2. Ice breaker 7:15

[@ibrahimsenan5273]

Thanks a lot for the great tips, I just have a question: After some time, retro meetings became more basic, the team got used to the method and the questions. I can feel some surface level answers. Is there a way(s) to make it more interactive, other techniques that can improve the retro meeting?

[@kseniiapavlova3715]

It might be not that simple. As advice, I'd start with figuring out what causes your team members to give basic answers. Is it really because of the format/techniques they have got used to? Or maybe there are some problems in the team or trust has deteriorated, and that's why they're not ready to 'go deeper'? Or maybe retrospectives don't lead to improvements, and team members aren't eager to participate because see little value. Or people are plain tired and overworked, they can't delve into deep and meaningful discussions. Or... whatever else. Once you have figured it out, then you can start solving the issue.

[@joannecastillo2355]

How should retrospectives change as the scrum team matures? I imagine that icebreakers are great for new team that are familiar with each other but needed less as the team works more together.

[@ScrumMastered]

I think that they become much more to the point. But it may also lead to the team getting a bit stuck and having trouble getting to new ideas, which will require some updates to how the retrospective is run