The Pomodoro Technique
The goals
Focus
Interruptions
Estimation
Efficiency?
Scheduling
Is multitasking good?
Defining one goal for the current timebox
External
Internal
Colleagues, boss
Telephone
Mail
I must check that website
I have to remember to buy milk
I wonder if that other class is ready...
Void the Pomodoro if unhandled
Maker's schedule vs. Manager's schedule
Move them 
Communication cannot be eliminated
Inform-negotiate-callback
Add at the end of the list (backlog/iteration)
Team tip: rotate a member
Collective Pomodoro
Done in Pomodoros
A few integer Pomodoros
Low risk
Easy benchmarks
Whole team is committed, do not force
Forced breaks
Am I interrupting my flow?
Concepts are in Camel Case: Sustainable Pace
Benchmarking helps: if you can't measure it...
Tip: include setup time in Pomodoros
Parkinson's Law
In Pomodoros: 4 and 3 morning, 4/4 afternoon
4, 3; 4, 4
They are by definition unexpected
Hook points for questions
The PT in 60 seconds
A little story
I will give you 860.00 thalers each day
Where's the catch?
You must spend them all every day
Tomorrow you won't be richer
You have certain expenses to cover
Will you be go broke or stay afloat?
No overdrafts
Metaphors: Agile methods, hardware and software
Save your stack
Less tech
Stop procrastination 
Winding up becomes a starter ritual
not too small
Continuous feedback
Don't use it for
Free time
Leisure tasks
Only 5-10 minutes available
Uninterrupted
Focused on a single task at the time
Real break, away from pc if you can
Deciding if the PT is for you, not in what sheets to draw circles
Work expands so as to fill the time available for its completion.
Flexible
Easy to learn
just do a Pomodoro, you'll get the momentum to do 4
5; 2; 4, 4
...
not too large
Only a Pomodoro can be lost each time
record re-estimate, no external factors
Each day there is a Pomodoro balance sheet
References
The (free) PT book
The story is from Marc Mancini's Time Management
The Agile comparisons are from Mike Cohn's Agile estimating and planning
The Goal: 
http://www.pomodorotechnique.com/book.html
Thanks for your attention
Reading a tech book
Team
false sense of precision
too high variance
Sustainable Pace
http://en.wikipedia.org/wiki/Parkinson's_law
http://www.extremeprogramming.org/rules/overtime.html
Images are from the public domain or shot myself or with URL for attribution
(aka: doing things right vs doing the right things)
It's eficiente vs. eficaz in Spanish
http://en.wikipedia.org/wiki/Flow_(psychology)
Flow is the mental state of operation in which a person in an activity is fully immersed in a feeling of energized focus, full involvement, and success in the process of the activity. 
aka The Zone
You can said it out loud
Giorgio Sironi
Zone Leader @ DZone
Former Architect, now Advisor @ Allbus
Bachelor in Computer Engineering
One reason programmers dislike meetings so much is that they're on a different type of schedule from other people. Meetings cost them more.

http://www.paulgraham.com/makersschedule.html
Fibonacci-based user stories: 1, 2, 3, 5, 8, 13 points...
Iterations?
“Alice came to a fork in the road. 'Which road do I take?' she asked. 
'Where do you want to go?' responded the Cheshire Cat. 
'I don't know,' Alice answered. 
'Then,' said the Cat, 'it doesn't matter.” 
to end of Pomodoro (quick)
to a specialized Pomodoro (long)
You do not feel time is passing
Courtesy of dilbert.com