As a seasoned Technical Project Manager, I approve this message. ;)
Retrospectives, as it is called in Agile, is one of the most important ceremonies to conduct at the end of an iteration (sprint). If neglected, productivity on the following sprints greatly suffers.
I have found it especially effective to have each team member independently write out what went well, didn't go well and could have been done better, then categorize, vote to discuss, then discuss. A note taker writes down separate action items that surface during discussion, ending with votes to accept or strike them.
Tasks are created and added to the backlog for consideration in a following iteration.
As a seasoned Technical Project Manager, I approve this message. ;)
Retrospectives, as it is called in Agile, is one of the most important ceremonies to conduct at the end of an iteration (sprint). If neglected, productivity on the following sprints greatly suffers.
I have found it especially effective to have each team member independently write out what went well, didn't go well and could have been done better, then categorize, vote to discuss, then discuss. A note taker writes down separate action items that surface during discussion, ending with votes to accept or strike them.
Tasks are created and added to the backlog for consideration in a following iteration.
Love the idea of having people do it independently then moving to a group setting. I'm sure you get some more unvarnished feedback that way.
Yes, that is the intention. 😉
And it works!