![]() The continuous improvement process leads to better value for customer.Motivate the team to find solutions to their problems.Improvements can be quickly included into the process. Teams learn from mistakes and collaborate together to improve future sprints.The retrospective begins with a team meeting to discuss what worked we. Retrospective meetings typically consist of data gathering, data analysis, and action items (areas of improvement for the next sprint). A Release Retrospective is a critical event because it captures all the lessons learned and improvements made during the project. The goal of the retrospective is to focus on specific actions the team can take towards their goal of continuous improvement (Kaizen) and not to conduct an extensive post-mortem. The Scrum team holds a retrospective meeting at the end of each iteration to briefly analyze this last sprint and identify one or two improvement ideas for the team to address in the next sprint. A retro meetings primary purpose is to help everyone develop their workflow by using objective team feedback as a tool. This retro happens at the end of the meeting. A retrospective in Scrum is a meeting after the completion of a sprint in order to discuss whether the sprint was successful and to identify areas of improvement for the next sprints. The second is slightly less common: retrospectives at company-wide meetings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |