Your SlideShare is downloading. ×
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Agile Pomodoro Development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile Pomodoro Development

7,956

Published on

Talk I gave at the Chicago APM meetup group on May 5, 2009. Compared to the my old pomodoro talk, this one is more detailed about the practices and focuses on team integration, especially XP.

Talk I gave at the Chicago APM meetup group on May 5, 2009. Compared to the my old pomodoro talk, this one is more detailed about the practices and focuses on team integration, especially XP.

2 Comments
18 Likes
Statistics
Notes
  • Thanks Carlo! Also consider the refined version of the slides I gave at Agile 2009. I incorporated more details about how I use the technique (http://www.slideshare.net/reborg/you-say-tomato-i-say-pomodoro-1915255) and the slides are in a printable 3x5 index card format. You make think that now it's 2011 and I should upgrade the presentation adding the details learned in the past 3 years. Time for the next talk! ;)
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I'm landing here just today - April 2011. This presentation is 2 years old. I'll call it a classic (as an old movie, or book, still keeping 100% of its meaning and beauty .. even when a lof of time has passed). I've been using pomodoro technique for a few years. Even tried to extend it to the team I was leading, a couple of years ago (with mixed results). The literature about pomodoro technique usage in teams is quite bare. These slides, clear and concise, are a good reference.

    Thanks for sharing them, Renzo. (I'll watch the video on Vimeo. Now in my activities inventory)
    carloz
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
7,956
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
184
Comments
2
Likes
18
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. http://github.com/reborg/talk-pomodoro Agile Pomodoro Development renzo.borgatti@agilepartners.com - Chicago APM - May 5th 2009
  • 2. P = Pomodoro
  • 3. Pomo what ? Francesco Cirillo, late ‘80s http://cirillosscrapbook.wordpress.com “Can you study, really study, for 10 mins?” He used a pomodoro shaped kitchen timer Technique refined over 20 years of coaching www.pomodorotechnique.com
  • 4. Rules P = 25’ + 5’ 4P + 20’ P doesn’t count if interrupted P is allocated to only one task
  • 5. Consequences P is indivisible: there are no 0.5P If task done, continue same task Protect P: inform, negotiate, reschedule
  • 6. Estimation If more than 5-7P break it down If less than one P add it up Collect all in the Inventory Sheet Allocate daily in the Today Sheet Record raw data
  • 7. Breaks Are Breaks P = what to do between breaks!
  • 8. Pomodoro Practices Day Dreaming Most effective break Train body to relax deeply in 5’ Close your eyes Relax completely http://reborg.tumblr.com/post/102158578/ how-to-take-a-5-minutes-nap
  • 9. Pomodoro Practices
  • 10. Pomodoro Practices Session Cycle New Today Sheet Available pomodoros Not done from last session Grab others from inventory Execute Pomospective
  • 11. Pomodoro Practices Execution Cycle Start pomodoro Is schedule still consistent with priorities? Execute next task Ring: close sentence/thought/line Write tags and description Mark one P Break
  • 12. Pomodoro Practices Handling New Task Always close current task Never jump to other task Use mocks, fakes, façades, whatever Append new task to inventory Re-prioritize on next P
  • 13. Pomodoro Practices Tagging The tag is the type of activity at ring-time @planning, @meeting, @refactoring ... Be consistent
  • 14. Pomodoro Practices Pomospective Why so many/few pomodoros? Why task “x” is 6 times the estimate? Why I feel so tired?
  • 15. Pomodoro Practices Demo
  • 16. Team Integration
  • 17. Team Integration 1 P = 1 Pair OR One P per workstation Negotiating P start Multiple P allow flexibility
  • 18. Team Integration Interrupt Shield Someone who protects the P for the team Coach or Scrum Master Inform, Negotiate, Reschedule
  • 19. Team Integration Standup Read last pomospective Read last pomodoro raw dump After the standup: Session Cycle
  • 20. Team Integration Ping Pong Pomo For pairs First P: dev-A writes tests, dev-B writes code Next P the other way around
  • 21. Team Integration Collective Break Decide target time (e.g. for lunch) Allow for around 15’ of synchronization time Don’t start a new P if you finish 15’ before target time
  • 22. Team Integration Break Room Don’t bug the team if you’re on break Distinct room or kitchen for breaks A couch would be great
  • 23. Metrics
  • 24. Metrics Count/Day
  • 25. Metrics Count/Tag tag
  • 26. Metrics Developer/Month Don’t be evil competition Highest count - Standard Deviation (we don’t want people to have a 40P/day and a 2P the next day ;)
  • 27. Conclusions
  • 28. Conclusions A measure of quality 8 hours != 16P Measuring in P means measuring quality work Include quality when exporting from P to H 12P =~ 8-10 hours
  • 29. Conclusions Break First Class Citizen Breaks as a commitment to your brain Breaks are planned as well as work Rhythm for a long run
  • 30. Conclusions Micro-Cosmos A reduced scale project lives in one P Including: frequent changes, tracking, estimation, focus, interaction, scope, negotiation etc. Rule the Pomodoro to rule them all!
  • 31. Resources The Pomodoro Technique http://www.pomodorotechnique.com The Pomodoro Book www.pomodoro-book.com The original paper http://www.tecnicadelpomodoro.it/docs/francesco-cirillo/2007/ThePomodoroTechnique_v1-3.pdf Keeptempo www.keeptempo.com Pomodori Timer http://reborg.github.com/pomodori

×