sap ageil sprint developmentysdfsdcsds.ppt

test

1. Agile
Retrospective Meeting
Name, SAP
January 18th, 2024
Add partner
logo and alt text

2. 2
Purpose
Provide insights about
when and how to organize a
Retrospective meeting in
Agile SCRUM Projects

3. 3
Objectives:
What and how can we do better next sprint?
While the scrum review meeting focuses on the results or deliverables, the sprint retrospective
concentrates on the sprint process itself
We have to identify means which enable us to be more efficient, better, or just have more fun in the next
sprint (or in the future in general)
Retrospective is not an opportunity to place blame
We learn what went well so we can repeat it
We learn what didn’t go well so we can stop doing it
What are the current top priority problems and how can we solve them during the next sprint?
Agile Retrospective Objectives

4. 4
When:
After each sprint (preferably after sprint demo)
As and when required
Participants: SCRUM Team and Product Owner if needed
Location: Room with whiteboard (undisturbed)
Time: half an hour to full day, depending on project and team size and sprint duration
Moderator: Scrum Master or any team member or external moderator
Facilities: Post-its, magnets or similar for dot votin
Retrospective – When and How To

5. 5
Generate Insights: Dot Voting Technic
Good stuff Bad Stuff Ugly Stuff
If we could redo the same
sprint again, we would do
these things the same
way
If we could redo the same
sprint again, we would do
these things differently
If we could redo the same
sprint again, we would not
do this at all
Post-
it
Post-
it
Post-
it
Post-
it
Post-
it
Post-
it
Post-
it
Post-
it
Post-
it
Post-
it
Post-
it

6. 6
•Plan at least one hour of preparation time for a sprint retrospective.
•Optimal: large room without tables to allow for group work.
•Review and update your Team Charter during a retrospective.
•When deciding what to do, ask people what they feel most passionate about.
•Bring burndown charts, picture of whiteboard or other artifacts which help the team remember
what happened.
•Do not “overdo” but focus on the most relevant aspects, focus on top impediments.
•A sprint retrospective could involve, if felt appropriate by the team, other relevant stakeholders
(QA, RUN organization, Architects, etc..)
•Put list of retrospective action items on the team board (to escape the “out of sight, out of mind”
syndrome)
Tips and Tricks for Spring Retrospectives

7. 7
•First and foremost: make sure retrospective decisions are implemented.
•Vary the activities you use in a retrospective (e.g. try emotional seismograph to find out stress
patterns during a sprint; use activities so that everybody – even the introverts – gets heard during
the course of the retrospective).
•Consider inviting stakeholders every now and then to bring in new perspectives.
•Consider inviting an external facilitator (i.e. not from within the team).
•Don‘t always use the „generic“ approach (what went well, what can be improved), but instead
tackle specific problems in a retrospective.
•Change the moderator (does not have to be the Scrum Master all the time; but don‘t force anybody
to be a retrospectives facilitator).
•Check whether decisions from former retrospectives have been put to action; if not, consider
skipping a retrospective and make sure old decisions are implemented first.
How to Keep Sprint Retrospectives Interesting

8. Contact information:
© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material.
Thank you.
Name
Email