Lot of teams don’t give Sprint Retrospective (hereon referred as SR) the time and effort it deserves. We’re so focussed on running the sprint on schedule and doing other sprint activities that SR takes a back seat.
Since SR involves only the team and not the Product Owner. May be that’s why teams tend to take it lightly. Often postponing (or rescheduling) it or skipping it every other sprint. This happens despite teams recognizing the importance of SR!
Often team members don’t have anything to contribute during a SR. And it tends to get boring when people don’t feel they’re contributing or involved. There are of course learnings in every sprint, but if the team was too busy working, they’d probably not recognize the learnings and may not remember them by the time SR happens.
You need the learning/issues from the sprint do be available during SR for it be effective. I like to make notes during the sprint about anything out of the ordinary. An unexpected technical issue, clarifications about any requirement, unexpected meetings etc. Any little thing that we didn’t anticipate.
These little notes serve as pointers for the SR. Each team member can make such notes throughout the sprint when they observe anything amiss or have any idea that can help the team. We tend to forget these things over time and they don’t get discussed on SR. Hence its good to note them as and when they occur. A sprint dairy, if you will!
Lot of these issues may have been reported during daily scrum meetings. The ScrumMaster can add them to his notes after the daily scrum meeting.
Everyone’s notes will help immensely in SR and make it more effective and fruitful for the team. As a bonus, why not start the SR with a small treat to celebrate the sprint gone by (everyone likes ice creams!). Everyone’s worked hard during the sprint and a small treat wouldn’t hurt!
Loading ...
Retrospect – This step, I feel, is very important in whichever sphere, to choose the way ahead consciously.
>>This happens despite teams recognizing the importance of SR!
very true! Just knowing the importance of something might not always add all the value.
May be the team(s) should have to calculate the degree of loss caused/might cause by missing SR. I believe this would add that missing extra sparkle charm to SR.
>>You need the learning/issues from the sprint do be available during SR for it be effective.
Correct.
But once learnt and understood, the excitement about a learnt ascpect is gone [for the member]. And hence the learnt issues just slips off from the active window in mind. Unfortunately, this is often way too early to SR meet. So, preparing notes should be done immediately or way before the excitement is lost. The member should understand the fact that the learning can be of value to the rest of the team as well. This kind of realization also might help the team(s) mentally set to NOT neglect the SR and prepating notes for the same.
Oops! too big to be an article!
No wonder, that important I feel is SR!!
nice article…
Thanks for the article. It was a value addition to my knowledge.
Useful tips for development projects.