![]() ![]() Retrospective sessions can prove to be effective only when members can collaborate effectively and share their ideas without any inhibitions. It should be ideally conducted in an atmosphere promoting trust and honesty. The Scrum retrospective is a very important Scrum event and should be taken seriously by all team members. Making the Scrum retrospective more effective The team asks three main questions to retrospect: ![]() The “inspect” and “adapt” principles play a key role in retrospective sessions. The main purpose of having a sprint retrospective meeting is to find what activities and “things” the team is doing well, what activities should be continued, and what “more” can be done to improve the development process. Retrospective sessions are attended by all – the product owner, scrum master, development team members, and even the stakeholders (if they so desire). Associated primarily with sprint cycles, the retrospective session is basically an “improvement” meeting held to find ways and means to identify potential pitfalls, past mistakes, and seek out new ways to avoid those mistakes. A Scrum retrospective meeting, known also as a sprint retrospective meeting, is held to assess the work carried out by the entire Agile team, and to identify what needs to be done further to improve upon the current Scrum process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |