Pomidor

Fear not

Problems

• Context switches
• Distractions
• Frustration

Tomato to the resque

Theory

• 25 minutes sessions of work
• 5 minutes break
• repeat
• after 4 sessions longer break

Theory

• 15 sessions of work = 375 minutes = 6:15
• 12 sessions of short breaks = 60 minutes
• 3 sessions of longer breaks = 45 minutes

Work session

• Focus on single task only
• Ignore distractions

Work session

• Programming, designing, etc
• Planning, discussions, meetings
• Code review
• Replying on mails
• Point 1
• Anything what takes time

Break

• Respond to questions
• Ask questions
• Adjust plan
• Check email, slack
• Review your work
• Take a break ;)

105 minutes of breaks

Hard things

• Fit meetings into pomodoro
• Discipline
• Wait before asking

Side effects

• Highly efficient last minutes
• Healthy breaks
• Discipline
• Estimations
• Find time for Point 1
• Perfect fit for pair programming
• Prepared for standup

Protips

• First session for day plan
• Differ between plan session and mechanical work
• Use Productivity Planner or simple notepad

Example

09:00 .. 9:25 - check email, plan your day
09:25 .. 9:30 - make a coffee
09:30 .. 9:55 - prepare and go to standup
09:55 .. 10:00 - sync with team mates
10:00 .. 10:25 - plan task X

10:25 .. 10:30 - check slack & email

10:30 .. 10:55 - coding for task X

10:55 .. 11:10 - check slack & email

11:10 .. 11:35 - coding for task X

11:35 .. 11:40 - find new task

11:40 .. 12:05 - ...

Next steps

• Start discussion
• Create global clock (TV? Slack?)
• Respect those who follow tomato
• What about Roundup, Dev meetings etc?