https://retrospectivewiki.org/api.php?action=feedcontributions&user=Niraj+Patel&feedformat=atomAgile Retrospective Resource Wiki - User contributions [en-gb]2024-03-28T22:16:36ZUser contributionsMediaWiki 1.35.1https://retrospectivewiki.org/index.php?title=Tips_%26_tricks&diff=693Tips & tricks2015-03-31T16:15:55Z<p>Niraj Patel: </p>
<hr />
<div>Add any simple tips you have for improving retrospectives. Can be generated by running a [[Retrospective Surgery]].<br />
<br />
*Split into small groups to narrow down actions (helps with large teams or with quiet members)<br />
*Use a space without a table<br />
*Have a backlog of retrospective actions with done / not done next to them<br />
*Write the output on a flip chart and stick it up in the workspace where all can see<br />
*Location, location, location - find a good spaces and mix it up so not always in same place<br />
*Write up the retrospective output including actions and put on a blog/wiki or send round in an email<br />
*Forward-specting - what can we start doing now<br />
*Do a 'warm up' exercise to break down any tension and get people in the mood (see below)<br />
*Food (especially nice food like cakes & biscuits) is an excellent way to make the session more appealing and is a great leveller.<br />
*Use a facilitator from outside the team (e.g. another team's scrum master)<br />
*Swap the facilitation role within the team: don't let it fall to the same person (coach, scrum master) each time<br />
*Plan your retrospectives - don't just turn up and run it the same way each time. Develop a [http://www.benlinders.com/2013/have-a-toolbox-of-retrospective-techniques/ toolbox with exercises].<br />
*Throw away everything from the retrospective except the retrospective actions. Focus on outcomes, not problems.<br />
*Create awareness for [http://www.benlinders.com/2013/retrospective-benefits-power-to-the-team/ Retrospective Benefits]<br />
<br />
<br />
----<br />
'''Warmup Exercise - Sprint Draw & Guess'''<br />
<br />
A fun 10 minute warmup. I don't know the source of this, so am happy to be corrected.<br />
<br />
Ingredients:<br />
*X index cards per team member, where X is the total number of people within the dev team<br />
*Sharpies or pens<br />
*A pair of phones to use as countdown timers<br />
<br />
Method:<br />
*Give each person index cards and a sharpie/pen<br />
*Each person should write 1 to X in the top left corner of the index cards, front to back<br />
*If team size is even, each person has 1 minute to draw (without using words) how they felt the previous sprint went<br />
*If team size is odd, each person has 30 seconds to write down in words how they felt about the previous sprint<br />
*On completion, place the card at the back of the stack and pass it to the right<br />
*The next person, looking only at the last card at the back, attempts to interpret it <br />
**If they see a drawing, attempt to write down what it represents<br />
**If they see text, draw it<br />
*Facilitator should keep time - 1 min for drawing and 30 seconds for writing<br />
**Everyone should be doing the same thing<br />
*Keep going around until you write or draw on the last card<br />
*Once complete, lay them all out in order<br />
*Enjoy comparing the interpretations<br />
*Leave the index cards out during the rest of the retrospective, as a visual aid to whatever activity you have planned<br />
** Alternatively, if the activity planned requires index cards, just flip them over and reuse<br />
<br />
Sounds silly, but is rather great in lightening the mood.</div>Niraj Patelhttps://retrospectivewiki.org/index.php?title=User:Niraj_Patel&diff=692User:Niraj Patel2015-03-31T16:00:48Z<p>Niraj Patel: </p>
<hr />
<div>Developer at [http://www.masabi.com/ Masabi].</div>Niraj Patel