Hide Notes 

Slide 1: http://github.com/reborg/talk-pomodoro/tree/agile2009 You Say Tomato, I Say Pomodoro doro omo tical P uide Prac ue G A chniq Individuals Te and Team for renzo.borgatti@agilepartners.com - Agile 2009
Slide 2: Pomo WHAT?! Francesco Cirillo, late ‘80s “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
Slide 3: Basic Rules 25 mins + 5 mins Longer Break Every 4 Pomodoros If a Pomodoro Begins, It Has to Ring The Pomodoro Is Indivisible One Single Task Each Pomodoro
Slide 4: Breaks ARE Breaks
Slide 5: Practical Rules Void the Pomodoro If Interrupted Review Same Task If Done Before Ring Protect the Pomodoro from Interruptions Inform, Negotiate and Reschedule
Slide 6: Estimation A Task Should not be more than 5/7 P A Task Should not be less than 1 P Split big tasks if necessary Aggregate multiple tasks if necessary Pomodoro Capacity Yesterday’s Pomodoros
Slide 7: Implementations Paper Based Plain Text Files Text Text Spreadsheets Suitable Software Tools mony Cere vel Le ation utom A
Slide 8: Plain Text Files No specific tools needed Simple formatting rules Easy to store Easy to version under source control Easily Scriptable
Slide 9: rE Ou le p am x t! ec roj P
Slide 10: User Registration Comment Proposal Create Proposal Show Tweets Signup Newsletter Search The Site Download Program PDF Edit Content Of Site Write a Blog Post
Slide 11: Show Tweets Create Proposal Download
list
of
current
Tweets Tweets
sidebar
on
the
page Create
page
with
form
and
submit
button Handle
validation
and
errors Show
proposal
preview Confirmation
page Edit Content of the Site Show
edit
link
for
editable
pages Create
form
page
with
page
body
 editing Include
