Why Should You Retrospect? An Agile Story

17
Retrospective Spock An agile story

Transcript of Why Should You Retrospect? An Agile Story

Page 1: Why Should You Retrospect? An Agile Story

Retrospective

Spock

An agile story

Page 2: Why Should You Retrospect? An Agile Story

In startup life things get "bumpy” pretty

fast.

Page 3: Why Should You Retrospect? An Agile Story

“So much for the little training cruise”

Page 4: Why Should You Retrospect? An Agile Story

I am George,

Co-founder of a

startup named

Apirise

PM, Scrum Master co-organizer of the Agile Greece and

API Athens Meetups

Page 5: Why Should You Retrospect? An Agile Story

Good communication

in a team is not to

be taken for

granted!

Page 6: Why Should You Retrospect? An Agile Story

“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…”

Page 7: Why Should You Retrospect? An Agile Story
Page 8: Why Should You Retrospect? An Agile Story

Lets do retrospectives…

not structured1 hour! strictly!

Page 9: Why Should You Retrospect? An Agile Story
Page 10: Why Should You Retrospect? An Agile Story

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.

Page 11: Why Should You Retrospect? An Agile Story

“Vulcans never bluff”

Page 12: Why Should You Retrospect? An Agile Story

Take turns and stand up

Post-it on the wall with your idea

Do not interrupt the person standing

Vote…

Page 13: Why Should You Retrospect? An Agile Story

“Insufficient facts always

invite danger”

Page 14: Why Should You Retrospect? An Agile Story

Estimating is not easy, but it

comes with experience.

There are external factors in a life

of a startup that can kill your

estimate.

Page 15: Why Should You Retrospect? An Agile Story

“Change is the essential process of all existence.”

Page 16: Why Should You Retrospect? An Agile Story

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.

Page 17: Why Should You Retrospect? An Agile Story

@Giorgosps

www.apirise.com