AGILE RETROSPECTIVE

SDeepak T Gururaja

DID YOU KNOW The very first version of Scrum did not

have a retrospective meeting Can you think of Scrum as a process

without an avenue to “Inspect and Adapt”

YES, WE KNOW THIS A ceremony conducted at the end of a

sprint Inspect and Adapt The last and the most important Agile

PrincipleAt regular intervals, the team reflects on

how to become more effective, then tunes and

adjusts its behavior accordingly

YES, WE KNOW THIS Time-boxed Attendees restricted only to

TeamScrum MasterProduct Owner

Scrum Master may or may not be the facilitator

The facilitator is just that The facilitator does not provide answers

THE PRIME DIRECTIVE

Regardless of what we discover, we understand and truly believe that

everyone did the best job they could, given what they knew at the time, their

skills and abilities, the resources available, and the situation at hand.

WHAT TO TALK ABOUT IN A RETROSPECTIVE What was out learning from the sprint What did we do well What should we do well What are the problems that we faced Retrospectives are also a place to

appreciate fellow team mates

IMPORTANT POINTS TO REMEMBER Come prepared with your inputs Points should not be directed to an

individual Its not so much about what went wrong,

rather about how can we correct it Always keep the time box in mind Arrive at constructive points for

implementation Before leaving the retrospective, have a

clear goal on what the future action plan will be

WHAT AGILE RETROSPECTIVES ARE NOT

AS A TEAM MEMBER It’s the best platform to bring out areas

of improvements Provide frank and data-driven insights

on the events that took place in the sprint

Keep the conversation focused Most importantly – Participate actively

QUESTIONS Why do you think retrospective is

important? When do you think a retrospective fails? What happens when retrospectives fail? Do you think retrospective should take

as long as it takes? Can you each identify one benefit of a

retrospective?