-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sprint Review event process #31
Comments
Outworking of how such meeting potentially could go. Although it looks like this will be a presentation, it's definitely not. It's a working session with a standard structure of agenda points. 1: Welkomstdia Titel: Sprint Review "Is iedereen fris en fruitig?" Tijd om met iedereen op persoonlijk niveau te spreken. Bevordert de natuurlijke gespreksvoering en het geeft mensen de mogelijkheid om problemen (stres, thuis, vermoeidheid etc) kenbaar te maken. 2: Opnemen van de sessie Iedereen zijn consensus vragen. 3: Start en Agenda "Ik wil iedereen wederom welkom heten en bedanken voor de aanwezigheid bij deze Sprint Review van Sprint x. Het is vandaag 4 april en het is stipt 19.00 uur." Op de planning staat het volgende:
"Hierbij wil ik opnieuw benadrukken dat dit een werksessie betreft en niet zozeer een presentatie. Noteer belangrijke informatie, zodat dit niet verloren gaat. 4: Sprintdoeldia https://lucidspark.com/blog/how-to-write-effective-sprint-goals 5: Sprint Board Voorbereiding Uitvoering: : voortgang richting product doel dia |
You can see and comment on my initial meeting structure here: https://docs.google.com/presentation/d/1bFjnriO-lJahDbDI3hNSwznz0yLQm_AFKMiceIt7JcU/edit?usp=sharing |
Feedback from @MiKessels:
Some improvements we've discussed are:
|
One of the events of scrum is the "Sprint Review". We've already decided that we're going to schedule a meeting with our stakeholders to present the work that has been realised in the current sprint. We will be reviewing the work that we had originally planned and discuss the outcome with the stakeholders. This will probably lead to new feedback and requirements.
After the current sprint has been discussed, the product owner will prioritise tickets from the backlog, so it can be planned for the next sprint.
Edit: For now, we will skip this to see if we actually need this
I would like create a summary of each Sprint Review within a ticket, so we can easily go back into time and see what we've discussed in the meeting. This means that the information from the meeting needs to be processed.Acceptance criteria
Worked out details for the Sprint Review Summary ticket templateThe text was updated successfully, but these errors were encountered: