Retrospective Simulation: Better to See Once Than to Hear 100 Times
Retrospective is known to be one of the most valuable ceremonies in Scrum. This is an opportunity for the team to take a look back on the past Sprint and learn. Retrospectives can be frustrating or interesting and lively - a lot depends on the facilitator. There are a number of supporting tools on the market to help keeping Retrospectives engaging (and manageable if you work with distributed teams). Yet, there are also some base steps, which we should remember while holding retrospectives regardless of the chosen tool or method.
Outline/structure of the Session
Like it is said "Better to See Once Than to Hear 100 Times”, the goal of this simulation is to demonstrate retrospective on a typical Scrum team by keeping in mind fundamental steps which are essential to achieving a successful outcome.
By the end of this simulation you will know key facilitation techniques for holding an effective Retrospective.
Scrum Masters, Project Managers, Release Train Engineers, and anyone interested in learning about effective retrospective facilitation
schedule Submitted 2 years ago
People who liked this proposal, also liked:
Maria Smyslova - Agile (Scrum) transformation : Learn from the mistakes of othersMaria SmyslovaScrum Master, CSM, PMPCapitalOne
schedule 2 years agoSold Out!
Agile adoption can be very challenging and many companies run into various issues on the path to transforming their organizations. Scrum is one of the most common Agile frameworks and is the focus of this talk.
A lot of new teams are failing to start with creating a healthy backlog which is a backbone of a Scrum project (properly sliced stories, clear prioritization, non-functional work etc.)
Others are trying to tailor their processes to the selected agile software management tools rather than focusing on practices that can increase team’s velocity and product quality.
The goal of this talk is to have an interactive discussion about lessons learned and best practices that can be helpful in implementing Scrum as well as sustaining it in a more efficient and stress-less way.