the pomodoro technique for sustainable pace

What is a Pomodoro? Pomodori for time boxing Case-studies Conclusions

The Pomodoro Technique for Sustainable PaceHow to feel time as an ally

Federico Gobbo Matteo [email protected]; [email protected]

Universita dell’Insubria, Varese; Sourcesense, Milano

(cc) Some rights reserved.

XP2008 Limerick, 2008 June 13th

Wannabe eXtreme?

http://www.ipernity.com/home/sendakseuss

How to start an XP team from scratch?

http://www.xpday.net/Xpday2007/session/XpLoops.html

Let’s start from XP team building...

team needs: velocity (story points / iteration)

each people needs: individual satisfaction, e.g. “coding is fun”

briefly:

a way to help teams find their ‘natural’ rhythm

The Pomodoro Technique (PT) is our proposalfor Sustainable Pace

briefly:

...from the PT, stand-up meetings, retrospectives

The Classic Pomodoro...

...is a kitchen timer...

...of whatever shape!

The Pomodoro is the unit of work

Pomodoro = 25 minutes + 5 minutes break

after 4 successful Pomodori:

a 15 minutes pause

The Main Goal of the Pomodoro Technique (PT)

perceive time as a valueI’m doing my best at a right rhythm

instead of:

perceive time as an enemyI’m not moving as fast as I can; I’m late

instead of:

When to apply the PT? In what kind of work?

professional

children homework

cleaning house

any work

professional

children homework

cleaning house

any work

professional

children homework

cleaning house

any work

professional

children homework

cleaning house

any work

professional

children homework

cleaning house

any work

Let’s see how to apply in XP teams

Our case-studies:

Milan XP user group (highly business-oriented)

Varese XP user group (linked with the local University)

Sourcesence (software house in Milan)

Sinapsi (software house in Milan)

Databtech (software house in Milan)

Quinary (software house in Milan)

7Pixel (software house in Milan)

Link I.T. (software house in Varese)

Perceived effects (in our experience)

When the PT is applied:

working time is not (so) wasted while Pomodoro starts;

overwork is drastically reduced;

the distinction between free time and work time is clear.

In other words:

Free Time is Free Time, i.e. Free from Pomodoro Time Boxing.

But how it works? The rules are very simple.

In other words:

The Zero Pomodoro Rule

If the Pomodoro is interrupted...

...that Pomodoro counts for nothing.

The Zero Pomodoro Rule

If the Pomodoro is interrupted...

...that Pomodoro counts for nothing.

Half pomodori?

The Fundamental Rule: A Pomodoro Is Indivisible

There are never half Pomodori:

the Pomodoro is the atomic unit of work!

The 4 Pomodori Rule

After 4 successful Pomodori take a longer pause

(usually 15 min., in any case never more than 1 Pomodorolong)

...and thank yourself after 4 following successful Pomodori.

The 4 Pomodori Rule

A typical day in a XP team using the PT

stand-up meeting (max. 1 Pomodoro)

4 Pomodori for work (usually in pairing)

a longer pause (usually 15’, max. 1 Pomodoro)

2 Pomodori for work (usually in soloing)

1 Pomodoro for a team continouspective

2 Pomodori for work (usually with different pairs)

1 Pomodoro for PT recording

Total: 10 pomodori per day

Ideal Engineering Days != Calendar Days

5 hours of real work at best is the optimum? Why?People believe to work at full-time on projects, but:

meetings

presales

support

...there are working activities not easily captured by the PT,especially in non-agile environments. With the PT teams learn toestimate every kind of working activity.

This is called the No Formula Rule.

The Pomodoro Technique’s FAQ

We found 7 key questions:

1 How many kitchen timers do I need in my XP team?

2 How to deal with interruptions?

3 What to do during breaks and pauses?

4 How to estimate pomodori?

5 How to record pomodori?

6 How to deal with multiple customers?

7 Can I use a software timer instead of a kitchen one?

1. How many kitchen timers

do you need in my XP team?

In *spectives: a timer per team

In pair programming: a timer per pair

