• Orit Hazzan
  • Yael Dubinsky
Part of the Undergraduate Topics in Computer Science book series (UTICS)


Time is addressed differently by different people and cultures; for example, in western culture culture, time is mainly associated with financial profit, i.e., “Time is money.” Time plays a special role in software engineering: the project schedule should be met, the product should be delivered on time, teammates should complete their tasks on time, and so on. This chapter deals with how the time concept is expressed in software engineering in general and in agile software development in particular. In agile software development time is boxed for each activity, and when needed, instead of “moving” deadlines, the scope is changed according to customer priorities. This conception is supported by agile software development methods in different ways that not only enable one to work at a sustainable pace, but that also result in high quality products.


Software Project Agile Method Development Task Planning Session Pair Programming 
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.


  1. Beck KBeck K (2000) Extreme programming explained: embrace change, 1st ed. Addison-Wesley, Reading, MAGoogle Scholar
  2. Beck KBeck K, Fowler MFowler M (2000) Planning extreme programming. Addison-Wesley, Reading, MAGoogle Scholar
  3. Beck KBeck K, Andres CAndres C (2005) Extreme programming explained: embrace change, 2nd ed. Addison-Wesley, Reading, MAGoogle Scholar
  4. Boehm BBoehm B (1981) Software engineering economics. Prentice-Hall, Englewood Cliffs, NJGoogle Scholar
  5. Boehm BBoehm B, Horowitz EHorowitz E, Madachy RMadachy R, Reifer DReifer D, Clark BKClark BK, Steece BSteece B, Brown AWBrown AW, Chulani SChulani S, Abts CAbts C (2000) Software cost estimation with COCOMO II. Prentice-Hall, Englewood Cliffs, NJGoogle Scholar
  6. Brooks FPBrooks FP (1975, 1995) The mythical man-month—essays on software engineering. Addison-Wesley, Reading, MAGoogle Scholar
  7. Cockburn ACockburn A, Williams LWilliams L (2000) The costs and benefits of pair programming. 1st international conference on extreme programming and agile processes in software engineering. ItalyGoogle Scholar
  8. Cohn MCohn M (2006) Agile estimating and planning. RC Martin Series, Prentice Hall PTR, Englewood CliffsGoogle Scholar
  9. Covey SCovey S, Merrill ARMerrill AR, Merrill RRMerrill RR (1994) First things first. Free Press, New YorkGoogle Scholar
  10. Dubinsky Y, Yaeli A, Feldman Y, Zarpas E, Nechushtai G (2008) Governance of Software Development: The Transition of Agile Scenario, IT Governance and Service Management Frameworks and Adaptations, Idea Group Publishing, Information Science Publishing, IRM pressGoogle Scholar
  11. Hazzan O, Dubinsky Y (2005) Clashes between culture and software development methods: the case of the Israeli hi-tech industry and extreme programming. Proceedings of the agile conference, IEEE computer society, Denver, CO, pp 59–69Google Scholar
  12. Hazzan O, Dubinsky Y (2007) The software engineering timeline: a time management perspective. Proceedings of the IEEE international conference on software—science, technology & engineering, Herzelia, Israel, pp 95–103Google Scholar
  13. Hughes BHughes B, Cotterell M Cotterell M (2002) Software project management. McGraw-Hill, New YorkGoogle Scholar
  14. Kemerer CFKemerer CF (1987) An empirical validation of software cost estimation models. Communications of the ACMGoogle Scholar
  15. Reifer DJReifer DJ (2002) How to get the most out of XP/agile methods. Proceedings of the second XP universe and first agile universe conference, Chicago, IL, pp 185–196Google Scholar
  16. Schuh PSchuh P (2004) Integrating agile development in the real world. Charles River MediaGoogle Scholar
  17. SEISEI (2001) Standard CMMI appraisal method for process improvement (SCAMPISM). Software Engineering InstituteGoogle Scholar
  18. Standish group chaos report Standish Group (1994) chaos_1994_2.php
  19. Tomayko JTomayko J, Hazzan O (2004) Human aspects of software engineering. Charles River MediaGoogle Scholar
  20. Van Vliet HVan Vliet H (2000) Software engineering—principles and practices. WileyGoogle Scholar

Copyright information

© Springer-Verlag London 2008

Authors and Affiliations

  • Orit Hazzan
    • 1
  • Yael Dubinsky
    • 2
  1. 1.Department of Education in Technology and Science TechnionIsrael Institute of TechnologyHaifaIsrael
  2. 2.Department of Computer Science TechnionIsrael Institute of TechnologyHaifaIsrael

Personalised recommendations