WYSIWYG
editor Allow
preview
of
edited
page Save
page
as
draft Signup Newsletter Create
form
page Handle
validation
errors
email Send
email
to
registered
users Confirmation
page
Slide 12: Inventory Sheet Collection of fine grained tasks Estimates in Pomodoros Multiple User Stories Repository for new and unexpected tasks Order defines priority Tasks categorized by @tags
Slide 13: Inventory Sheet Structure UPPERCASE HEADERS FOLLOWED BY A COLON: IT’S AN USER STORY NAME OR A SUBPROJECT: - @multiple @tags starting with a dash - @followed by a number are tasks 4 THE INBOX IS AT THE BOTTOM: This is the “TaskPaper” format (VIM plugin available) You can roll out your own 5
Slide 14: How to Use the Inventory Move lines around to set priorities Try to use a single line each task Append to INBOX all new tasks Process the INBOX before the standup
Slide 15: Inventory Workflow Process INBOX Grab tasks from User Story repo Split tasks, add spikes if necessary Re-estimate Pomodoros Prioritize, move up and down
Slide 16: ice ct ra sP t’ Le ith ry w to en nv I he t
Slide 17: Todo Today Sheet Record relevant session facts Create a new one each session (day) Fill from inventory when empty Mark done pomodoros Mark total done and total planned Record interruptions
Slide 18: What’s in the Todo Today SCHEDULE: to calculate pomodoro capacity PLANNED: todo list from inventory DONE: move tasks here when done NOT DONE: move here what was not done STANDUP: yesterday, today, what did I learn POMOSPECTIVE: how the PT is doing INTERRUPTS: record interruptions
Slide 19: Today Todo Workflow Start the Pomodoro Create new Todo Today Sheet Session Standup Pomospective Compute available pomodoros Compare total to yesterday’s capacity Bring-in not done tasks from last session Bring-in tasks from Inventory Reconsider priorities after each Pomodoro
Slide 20: Pomodoro Practices Session Stand-up Different from the team stand-up Main goals for the day @today, @yesterday, @learned Other project related tags Re-establish focus and effort
Slide 21: Pomodoro Practices Pomospective Any noticeable under/over estimate? What went good/bad about the technique? Am I respecting breaks? Can interruptions be avoided? Is rhythm established?
Slide 22: Todo Today Folders Folders by year, month Actual file name: <day>_<pair>.txt
Slide 23: ice ct ra sP t’ Le ith s w do To ay od T
Slide 24: Execution Workflow Start the Pomodoro Check priorities, shuffle tasks if necessary Execute task Mark one Pomodoro done for task Short Break, (long break after 4P) Wash, Rinse, Repeat
Slide 25: e tim oro od om P
Slide 26: Pomodoro Workflows Inventory Workflow Session Workflow Execution Workflow New Task Workflow Interruption Workflow
Slide 27: What If? sk Ta ed ct pe ex Un
Slide 28: New Task Workflow Always close current task Never jump to new task Append new task to INBOX Re-prioritize on next Pomodoro
Slide 29: What If? te In ns tio rup r
Slide 30: Interrupt Workflow Protect the Pomodoro Inform: current task and schedule Negotiate: based on priorities Reschedule: move the interruption later on
Slide 31: Pomodoro for software projects
Slide 32: The Pomodoro Domain Inception to user stories Story selection for current iteration Developers volunteer for stories pomodoro domain starts here Developers fill out the Inventory Sheet Developers start their first Pomodoro
Slide 33: Process Independent The Pomodoro influence is at the task execution level It does not mandate programming techniques It does not alter the software process affects the focus/relax cycle improves estimates precision improves productivity
Slide 34: Multiple Inventories One each pair/developer OR each workstation The story owner is responsible to maintain the inventory OR whoever sits at the workstation It contains tasks from the current story It contains tasks from QA stories It contains other technical tasks
Slide 35: Inventory: iteration One SIGNUP NEWSLETTER: - @signup create form page 6 - @signup handle validation errors 4 - @signup form to create a new newsletter 6 (SPLIT) - @signup async process to send emails at intervals 6 (SPLIT) - @signup confirmation page 3 SPIKES: - @spikes how to create async process with framework X? 3 INBOX:
Slide 36: Inventory Iteration Two SHOW TWEETS: - @tweet setup twitter account for procuct 1 (NEW) - @tweet async process to download tweets locally 5 (SPLIT) - @tweet create tweets sidebar on the page 4 (SPLIT) - @tweet retrieve list of tweets from file 2 (SPLIT) SIGNUP NEWSLETTER: - @signup more specific error messages 2 (QA) [...]
Slide 37: Today Todo 8.30am SCHEDULE: 8am => 12pm, 1pm => 5pm PLANNED 14 - @signup create form page 6 - @signup handle validation errors 4 - @signup form to create a new newsletter DONE: - @planning 1 => 1 NOT DONE: STANDUP: - @today should be able to close form POMOSPECTIVE: - @good think positive planning 14 solid pomodoros INTERRUPTS: notice the total here: 6 what’s wrong?
Slide 38: Today Todo 1pm SCHEDULE: 8am => 12pm, 1pm => 5pm PLANNED 14: - @signup handle validation errors 4 => 1 - @signup form to create a new newsletter 6 DONE: - @signup create form page 6 => 5 NOT DONE: / STANDUP: [......] overestimated
Slide 39: Today Todo 5pm SCHEDULE: 8am => 12pm, 1pm => 5pm PLANNED 14: DONE 12: - @planning 1 => 1 - @signup create form page 6 => 5 - @signup handle validation errors 4 => 6 NOT DONE: - @signup handle validation errors 4 => 6 - @signup form to create a new newsletter 6 overall a productive day underestimate and still WIP INTERRUPTS: - @external unexpected call from customer, voided
Slide 40: Today Todo Next Day SCHEDULE: 10 am => 12pm, 1pm => 5pm company gathering day PLANNED 10: - @signup handle validation errors 2 re-estimate from yesterday - @signup form to create a new newsletter 6 not done yesterday - @signup confirmation page 3 new from inventory DONE: NOT DONE: STANDUP: - @yesterday done form for submission - @today completing form related stuff like validation POMOSPECTIVE: - @good productivity yesterday - @bad understimated the task
Slide 41: Team Integration Multiple Pomodoros One Pomodoro each pair OR one Pomodoro per workstation Start/stop negotiation Flexibility
Slide 42: Coach - ScrumMaster Interrupt Shield Protects Pomodoros for the whole team Effective if team is co-located Again inform, negotiate, reschedule
Slide 43: Team Standup Use Pomospective and Session Standup More effective team standup Ready for Session Workflow
Slide 44: Ping Pong Pair Pomo First Pomodoro: first developer writes tests, second developer writes code Next Pomodoro: Invert roles
Slide 45: Collective Breaks Decide target time (i.e. lunch) Allow 15 mins synchronization Do not start new Pomodoro if now = (target-time - 15 mins)
Slide 46: Break Room Don’t bug the team if you’re on a break Use another room or the kitchen A couch is great for micro-naps
Slide 47: Metrics Pomodoro effort over time Pomodoro estimate accuracy Pomodoro scattering Pomodoro by tag
Slide 48: Collecting the data Manual insert from paper or file to Excel Mash-up of scripts and tools Dedicated software still missing A few examples
Slide 52: Conclusions
Slide 53: A measure for quality 8 hours != 16P Measuring in Pomodoros is like measuring the quality work 12P ~ 8-10 hours e aybe m or m Include quality when exporting from Pomodoros to Hours
Slide 54: Breaks First Class Citizens A commitment to your brain Breaks are planned as well as work Establish Rhythm Steady and sustainable pace Confidence Big project connected to short term cycle
Slide 55: Mikrokosmos A Pomodoro is a 30 mins project Frequent changes, tracking, estimation, focus, interaction, scope, negotiation etc. Rule the Pomodoro to rule them all! User Stories, Tasks, Iterations, Projects, Everything!
Slide 56: Results Task execution under control Learn how to improve High quality and consistent work Better estimates Feeling of accomplishment Consistent level of energy
Slide 57: Resources The Pomodoro Technique: http://www.pomodorotechnique.com The Pomodoro Book: www.pomodoro-book.com The original paper: http://www.pomodorotechnique.com Keeptempo: www.keeptempo.com Pomodori, my timer: http://reborg.github.com/pomodori Pomodoro, another good timer: http://pomodoro.ugolandini.com/ Special thanks to Ana Calliari for her wonderful Callani font http://www.anacalliari.com/
Slide 58: Thank you