A "tomato" is a slot of 25 minutes where you focus continuously on a single task. The "pomodoro technique" is a tracking and feedback process that fills the gap between the high-level tracking of user stories and the hour-by-hour development cycle.
8. Why 25 Minutes?
short
enough to avoid frustration of becoming
enough to always feel energized
long
enough for a consistent unit of work
9. Why 5 minutes?
short
enough to remember what’s the goal
long
enough to enable sustainable pace
10. Exercise
common registration process:
collect information from a form
validation and error handling
vend email with link
process registration confirmation
login welcome page
11. Rules
25 + 5 and 4 + 1
The Pomodoro Is Indivisible
If a Pomodoro Begins, It Has to Ring
Zero Pomodoro Rule
If More Than 5-7 Pomodoros, Break It Down
If Less Than One Pomodoro, Add It Up
The Next Pomodoro Will Go Better
15. Benefits
feeling of accomplishment
actively fights the “bad days”
prevents yak shaving
learn about yourself
16. Pomodoro Evolution
description and timestamp
pomodoro metrics
tagging
pomodoro switch
standup preparation
user story elapsed time VS time spent
iteration retrospective
timetable
17. Tools
timers, soft or hard
paper or paperless
spreadsheet
omnioutliner and the alike
twitter db
keeptempo
easytracking
18. Tracking Exercise
start the timer
a pomodoro was spent
store pomodoro
break
restart
19. Team Pomodoro
yesterday’s pomodoros
pair rotations
your break is not necessarily everyone’s
the coach protects all pomodoros
20. Resources
the original paper http://www.tecnicadelpomodoro.it/docs/francesco-
cirillo/2007/ThePomodoroTechnique_v1-3.pdf
PT in XP Teams http://www.tecnicadelpomodoro.it/docs/conferences/gobbo-
vaccari-XP2008-camera-ready.pdf
easytracking http://www.myagileprojects.com/demo.html
keeptempo www.keeptempo.com