If the team wants to speak openly and honestly about the iteration that just ended, having stakeholders present can be a hindrance.Īgile coaches (a “Scrum Master” in a Scrum Team) help the team identify good practices and possible improvements that can be used in the next iteration. Stakeholders can be invited to attend a retrospective meeting, but their presence is normally not necessary. This enables you to immediately apply what you have learned to the current project, instead of merely gathering these findings to use on some future project. With agile teams, this happens on a regular basis after each iteration – before the next iteration begins. Projects planned in the traditional manner generally have the project manager meeting with the team when the project has concluded to discuss what happened and the lessons learned. Retrospectives thereby differ from the Lessons Learned meetings used in traditional project management, especially with regard to the timing and frequency. Retrospectives promote the continual, iterative improvement of the processes in the current project. The retrospective is held at the end of an iteration, just as with the review. What remains are the aspects processes and teamwork – which the agile retrospective meetings are designed to address. It also benefits the further development of its functionality, thanks to the stakeholder feedback. The iteration review meetings or product review meetings with the stakeholders at the end of each iteration serve to evaluate and adapt the product. Three factors are analyzed and, if necessary, adapted: This gives you the opportunity to significantly influence the further course of your project. “Inspect & adapt” rituals are therefore a key ingredient of each iteration. These can be viewed as development cycles, but they also represent learning cycles because it is assumed that complex endeavors require a step-by-step approach in which it is necessary to frequently pause to evaluate oneself and the (intermediate) results. The basic concept of a retrospective is anchored in the 12th principle of the agile manifesto: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”Īgile teams work in preferably short intervals called iterations (called “Sprints” in Scrum). Let us get started! What Is an Agile Retrospective? Which formats are best for holding a retrospective?.How should a retrospective be organized?.This article covers the following topics: Such agile retrospectives aid the continual improvement of processes, methods, and teamwork. With agile retrospectives, you start thinking about the lessons learned and how to improve the collaboration even before the project is over – starting at the very beginning and continuing at regular intervals. As a project management expert, you know that: Lessons Learned meetings are an essential tool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |