It’s continues improvement aimed meeting, taken place at
the end of each sprint. Helping the team to improve their performance
effectives and efficiency (http://qconlondon.com/london-2012/presentation/Effective%20Retrospective). We look back as a team, learning from what
we did wrong and how to improve in the future. And learning from what we did well
and how to recreate it.
This is, in my opinion, one of the most important sessions
to take place as part of the agile rituals that lead us to continuous
improvement.
Don’t skip this session!
Why ?
Because it’s a learning meeting. We Communicate our
performance on a regular basis (end of each sprint) we retrospect over our
performance and pick action for next sprint.
** Just before we continue , please note, I will be using
the term “team” as a general reference , but, you may apply this to family members,
classmates, teachers group and any other form of ‘team’ with common goals.
Why retrospective?
·
Because improvement does
not come alone. Having a heart beat of
improvement sessions will take us forward.
·
Because we if want to
constantly improve we need to have this official
place and time, and it goes without saying that talking about our performance
is what we naturally do, Regardless our results.
·
Because continues
improvement and learning can come only when we are set to reflect over our
performance, effectiveness and efficiency.
·
Each team member sees
things differently, if we wish to improve as a team we need to get everyone’s
opinion to the context of the team.
·
Without a retrospective
session, the team will probably continue to make the same mistakes all over
again and the improvement items will be randomly, based on crisis and the rate of
improvement will be lower than it can get.
Who attends the retrospective?
Team members only! Those who have tasks on the board. Pigs ,
remember?
Managers are not allowed. Why? Because it’s a self-organized
team, remember ? Because the team should
be accountable for its performance, therefore accountable for the improvements.
The team will decide whether to share or not retrospective
items.
The scrum master can conduct the meeting few first times , but later on it is
recommended that The team will conduct the meeting.
Things that should take place during the
retrospective:
·
The
retrospective is an open discussion
·
Set
up goals
·
Assign
tasks to goals for next sprint.
In this session, we will ask ourselves questions:
1.
What
should we continue doing?
2.
What
should we stop doing?
3.
What
should we start doing?
Or :
What were our successes
“+” , or things we wish to improve “_”
The session should take place at a time when it’s convenient
to chat, in a sharing atmosphere. Each team member should feel entitled to
comment and contribute to the session and to the three questions.
We sometimes encountered people who avoid this session with
various excuses, such as “we don’t have time for yet another meeting”,” we
don’t want to share our thoughts and feelings with others”, and so on. Team
members may be afraid to share their thoughts and opinions, especially if the managers
are very 'command and control', ordering team members around and managing the team
tasks.
Two types of retrospective as important to mention:
·
We can have a goal
oriented retrospective, which is aimed to talk about a specific issue. For
example – our relationships as a team with our interfaces.
·
Or we can have what I
call as “free hand” retrospective
, which is more of an open discussion
over issues bothers the team , and from there the discussion will scope over
the most important issues that the team thinks needs discussion.
Setting up a retrospective session:
●
Allocate about an hour of team
time.
●
Conduct the session when
just the team members are present, especially for the first few sessions.
●
Have the session where you
all feel comfortable. Don’t take it outside, at least not at the first times.
●
Set the ground rules: for example:
everybody can talk , we are here to share our view, don’t interrupt when one
team member is talking and more…
As usual, the format may vary, and you can employ more creative
methods than just conversation or writing tasks down on sticky notes. Here are few examples:
Example 1 :
●
One team member will review
the weekly tasks. Preferred to be the scrum master Along with the rest of the team,
the scrum master will summarize the sprint: main events, achievement, outcomes.
●
Each team member says, in
his turn, what he thought of the sprint, what can be done better, what we
should keep on doing and what we should we start doing.
●
One team member needs to
summarize what the team says. This shows that we are taking the session and the
things the team members are saying seriously.
●
Pick a few tasks (not many)
for preservation, changing, or to start doing.
●
Assign a team member to
each task. His role will be to follow this task and make sure we discuss this
task in the daily family gathering.
●
All team members are
committed to the retrospective tasks and outcomes.
●
In each retrospective
session, bring up the outcomes and progress of the previous session’s action
items. You may even choose to bring up the previous tasks as something we may
want to deal with in our next sprint.
Example 2:
1.
Draw three columns on a
white board or piece of paper:
●
Things we would like to
keep on doing.
●
Things we would like to
stop doing.
●
Things we would like to
continue doing.
2.
Pass around sticky notes.
3.
Each team member writes
down issues and adds them to the appropriate column. Don’t comment or criticize
team members over issues they add to the board.
4.
Once all finished, the team
chooses the first team member to go to the board and make his case. Explain
that you should start off with the positive things.
5.
When a team member finds
that another team member wrote the same thing he did, he may approach the board
add his sticky note together with the one presented.
6.
When a team member start
presenting the issues he thinks requires improvement, start asking questions.
7.
We now have a good overview
of the issues that occupied our mind during the last sprint. We also know what
are the most important issues we need to improve, as we listened to all the team
members' opinions.
8.
Now, it’s possible that
some issues will create a lengthy conversation. If this happens, it is best to
stop the discussion, and ask the team members to talk about it after the
retrospective session.
9.
After all the tasks and team
members concerns are on the board, lets select the tasks for improvement, to
keep or to start doing.
10.
We can move the selected
tasks to our ongoing tasks board, and put the rest in the backlog. This way we
make sure the improvement will be followed (during the daily meeting) and will
take place.
You can perform this session in many more creative ways, as
long as you remember to have :
·
Open discussion:
o
Remember to get into the
mood of active listening. Ask questions during the session. Don’t let slogans to stay as is, get to the
root cause of what happens.
o
Visualizing and sharing
your issues as a team on the board, as part of a team dialog, makes it easier
to talk about issues and address them.
·
Set up goals
Achieving
goals with agile – using Kanban and scrum with kids and at home
Why
spiders can help you achieve your goals
·
Assign tasks to goals
for next sprint.
o
Just make sure not to
select too many tasks for improvement. Focus on the important ones.
o
By the way, this isn’t as
obvious as it sounds. By choosing the important tasks, we find out what the
other family members are thinking. We may find out that there are specific
issues that bother more than one family member, and we can focus on those for
improvement.
More creative retrospective sets:
Attention and techniques:
• Don’t let this session become a status reporting meeting and
then to be delivered later to managers.
• The past looks all black and the retrospective becomes a
sad or angry meeting?
• Use future
spective technique to look at the future and make things better.
• When we delay issues to the retrospective instead of solving
them on the spot.
• Raise the issue in the retrospective and make sure to bring the
message that issues can be solved outside the retrospective as well..
• Too many problems rise in the retrospective?
• Set priority and take issues offline to task forces.
• Deal with one issue at a time
You can use
“retrospective” session whenever you have something you want to check and
improve , you don’t need wait to have a
retrospective session to make a change or improvements. All you need to know is
how to talk about things.
o Credit “agile kids book “
