Why hold retrospectives if ideas don't get implemented?
From the Easy in theory, difficult in practice Blog
by Kiron Bondale
My musings on project management, project portfolio management and change management.
I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success.
This blog contains articles which I've previously written and published as well as new content.
Recent Posts
"It's the end. But the moment has been prepared for." - retirement lessons from the Doctor
Just because they are non-critical, doesn't mean they are not risky!
Just because they are non-critical, doesn't mean they are not risky!
How will YOU avoid these AI-related cognitive biases?
What won't change...
Categories
Agile,
Artificial Intelligence,
Career Development,
Change Management,
Decision Making,
Governance,
Hiring,
Kanban,
Personal Development,
PMO,
Portfolios (PPM),
Project Management,
Risk,
Risk Management,
Scheduling,
Team Building,
Time,
Tools
Date
I've written and spoken frequently about the many issues with holding infrequent lessons learned sessions. The good news is that many practitioners now recognize that it is much better to discuss and implement improvement ideas frequently over the life of their projects than just at the end of a phase or the project as a whole. This applies both to projects which follow a predictive life cycle as those following an adaptive one, with the main difference being the frequency at which such reviews occur.
Retrospectives are an integral part of the Scrum framework but conducting such reviews regularly is core to most flavors of agile.
However, that doesn't mean they are well performed.
To understand why, let's draw a parallel to project risk management.
Teams might do a reasonable job at identifying risks, assessing them and coming up with risk response recommendations for the higher priority ones. Unfortunately, often times those risk responses never get implemented. This might be the result of response owners not understanding how important it is to implement the responses in a timely manner, a lack of quality in the risk or risk response descriptions, a high tolerance for accepting risks, or just a generally low level of organizational project risk management maturity.
The same appears to be the case with retrospectives.
I ran a one week poll in PMI's Project, Program and Portfolio Management discussion group on LinkedIn soliciting feedback from the group members on what percentage of improvement ideas had actually been implemented from the last retrospective which had been held within their teams.
Of the 42 members who answered my poll, just under two thirds of them indicated that fewer than 25% of the improvement ideas were implemented. Not a single member indicated that over 75% of the ideas had been implemented.
There are many possible causes for this including:
- The team comes up with too many ideas and is unable to prioritize which should be implemented
- The team identifies issues but no ideas to address those issues
- The team lacks the psychological safety to run experiments to test the top ideas
- The system surrounding the team impedes their ability to implement ideas
- Most of the ideas fall outside the control of the team and they are unable to convince stakeholders to implement those ideas
Regardless of the cause, given how frequently retrospectives are conducted, if so few ideas are implemented, this is a significant waste of people's time.
Perhaps teams should being to apply the old agile cliché of "Stop starting, start finishing" to the improvement ideas...
Posted on: April 10, 2022 07:00 AM |
Permalink
Comments (5)
Please login or join to subscribe to this item
Luis Branco
CEO| Business Insight, Consultores de Gestão, Ldª
Carcavelos, Lisboa, Portugal
Dear Kiron
The topic that you brought to our reflection and debate was very interesting.
Thank you for sharing and for your poll results.
Holding retrospective meetings can be a practice extended to projects with hybrid and/or predictive development approaches.
We are in agreement. If they are just meetings to "throw away small talk", it is better not to hold them.
I liked the "old agile cliché of "Stop starting, start finishing" to the improvement ideas..."
Ronan O Rourke
Retired Executive Manager, Water & Drainage Operations| Retired
Bray, Ireland
Thanks for these reflections on lessons learned. I have found that Management think that the lessons learned are only going to be relevant if an identical project comes along and as this rarely/never happens they use this as an excuse for not implementing the lessons and then for not holding retrospectives
Michael Hilbert
Director of Project Management| TuWay Communications
Bethlehem, Pa, United States
Thank you Kiron.... Lessons Learned that are not implemented, are simply Lessons Observed.....
Thanks Luis, Michael & Ronan!
Kiron
Warren Simon
Program Manager| DoD
Baltimore, Md, United States
Great post! Lessons learned are so important, and yet so under-used.
Please Login/Register to leave a comment.
"One man alone can be pretty dumb sometimes, but for real bona fide stupidity there ain't nothing can beat teamwork."
- Mark Twain
|