Essay --

Some supple groups hold a ex post facto meeting once a week along with their daily ensure stand-up meetings. It is called stand-up because the meeting is essentially conducted with all the team members standing. The bunsonical idea behind this is to keep the meeting as short as possible typically 15 minutes or lesser. During this meeting the team members discuss around the status of the project and the issues that they are facing. The weekly retroactive would help in identifying any process changes that are required immediately. As the completion time for the dash nears, the time taken to discuss about process improvement for the current sprint decreases as improvements for the ongoing sprint has been discussed in the everyday stand-up meeting. This results in a better parcel product as the team is continuously working on upward(a) its knowledge management process.Each retro has both qualitative and three-figure aspects. The qualitative part discusses the various team p ractices and the success of for each one. It also comprises the item challenges that presented themselves during the iteration. Upon identification of the issues, root cause analysis is performed and potential corrective actions are discussed and recorded. The quantitative review gathers and reviews any metrics the team is using to footmark its performance.PurposeAn iteration retrospective is a reflective process. The iteration retrospective enables the team to reflect on the iteration just completed and guess new ideas for process improvement. This helps instill the spirit of continuous improvement or kaizen mind in the individuals and the team, and helps assure every iteration makes some gnomish improvements in the processes. The Scrum Master plays an import... ...s an insight into the project from the perspective of each team member and make them realize that its the team that can make the change.A qualitative study can be make among companies employing the agile methodolo gy about the in force(p)ness of the retrospective process. Interviews can be conducted with the scrum masters and certain important people within the team to elicit what kind of improvements they have seen in their projects due to the action items suggested in retrospective meetings. A major challenge facing most agile teams is how to keep the retrospective meetings fresh. A comparative study can be done among agile teams about the various retrospective techniques that they employ and how effective and interesting these techniques. This would give an insight into a plethora of ideas on conducting a retrospective that will never become boring and redundant.