We’ll soon be launching a collection of new features aimed at helping companies use and support Retrium across their company. We call it Retrium Organizations.
Our mission for Retrium has always been to create a retrospective product that’s easy to use and provides a safe place for teams to discuss learnings, issues, and anything else that needs to be addressed. We’ve taken the feedback you’ve shared with us to guide the evolution of Retrium, which balances usability and psychological safety with power and visibility.
What we will accomplish with organizations is the same great product you love for team retrospectives, now with better visibility across your company, simpler permissions, and easier access to team rooms for all.
We share tips and best practices for retrospectives because we're passionate about helping teams continuously improve. We are always excited to hear about how incorporating these tips has helped you improve your retrospectives. So you can only imagine how excited we were to hear we'd been recognized as #33 on the list of 100 Top Agile Blogs by Luis Goncalves!
Effective brainstorming is critical in a retrospective. It is the very first thing you do during your retrospectives and serves as the foundation for the discussions that follow. So it’s not unexpected that I’m regularly asked how to have more engaging and effective brainstorm sessions.
Since our first call for input by way of the survey, we've received a lot of feedback on the Annual Agile Retrospectives Report, or AARR as we've started referring to it at Retrium. We've heard from some folks that there are additional topics that we should be covering; others want to see the survey broken into different sections. Regardless, there is one common theme in the response we've received in our feedback - it's about time!
While the response we've received has already exceeded our expectations, we decided to extend the deadline to this Friday, May 12 to gather as much feedback as possible. Click here to take the survey now.
You're facilitating a retrospective. You're creating action items to ensure the team walks away with tasks to help us improve. But a simple question reveals there are different interpretations to the same discussion and action item. Sound familiar?
There are several quotes that have stuck with me about agile retrospectives. These range from the importance of retrospectives as the real catalyst for continuous improvement in scrum to the fact that people struggle with holding effective retrospectives so much that the decision is often made to no longer have retrospectives. And the challenges teams face in retrospectives are just as varied.
Ever finish a meeting and ask yourself, "So what did we accomplish in that meeting, anyway?"
To be vulnerable is to expose yourself. In other words, increasing your vulnerability makes you more susceptible to being hurt.