SWOT Retrospective

The retrospective is an important meeting so I have been reading a lot about it and I found this amazing article about SWOT which is another way of doing the Retrospective.

http://www.emilianosoldipmp.info/2011/08/the-swot-an-innovative-tool-for-agile-retrospective/

 

SWOT images

 

 

 

 

 

What does SWOT mean?

The first quadrant contains the strengths (S): which attitudes, behaviors, approaches were good. The idea is to write what went well in the last iteration?

The second quadrant is a container of weaknesses (W): think of what has gone in the wrong way and analyze what is missing and where the problems were.
Think about the bad effect that was caused by the problem and try to conduct an analysis in order to climb to the root reason. Keep in mind the idea is no to talk about any team member in particular. Everybody did their best effort with the tools and knowledge at that time.

The third quadrant is dedicated for Opportunities (O) means the chances to improve (small steps that the team can do to keep with the strengthens or reducing the weakness).

Last but not least, the four quadrant is for Threats (T) which involves the risks for future sprints, they could be issues with a testing server, to get real data, a couple of guys on vacation or leaving the company.

After every team member has understood the “SWOT”, it is time for them to write on a white-board, flip-charts or sticky notes both the strengths (good things) and weaknesses (bad things) giving insights regarding the opportunities and threats that they can bring aboard.

After everyone wrote and put their post it on the whiteboard it will be the time to vote for each opportunity and decide what of them will be taken as part of improving as a team.

Nowadays, I would like to add a couple of items more to the action of improving such as who will be the man in charge to following the progress of each opportunity and set any date as a deadline.

To sum it up, the Scrum Master has to remember to the team that every improvement has to be done. On the other hand, it is better not to commit with something that could be too difficult or too big.

 

“if you want to learn more about agile retrospectives, subscribe to this program”

http://oikosofy.com/programs/agile-retrospectives

 

Share:
Mario Lucero

Mario Lucero

I am all about helping companies to adopt agile as methodology in Chile. Why? I believe many organizations think that agile is not for Chilean companies because of Chilean culture is totally different from i.e. USA culture but I worked with Chilean professionals who after using agile realized it is feasible to implement it. Agile works in small and large projects and there are many evidences which demonstrate this.

Leave a Reply

CommentLuv badge