The document discusses the importance of effective communication and retrospectives in a startup environment, emphasizing the need for structured reflection on team performance. It outlines a process for team members to identify and address what is working well, what could be improved, and what should be stopped. The author highlights the role of external factors in project estimation and the necessity of open dialogue to uncover underlying issues.

1. Retrospective
Spock
An agile story

2. In startup life things
get "bumpy” pretty
fast.

3. “So much for the little training
cruise”

4. I am George,
Co-founder of a
startup named
Apirise
PM, Scrum Master
co-organizer of the
Agile Greece and
API Athens Meetups

5. Good communication
in a team is not to
be taken for
granted!

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

8. Lets do retrospectives…
not structured
1 hour! strictly!

10. 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.

11. “Vulcans never bluff”

12. Take turns and stand up
Post-it on the wall with your idea
Do not interrupt the person standing
Vote…

13. “Insufficient facts always
invite danger”

14. Estimating is not easy, but it
comes with experience.
There are external factors in a life
of a startup that can kill your
estimate.

15. “Change is the essential
process of all existence.”

16. 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.

17. @Giorgosps
www.apirise.com