Turning Time from Enemy into an Ally Using the Pomodoro Technique

  • Xiaofeng WangEmail author
  • Federico Gobbo
  • Michael Lane


Time is one of the most important factors dominating agile software development processes in distributed settings. Effective time management helps agile teams to plan and monitor the work to be performed, and create and maintain a fast yet sustainable pace. The Pomodoro Technique is one promising time management technique. Its application and adaptation in Sourcesense Milan Team surfaced various benefits, challenges and implications for distributed agile software development. Lessons learnt from the experiences of Sourcesense Milan Team can be useful for other distributed agile teams to turn time from enemy into an ally.


Team Member Software Development Process User Story Software Development Project Agile Software Development 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Ågerfalk, P. J., Fitzgerald, B., Holmstom, H., Lings, B., Lundell, B., & Ó Conchúir, E. (2005). A framework for considering opportunities and threats in distributed software development. In Proceedings of the international workshop on distributed software development (DiSD 2005) (pp. 47–61), Paris, 29 August 2005. Vienna: Austrian Computer Society. Google Scholar
  2. 2.
    Agile Manifesto (2001)., last visit Nov. 2009.
  3. 3.
    Beck, K. (2000). Extreme programming explained: Embrace change (1st ed.). Upper Saddle River: Addison-Wesley. Google Scholar
  4. 4.
    Brooks, F. P. (1975). The mythical man-month—Essays on software engineering. Upper Saddle River: Addison-Wesley. Google Scholar
  5. 5.
    Cirillo, F. The pomodoro technique (XPLabs Technical Report version 1.3). English Version. Published 15 Jun 2007.
  6. 6.
    Cramton, C. (2001). The mutual knowledge problem and its consequences for dispersed collaboration. Organization Science, 12(3), 346–371. CrossRefGoogle Scholar
  7. 7.
    Espinosa, J. A., Cummings, J. N., Wilson, J. M., & Pearce, B. M. (2003). Team boundary issues across multiple global firms. Journal of Management Information Systems, 19(4), 157–190. Google Scholar
  8. 8.
    Grinter, R. E., Herbsleb, J. D., & Perry, D. E. (1999). The geography of coordination: Dealing with distance in R&D work. In Proc. int’l ACM SIGGROUP conf. supporting group work (GROUP ’99) (pp. 306–315). New York: ACM Press. CrossRefGoogle Scholar
  9. 9.
    Gobbo, F., & Vaccari, M. (2008). The pomodoro technique for sustainable pace in extreme programming teams. In Proceedings of XP2008, Limerick, June 2008. Google Scholar
  10. 10.
    Hazzan, O., & Dubinsky, Y. (2007). The software engineering timeline: A time management perspective. In Software-science, technology & engineering, 2007. SwSTE 2007. IEEE international conference on (pp. 95–103). Herzlia, Israel. Google Scholar
  11. 11.
    Humphrey, W. S. (2000). Introduction to the team software process. SEI series in software engineering. Upper Saddle River: Addison-Wesley. Google Scholar
  12. 12.
    PMI (2004). A guide to the project management body of knowledge (PMBOK). Google Scholar
  13. 13.
    Sarker, S., & Sahay, S. (2004). Implications of space and time for distributed work: An interpretive study of US-Norwegian systems development teams. European Journal of Information Systems, 13(1), 3–20. CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  1. 1.Lero, The Irish Software Engineering Research CentreLimerickIreland
  2. 2.DICOM Dipartimento di Informatica e ComunicazioneUniversity of InsubriaVareseItaly
  3. 3.Computer Science and Information SystemsUniversity of LimerickLimerickIreland

Personalised recommendations