Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
The Pomodoro Technique (#phpbnl13)
Transcript of The Pomodoro Technique (#phpbnl13)
(scales up to 3-4 in development) Done in Pomodoros A few integer Pomodoros Lower risk Easy benchmarks Don't impose 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 They are by definition unexpected Hook points for questions The PT in 60 seconds Metaphors: Agile methods, hardware and software Easy, no technology Stop procrastination Small successes not too small Don't use it for Free time Leisure tasks Less than 25'
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. just do a Pomodoro, you'll get the momentum to do 4 not too large Only a Pomodoro can be lost each time record re-estimate, no external factors References The (free) PT book The Agile concepts are all documented in 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 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 Giorgio Sironi Developer @ Onebip Computer Engineer 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? to end of Pomodoro (quick) to a specialized Pomodoro (long) You do not feel time is passing Velocity? Sprint backlog? WIP? Time-boxing of iterations? Preventing death marches Feedback over forced breaks N Pomodoros meetings,
stand-up meeting (15') Backlog? Manager's schedule Context switches Pay by SIM or DSL