Do Retrospective or Don’t Do Scrum at All

For those of you who have been learning Scrum must know that there are a couples of meeting in Scrum:
1. Sprint Planning Meeting
2. Daily Scrum
3. Sprint Review Meeting
4. Retrospective Meeting
Many have acknowledge that from number 1–3 are important, but few believe that the last one is important as well
This is totally disturbing because one of the keys in Scrum is continual improvement. But without this meeting facilitated, how can you improve? You will keep repeating the same mistake all over again.
I even can say that even without the first meeting, you will progress your project just fine with only just relying on the Retrospective?
How, you might ask?
Simple, try to do a Sprint, 2 weeks Sprint without any meeting but Retrospective in day 10. When doing that, ask them the following basic question in Retrospective:
1. What worked?
2. What didn’t work?
3. What should we try in the next sprint?
Now, there are a lot of responses that come out during this event but I am sure these comments must exist:
1. “We didn’t have a clear goal and plan what we want to reach in this Sprint. Somehow, there are a lot of request but we don’t have a say whether or not we can do it(solvable with Sprint Planning)
2. “There are no communication between programmers. Sometimes, I even find myself working on the same task with my peers. There are also many obstacles in doing this task but I find it difficult to deal with it(solvable with Daily Scrum)
3. “I don’t know the progress of our current project. Sometimes, I even don’t know whether the task I finish is correct or not(solvable with Sprint Review)
4. And many other problems that persisted during Sprint
You see, there are a lot of problems we can solve by using Retrospective. You might say that if they had already implemented Scrum’s supposed meetings from day 1, These wouldn’t have happened. But how many times people try to reject all of these meetings because they think all of these meetings are not important and just waste of time. By introducing pain and trouble, it will encourage them to search the solution and when they consider the meetings as a solution, they will easily and gladly embrace it
Imagine if you just did the Scrum process and abandon Retrospective in the end. You might find problems and difficulty in implementing Scrum in your organization but you don’t spare time to just hold a meeting to solve them. Eventually, you will just consider Scrum not fit in your organization because of one or two problems. A shame that it can be avoided if they just want to do retrospective
In conclusion, Retrospective is the most important meeting you need to do if you want to implement Scrum in your organization. It solves and gives team a chance to express their happiness, discontent, and suggestion to make the process better. Without Retrospective, team will not be facilitated to improve and keep repeating the same mistake all over again. Eventually, the management will just say that Scrum is not for their organization, just revert to the dark age, where everything is controlled by management
font-famil����G
