agree on their prioritisation among the team before the are fed back into the backlog. Rotate on retrospective formats among the multiple available, to collect different aspects and engage more with the people.Īsk different participants to playback the different topics.Įnsure everyone has a chance to contribute.Įnsure improvement actions are tracked and monitored: Use a virtual whiteboarding tool or another tool that suits the purpose. This event can be completed quite easily remotely. Changing a Retro location to a Cafe, pub or even using techniques such as the walking retro can help to drive out different problems/issues that might not have come up otherwise Locations can play a major role in the outcome of a Retrospective. They can be broad and encompass multiple issues and problems, or with the teams permission can drill down into specific issues using techniques such as the 5 whys. Retro's are within reason whatever a team needs to be. Ensure you track them and raise them to the relevant owners but value can rarely be found in a one hour ranting session. White-board pens if using a white board or MagicWhiteboard paperīe careful not to dwell too heavily on things outside of the teams control. Typical materials used during facilitation include: There are lots of different formats retrospectives can take (see the references for links to some excellent resources which provide ideas). We recommend allowing 30-60 minutes for a one week sprint retrospective. Varies based on the duration of the time period the retrospective is covering.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |