1/13/2024 0 Comments Sprint retrospective examples– What they are confused about: another important thing to know is what confuses people. This even makes it easier when you want to pitch a project to them or get help on something, you would probably know the best person to approach. – What they like to work on, specific projects, tasks, hobbies, and what they think of the work. Get to know your team better: from a PM’s perspective, one of the great things about doing retros is that it is a great way to get to know your team better. These meetings can be extremely important and really unearth certain things about projects, team dynamics, and work in general. This could be the good, the bad, or the ugly, but it is still important that the team, product manager, and scrum master know what the overall sentiment is. Individual and team expression: Another great reason to do a retrospective is that it allows the team to express themselves. We will see the specifics of this in the section below on – Why you should do it. Conducting retros helps you look for ways to learn from your past work and help make things go smoother in the future. One of the pillars of Agile is continuous improvement. Others think that taking 7 or 8 members of the team and sitting them in a room just to discuss the last couple of weeks of work is a real financial drain and a costly meeting. Some believe it is a waste of time and doesn’t bring value to the team. Some managers and other individuals are against doing retrospectives. We will explore both sides of the coin, but I can guarantee you that you should do them with your team as they will bring value. Sometimes, there are mixed feelings about doing retros. These three questions can come in different forms, but it all boils down to, “ what went well?” and “ what can we improve?” So, now that we know it’s a meeting to discuss past work and ways we can improve moving forward, what exactly is done in this meeting and how does it go? There are three major things covered in this meeting: What actions would you start what actions would you stop, and what actions would you continue doing. you allocate maybe an hour to an hour and a half to discuss work that was done in the sprint(s). This meeting is typically time-boxed e.g. Normally the last sprint we’re referring to is the last 1 week, 2 weeks, or 1 month of work. The goal is to self-inspect, identify improvement opportunities, and then create a plan on how to put that improvement into practice. If you aren’t familiar with agile, you must be wondering, what is a retrospective? A retrospective is a meeting where you get together with your development team to discuss the last sprint.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |