virginiatore.blogg.se - Retrospective meeting agenda

#RETROSPECTIVE MEETING AGENDA HOW TO#

Whatever it is, make sure that you’re encouraging recognition amongst the team!ħ. Did someone bring in donuts to the office?.Who doesn’t love a little recognition? Open up the floor for the team to give each other praise.

#RETROSPECTIVE MEETING AGENDA HOW TO#

Think about the things that can affect the future success of your team and start proactively planning out how to overcome them. This time, focus on anything that the team should be aware of or look out for in the future. Once again, open this question up to the entire team. Things to look out for in the future? (5 min) Use this information to improve processes, understand the frustrations of the team, or learn about any blockers that slowed someone down.ĥ. Go around the room again and ask the team to share some things that could have gone better.

Were the lines of communication more open?.

Did the team’s burndown chart look great compared to past sprints?.

Were the story points assigned to each task accurate?.

Was the handoff from marketing to sales more seamless this past sprint?.

Go around the room and have everyone share what they thought went well for them this sprint.

Is there anything that needs to be refined?.

Does the work that was presented meet acceptance criteria and user stories?.

During this time, you’ll want to answer two questions: This is when the team will review what’s been demoed, share feedback, and create next steps for actioning on suggestions. Product acceptance and change requests (10 min)

It’s also a great time for the team to share recognition and feedback with one another on things being demoed.Ģ. So, starting with demos is a great way to start off this meeting. For other teams, maybe the baseline is to demo anything that was shipped and is customer-facing.įor many, this is a super exciting meeting because people are proud of the work that they put in and want to share that with the team. Depending on how long your sprints are, try to set a baseline for criteria on things you can demo so that it’s not showcasing the same thing over and over again.įor example, if you’re a team that wants to see anything and everything, then set your guidelines to be anything that was worked on during the sprint. Whether it was fixing up some UX things on the product, building a brand new feature, or launching a campaign, give people the opportunity to showcase their work. Kick off the meeting by having the team demo the work they did during the sprint.