A short overview of how the Pomodoro Technique can be used for developers together with Scrum.

1. Pomodoro
Technique®
and
Scrum

2. Comparison Pomodoro vs Sprint
Each Pomodoro becomes a
mini sprint of sorts, where you
are your own ScrumMaster
 Each Pomodoro has the same length
 A Pomodoro, like a Sprint, is indivisible
 You work actively to remove obstructions

3. Overview of Workflow
Pomodoro
Work Day
Sprint

4. Pomodoro Benefits
Benefits of using the Pomdoro
Technique® as a programmer
 Helps you focus on the task at hand (helps making commits
task oriented)
 Maintain a sustainable pace and prevent fatigue as you are
reminded to take breaks regularly
 Time for refactoring when you finish tasks before the sprint
has ended, and by using dedicated refactoring Pomodoros

5. The Pomodoro To-Do Sheet

6. Programmer’s Pomodoro Structure
 In the beginning of the Pomodoro, plan the next steps
necessary to complete the task.
 At the end of each Pomdoro, review written code and
potential problem areas.
 Every third or fourth Pomodoro, dedicate a Pomodoro for
refactoring.

7. Pomodoro Major Cycle (Pomodoro Set)
Pomodoro Set
Development Refactoring Break

8. Dealing with Interruptions
Inform
Let the interruptor know you’re busy at the moment.
Negotiate
Agree on a time when you can get back to them.
Call
Make sure you get back to them on the time agreed.