you say tomato, i say pomodoro
DESCRIPTION
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.TRANSCRIPT
“Becoming” Anxiety
time flow is frustrating if not measurable
even a few hours are difficult to “feel”
Why 25 Minutes?
short
enough to avoid frustration of becoming
enough to always feel energized
long
enough for a consistent unit of work
Exercise
common registration process:
collect information from a formvalidation and error handling
vend email with linkprocess registration confirmation
login welcome page
Rules
25 + 5 and 4 + 1The Pomodoro Is Indivisible
If a Pomodoro Begins, It Has to RingZero Pomodoro Rule
If More Than 5-7 Pomodoros, Break It DownIf Less Than One Pomodoro, Add It UpThe Next Pomodoro Will Go Better
Benefits
feeling of accomplishment
actively fights the “bad days”
prevents yak shaving
learn about yourself
Pomodoro Evolution
description and timestamppomodoro metrics
taggingpomodoro switch
standup preparationuser story elapsed time VS time spent
iteration retrospectivetimetable
Tools
timers, soft or hardpaper or paperless
spreadsheetomnioutliner and the alike
twitter dbkeeptempoeasytracking
Team Pomodoro
yesterday’s pomodorospair rotations
your break is not necessarily everyone’sthe coach protects all pomodoros
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