![\"\"](\"https:\/\/www.59secondsagile.com\/wp-content\/uploads\/2020\/04\/Scrum-Master-Banner-Introductory-Offer-1536x450-1-1024x300.gif\")
<\/a>How can we implement Continuous Improvement with the Retrospective Ceremonies? The Concept of a Retrospective ought to be familiar to anyone Working on an Agile Project. There have been several names over the years. These names explain this activity of Reviewing what happened throughout a Project, such as “post-mortem” or “lessons learnt”. Some may argue that these are not the same thing for a variety of reasons. However the inputs, discussions and actions arising out of such Meetings are Fundamentally the same.<\/p>\n\n\n\n
There are different adjectives one can hang in front of the word “Retrospective”, such as “Sprint”, “Release” or “Project”. This defines the Scope of what is to be Reviewed. Any Sprint Team member will have participated in a Sprint Retrospective, and knows its Value. At the end of a Project, the holding of a Project Retrospective is often perfunctory or omitted altogether. This often happens because the Team is being dissolved, now that the Project has actually finished. This is a serious oversight of a very Valuable tool for process improvement, not just for future Projects, but for the Company as a whole.<\/p>\n\n\n\n