you say tomato, I say...

Pomodoro
In XP


user stories, planning game, iteration starts
Or Maybe Scrum


user stories, product backlog, sprint backlog,
                 sprint starts
then what?
“Tasks”


few hours, half a day, a few days
“Becoming” Anxiety


time flow is frustrating if not measurable
 even a few hours are difficult to “feel”
Time Boxes


how long a time box should be?
Why 25 Minutes?
                short
enough to avoid frustration of becoming
   enough to always feel energized
         ...
Why 5 minutes?

              short
enough to remember what’s the goal
               long
 enough to enable sustainable p...
Exercise

common registration process:
  collect information from a form
   validation and error handling
        vend ema...
Rules
                25 + 5 and 4 + 1
           The Pomodoro Is Indivisible
      If a Pomodoro Begins, It Has to Ring
 ...
Short Break


distraction forces re-prioritization of
  thoughts for the next pomodoro
Longer Break


helps maintaining a sustainable pace
Protect the Pomodoro


    inform, negotiate, reschedule
           GTD anyone?
Benefits

 feeling of accomplishment
actively fights the “bad days”
    prevents yak shaving
    learn about yourself
Pomodoro Evolution
       description and timestamp
            pomodoro metrics
                  tagging
            pom...
Tools
  timers, soft or hard
  paper or paperless
      spreadsheet
omnioutliner and the alike
       twitter db
      kee...
Tracking Exercise
      start the timer
   a pomodoro was spent
     store pomodoro
          break
          restart
Team Pomodoro

        yesterday’s pomodoros
             pair rotations
your break is not necessarily everyone’s
  the co...
Resources

the original paper http://www.tecnicadelpomodoro.it/docs/francesco-
                cirillo/2007/ThePomodoroTec...
Upcoming SlideShare
Loading in …5
×

You say Tomato, I say Pomodoro

3,364 views
3,271 views

Published on

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.

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,364
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
59
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

You say Tomato, I say Pomodoro

  1. 1. you say tomato, I say... Pomodoro
  2. 2. In XP user stories, planning game, iteration starts
  3. 3. Or Maybe Scrum user stories, product backlog, sprint backlog, sprint starts
  4. 4. then what?
  5. 5. “Tasks” few hours, half a day, a few days
  6. 6. “Becoming” Anxiety time flow is frustrating if not measurable even a few hours are difficult to “feel”
  7. 7. Time Boxes how long a time box should be?
  8. 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. 9. Why 5 minutes? short enough to remember what’s the goal long enough to enable sustainable pace
  10. 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. 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
  12. 12. Short Break distraction forces re-prioritization of thoughts for the next pomodoro
  13. 13. Longer Break helps maintaining a sustainable pace
  14. 14. Protect the Pomodoro inform, negotiate, reschedule GTD anyone?
  15. 15. Benefits feeling of accomplishment actively fights the “bad days” prevents yak shaving learn about yourself
  16. 16. Pomodoro Evolution description and timestamp pomodoro metrics tagging pomodoro switch standup preparation user story elapsed time VS time spent iteration retrospective timetable
  17. 17. Tools timers, soft or hard paper or paperless spreadsheet omnioutliner and the alike twitter db keeptempo easytracking
  18. 18. Tracking Exercise start the timer a pomodoro was spent store pomodoro break restart
  19. 19. Team Pomodoro yesterday’s pomodoros pair rotations your break is not necessarily everyone’s the coach protects all pomodoros
  20. 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

×