Merge the Sprint Review & Retrospective to a single meeting
Let teams decide how much time that they spend on each one.
Martin Hinshelwood
shared this idea
9 comments
Comments are closed-
Daniel Wilhite
commented
While we are at it, why don't we include Backlog Refinement in this and make them all a total disaster?
The separation is because they serve different functions. I am also wondering why you call them "meetings" but it also might indicate why you suggest combining them. If you look at them as events (as described in the Guide) or even as "activities" you can easily see how they are different and why they are best handled separately. If you look at them as meetings (which many complain about there being too many of) combining them into 1 could be seen as a good thing.
-
Andrew Marshall
commented
Like the others, I disagree. The two meetings have different purposes - Review for the product, Retrospective for the process.
-
Mike Dwyer
commented
I agree with the previous comments and need to ask an overall question based on the several suggestions you have made. Are you looking for some basics to applky in a process improvement process.?
-
Charles Bradley
commented
Martin, because I know you, I get the eery feeling that you should have posted this on April 1 instead of Feb 19. Am I right in that?
Consider me adamantly against this idea.
-
Rajesh Toleti
commented
Different set of audience so meetings should be separate. Time boxing should be done for all the events in advance in the spirit of scrum
-
Richard Banks
commented
As Andy said, the purpose and audience is different. Keep them separate.
I also disagree with removing the time boxes. Time boxes exist to limit the potential for time wasting and creates an environment for focused effort. Removing the time box would be counterproductive.
-
Andy Brandt
commented
I don't agree with this one. Those two events serve distinctly different purposes and different people participate. They should be kept separate.
-
Fredrik Wendt commented
I agree completely with Peter Gfader. I meet too many teams that have already merged the two events into one, kind of missing the point of both.
-
Peter Gfader
commented
I like the suggestion about "Let teams decide how much time that they spend on each one."
I don't like merging these 2 events.
Usually there are different people in those 2 meetings, and in my experience it's a great idea to leave the "room" between those 2, or better have it in 2 different places anyway.