Everything is Clearer in Retrospectives
"No system will make us effective if we aren't in the habit of reviewing our performance and adjusting our actions based on what we have learned."
- PragmaFlow
Why are We Focusing on Retrospectives?
Retros are one of the key project team ceremonies. Retros provide a time when lessons can be interpreted and adjustments can be decided on.
Retros provide a guaranteed opportunity to address issues and areas of improvement. While they're not the only time this can or should happen, they do act as a forcing function.
As a plus, issues that occur tend to take on a less threatening form because we know that we have a mechanism in place for dealing with them.
DPM adds that a retrospective offer the following benefits:
- It creates a safe, blameless space for team members to share their valuable feedback.
- It allows the team to document wins and areas of opportunity.
- It identifies small, incremental changes that can lead to larger waves of improvement.
- It allows teams to iterate on their process to amplify results.
- It allows opinions to be heard.
- It helps the team mature.
- It makes each sprint better than the last.
What to expect?
During the first session, we'll each do a quick intro:
- who we are
- what we do
- what we're hoping to achieve
After that we'll each move through each agenda item
- What went well
- What did not
- What we learned
- What we will adjust
Among this group there is a wide range of professions from freelancers to team managers, this means you’ll benefit from a multitude of different perspectives.
The Retro Space
In order to make sure that all of the above can happen, there are a few guidelines to follow:
- The retro space is a safe space, this means that candor is valuable and appreciated. Speak your truth, during your turn or when solicited, of course.
- It also means that we listen impartially to the feedback of others.
- So much of communication is non-verbal and so cameras on is a must.
- The 2-ears 1-mouth concept applies here. We'll all get to speak but listening is magical. We definitely want to use 'how' and 'what' questions to gain understanding of others' perspectives before we give feedback.
- At some point you may feel defensive, that's totally ok; It's probably best to own it and shake it off.
Who are we and why are we sharing this?
Over the last decade and a half, I’ve worn many hats in the design, coaching, sales, marketing, and productivity fields.
Steven comes with with 20 years of experience as a developer, designer, IT and security professional, and team leader.
We've designed:
- Software
- Hardware
- Graphics
- Functional apps
- Products
- Business channels
- …and then some.
We focus on helping both leaders and creators get results.
Why?
We've worked with amazing team, and we’ve worked with horrible teams. We want all of you to be part of amazing teams.
After all you are the ones that create the products we use, lead the teams we work with, write the blog posts we read, and create the music we listen to; when these creations are amazing, everyone wins.
As this is a test program that we're piloting with you awesome people, the first group sessions we are setting up with be cost-free.
If successful, the larger program may become a paid membership group (it also may not). If it does, know that you will be part of the conversation, you'll have meaningfully advanced notice, and that we'll make sure you feel respected and appreciated as our early pioneers.
If there are more people interested in the program than the 3 free sessions we are launching as part of this test, we may offer a paid option right away to better accommodate everyone.
Ending Thoughts
"Agile [...] represents a radical transformation of methods of thinking—a basic change in the way firms try to arrive at the truth of what will work and what won’t, of what will get results and what won’t."
- Forbes
