A big part of doing retrospectives is not only for you as an individual but you as a team to improve on the next and every other project. That is a given, since this is a team effort. Now, every retrospective should have list of “action” items to work on for next sprint/project. An action list is basically a list that your team and you come up with to improve on that lacked or failed in the prior sprint.

So, what does making good team decisions have to do with action items? Well, as a team you should come to a consensus of what to place on the action list. Sounds easy at first but when practiced there can be a lot of mistakes that happen and teams become narrow-minded by focusing on small fixes that can take up time and energy and still places the team in a stagnant maybe even regression state. An example problem/challenge that could happen, this is directly from Doug Rose on Lynda, is “The first challenge is too much talk and not enough action. Sometimes this is called a kvetchrospective”.[1] Kvetchrospective is derived from the yiddish word Kevetch, which means “The first challenge is too much talk and not enough action. Sometimes this is called a kvetchrospective”[2] That’s why making good team decisions are really necessary, important and relevant.

This was only one of three challenge that most teams will face when trying to make a good team decision on what to add and work on the action items. Just remember the challenges that can happen and work hard with your team to avoid them and benefit from fixing the action items.


Cite error: <ref> tags exist, but no <references/> tag was found
Community content is available under CC-BY-SA unless otherwise noted.