Why Should You Retrospect? An Agile Story
-
Upload
george-psistakis -
Category
Software
-
view
276 -
download
0
Transcript of Why Should You Retrospect? An Agile Story
Retrospective
Spock
An agile story
In startup life things get "bumpy” pretty
fast.
“So much for the little training cruise”
I am George,
Co-founder of a
startup named
Apirise
PM, Scrum Master co-organizer of the Agile Greece and
API Athens Meetups
Good communication
in a team is not to
be taken for
granted!
“This is how it should be…”
“Everybody knows that…”
In reality, things remain that are not
spoken…
“I didn't have time…”
“nothing ever happened…”
Lets do retrospectives…
not structured1 hour! strictly!
All take 5-10 minutes to think silently and
write down the things we:
a) Did well and should continue
b) Could do better by introducing minor
modifications
c) Should improve by introducing a major change.
This could include things we should stop doing as
well.
“Vulcans never bluff”
Take turns and stand up
Post-it on the wall with your idea
Do not interrupt the person standing
Vote…
“Insufficient facts always
invite danger”
Estimating is not easy, but it
comes with experience.
There are external factors in a life
of a startup that can kill your
estimate.
“Change is the essential process of all existence.”
We keep everything on the wall.
All have a view of the changes we need
to put in place.
Sometimes even talking about a problem
helps understanding any hidden issues.
@Giorgosps
www.apirise.com