A release retrospective is held at the end of the release and usually before starting the next release cycle. A schedule is worked out well in advance, and the date and time are communicated to all concerned so that they come prepared with some data.
How do you conduct a retrospective release?
To follow, break up your Retrospective into the following five stages:
- Set the Stage.
- Gather Data.
- Generate Insights.
- Decide What to Do.
- Close the Retrospective.
What is the purpose of a retrospective?
Definition: A retrospective is a meeting held after a product ships to discuss what happened during the product development and release process, with the goal of improving things in the future based on those learnings and conversations.
What is an example of retrospective?
Examples of retrospective in a Sentence
a retrospective analysis of what went wrong The museum is having a retrospective exhibit of the artist’s early works. Noun The museum is featuring a retrospective of Picasso’s early works.
What is a retrospective action?
Action focused retrospectives are a way for your team to reflect on your past cycle of work, discuss what you’ve learned, identify specific action items to pursue, and follow through on those action items.
What are the 3 retrospective questions?
Three things you can do today
- What went well (keep doing these things)
- What could be improved (went OK, but could be better)
- What went badly (don’t do these things again)
- Focus for next period/sprint/month/quarter (One or two things to focus on)
What do you say in a retrospective?
Questions to ask when closing a sprint retrospective
- Can you reiterate the most important thing you learned today?
- How are you feeling about our next sprint now that we’ve identified these issues?
- Is anyone confused or unclear on any of the items we discussed today?
- Do all of our next steps make sense?
Who is responsible for retrospection?
The sprint retrospective is usually the last thing done in a sprint. Many teams will do it immediately after the sprint review. The entire team, including both the ScrumMaster and the product owner should participate.