Avoid the One Pomodoro to Rule Them All Style!

The Driver is responsible for loading and recording

In pair programming: a timer per pair

Avoid the One Pomodoro to Rule Them All Style!

The Driver is responsible for loading and recording

In solo work: a timer per member

http://www.flickr.com/photos/jeffhenshaw/244893028/

2. How to deal with interruptions?

Protect your Pomodoro

There are two kind of interruptions:

internal ones: I should check email; I need a coffee now

external ones: the phone rings; a colleague have a request, etc.

Remember the Zero Pomodoro Rule:if interrupted, end of your current Pomodoro.

Internal interruptions are more easily managed

in pairs, Driver helps Navigator and vice versa;

in teams, either a good coach or group pressure protectpomodori;

in soloing, the XP value of honesty assures your pomodori

In any case:

it is very important to record your (un)successful pomodori!

Internal interruptions are more easily managed

in pairs, Driver helps Navigator and vice versa;

in teams, either a good coach or group pressure protectpomodori;

in soloing, the XP value of honesty assures your pomodori

In any case:it is very important to record your (un)successful pomodori!

Some examples for programming pairs

Navigator takes notes like this in a TODO (or even GTD) list:

“test for empty input at method add user to group: 1 pomo”

“as Driver, test for exceptions: 2 pomos”

“as Driver, refactor db update max 20 lines: 2 pomos”

Some Navigators write even User Storiesthanks to Pomodori analysis

Some examples for programming pairs

Navigator takes notes like this in a TODO (or even GTD) list:

“test for empty input at method add user to group: 1 pomo”

“as Driver, test for exceptions: 2 pomos”

“as Driver, refactor db update max 20 lines: 2 pomos”

Some Navigators write even User Storiesthanks to Pomodori analysis

A pattern for external interruptions

In our experience, colleagues learn to respect your working timemore.

inform: After 8 minutes I will have a break.

negotiate: How really urgent is it?

callback: Ok. I’ll get back to you in 8 minutes

3. What to do during breaks and pauses?

First of all: accept your breaks!

Surprisingly, people don’t accept to thank themselvesfor their good pomodori through breaks and pauses.

A break is a break. Relax. You have worked well!

Suggestions:

Take a deep breath

http://www.ipernity.com/doc/willyong/1224617/

Have a cup of tea

http://www.ipernity.com/doc/underscan/764465/

4. How to estimate pomodori?

Individual planning

Estimating cards in pomodori

More Than Five Rule

Very big tasks?

Split it!

(just like User Stories)

More Than Five Rule

Very big tasks?

Split it!

More Than Five Rule

Very big tasks?

Split it!

Less Than One Rule

What if

it Lasts Less Than One Pomodoro?

Add It Up!

(it’s easy!)

Less Than One Rule

What if

Add It Up!

(it’s easy!)

Less Than One Rule

What if

Add It Up!

(it’s easy!)

Less Than One Rule

What if

Add It Up!

(it’s easy!)

5. How to record pomodori?

...with a Textile file

by Federico Gobbo

...with paper at Sinapsi

http://wiki.sinapsi.com/

...with a wiki at Databtech

by Alessandro Mercanti

...with a custom app at Sourcesense

...with EasyTracking II at XPLabs

by http://www.myagileprojects.com

6. How to deal with multiple customers?

Distribute your available pomodori according to priority

Customer A is very important: 50% effortCustomer B is important: 30% effortCustomer C is less important: 20% effort

This week we have 150 pomodori

Customer A will get 75 pomodoriCustomer B will get 45Customer C will get 25

by Gabriele Lana

7. Can I use a software timer

instead of a kitchen one?

Pros and Cons of software Pomodori

Our Mantra

Synopsis of the PT features

Synopsis of the PT rules

Thank you. Any questions?

Please don’t forget to tell us your experience:http://it.groups.yahoo.com/group/pomodoro/

(cc) Federico Gobbo & Matteo Vaccari 2008. Published in Italy.Attribution – Non commercial – Share alike 2.5

the pomodoro technique for sustainable pace

Technology