Who enjoys this activity?
14 replies (most recent on top)
Tired of agile, jira, confluence and scrum calls.
A daily scrum invite grinds my gears
Retrospective are great if you have a good Scrum Master that keeps them relevant & fresh combined with a team that hasn't had the life beaten out of them and they want to commit to making changes based on the retro. We have maybe 10 good Scrum Masters in the entire organization and we all know the will to live has been beaten out of most of us. So yes, by and large, the retros here are pointless and nothing more than a box checking event.
Not a Scrum Master here, but the retrospective could be useful if they were shorter and more structured. It's not a "feeling" session. Just talk facts and could be a short meeting. Speaking of short meetings - we have way too many long meetings here.
Almost forgot what retrospectives were all about. Agile is always evolving. So even if agile is over 20 years old there are new approaches. Now here is some bard AI on agile. BTW I see the scrum master and product owner roles being replaced by AI at some point in the future.
Yes, retrospectives are very important in the agile process. They are a chance for the team to reflect on what went well, what didn't go so well, and identify opportunities for improvement. This helps the team to continuously improve their processes and deliver better results.
There are no real alternatives to retrospectives, but there are different ways to run them. Some popular formats include:
Start, Stop, Continue: The team brainstorms things they want to start doing, stop doing, and continue doing.
Happy, Sad, Mad: The team shares things that went well, things that didn't go well, and things that made them angry.
Thank You, Sorry, Ask: The team members thank each other for things they did well, apologize for things they could have done better, and ask for help with things they are struggling with.
The best way to make retrospectives better is to make sure they are productive and engaging. This means:
Setting clear goals: The team should know what they are trying to achieve with the retrospective.
Inviting everyone to participate: Everyone should have a chance to share their thoughts and ideas.
Creating a safe space: The team should feel comfortable sharing their honest opinions.
Following up on action items: The team should make sure that the action items from the retrospective are actually implemented.
Retrospectives can be a valuable tool for agile teams. By taking the time to reflect on their work and identify areas for improvement, teams can continuously improve their processes and deliver better results.
Here are some additional tips for making retrospectives better:
Keep them short and to the point.
Use a variety of activities to keep things interesting.
Make sure everyone is involved.
Follow up on action items.
Celebrate successes.
Retrospectives can be a great way to improve team morale and productivity. By following these tips, you can make sure that your retrospectives are productive and effective.
What is a Jira Retrospective? Jira is a software product.
Jira is horrible
@xdk+1nFpdU1E everyone on the team provided feedback...it was our mgr that told us to live with it.......
@fuo - Scrum Masters don't have any say in whether or not the teams do retrospectives. It's the process they're required to follow. It would be like asking why developers like the bureaucracy and process around ServiceNow CRs. (They probably hate it like the rest of us.)
@fuo ITIL is also ancient but that's not stopping "modern" companies from going all-in on it.
Agile works but not so much in a bank setting.
I love them. Then again, I'm in a group that actually practices Agile. We actually change things based upon what we recognize is not going well. Crazy idea, right?
Provide such feedback if you want to see change. Keeping it to yourself and not speaking up will continue the behavior.
Our retro’s are a pretty positive experience. We’ve made some changes over the last few months to improve some processes that came out of it.
every question answered in discussion is shot down.... so why ask the team what we did well or what could we do better if in the end it doesn't matter?
People with the job title 'scrum master' like retro because they can mention that they had it in their next 1:1. It makes them sound busy.
It's a weird job title because these people are masters of nothing (just like most occupations, so I'm not being insulting here).
But the teams themselves find retro useless and awkward - drawing on virtual whiteboards instead of simply stating or typing your answer, etc. Retro is the most childish ritual of agile.
Side note friendly reminder: agile is over 20 years old. It's freaking ancient! The world of tech dev shouldn't be ancient. Agile was never genius, so it's weird that the tech world hasn't adopted a newer/different happy meal approach than agile in 20+ years.