Any right way of doing Agile retrospective meeting?

There is no TRUE way of doing retrospectives. Teams are different in motivation, competence, culture and size. What works for you, might be ineffective in my context. 

For me, the key indicator of good retrospective - developed action plan to improve process. How you get there is not as relevant

Comments

  1. Ben LindersOctober 19, 2014 at 10:07 AM

    Fully agree that teams and situations differ.

    There is a book that Luis Gonçalves and I wrote with Retrospective exercises: http://bit.ly/RetroValue. Nest to the exercises it also helps you to come to actions that are valuable for the team.

    ReplyDelete

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more