Software Project Management: Setting the Context

  • Günther RuheEmail author
  • Claes Wohlin


This chapter is designed as the introduction to the book. It provides the motivation for studying software project management as a response to the increasing variety of software development methodologies. The chapter characterizes software projects and presents ten knowledge areas in software project management. This body of knowledge is described in the software edition of the Project Management Body of Knowledge (PMBOK). The chapters of the book are classified in terms of their contribution to these knowledge areas.

The chapter also discusses the multidisciplinary nature of the project management discipline. Based on some predicted trends for the future of software engineering, a prediction on the future of software project management is given. Finally, an overview of the content and structure of the whole book is presented.


Project Management Software Project Portfolio Management Stakeholder Management Virtual Team 
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. Basili VR, Shull F, Lanubile F (1999) Building knowledge through families of experiments. IEEE Trans Softw Eng 25(4):456–473CrossRefGoogle Scholar
  2. Boehm BW (1981) Software engineering economics. Prentice Hall, Englewood Cliffs, NJzbMATHGoogle Scholar
  3. Boehm BW (2006a) Some future trends and implications for systems and software engineering processes. Syst Eng 9(1):1–19CrossRefGoogle Scholar
  4. Boehm BW (2006b) A view of 20th and 21st century software engineering. In: 28th international conference on software engineering, New York, pp 12–29Google Scholar
  5. Boehm BW, Lane JA (2010) Evidence-based software processes. In: International conference on software process, ICSP 2010. LNCS, vol 6195. Springer, Berlin, pp 62–73Google Scholar
  6. Brooks FP (1987) No silver bullet: essence and accidents of software engineering. IEEE Comput 20(4):10–19CrossRefMathSciNetGoogle Scholar
  7. Goff SA (2009) Visions for the project management software industry. In: Cleland D, Bidanda B (eds) Project management circa 2025. Project Management Institute, Athabasca University, Newtown Square, PA, pp 1–15Google Scholar
  8. Hassan AE (2013) Software analytics: going beyond developers. IEEE Softw 30(4):53CrossRefGoogle Scholar
  9. Kruchten P (2011) The frog and the octopus – a model of software development. CSI Commun 35(4):12–15Google Scholar
  10. Kwak YH, Anbari FT (2008) Impact on project management of allied disciplines: trends and future of project management practices and research. Project Management Institute, Newtown Square, PAGoogle Scholar
  11. Larman C, Basili VR (2003) Iterative and incremental development: a brief history. Computer 36(6):47–56CrossRefGoogle Scholar
  12. Nidiffer KE, Dolan D (2005) Evolving distributed project management. IEEE Softw 22(5):63–72CrossRefGoogle Scholar
  13. Novais RL, Torres A, Mendes TS, Mendonça M, Zazworka N (2013) Software evolution visualization: a systematic mapping study. Inf Softw Technol 55:1860–1883CrossRefGoogle Scholar
  14. Pereira AM, Goncalves RQ, von Wangenheim CG, Buglione L (2013) Comparison for open source tools for project management. Int J Softw Eng Knowl Eng 23:189–209CrossRefGoogle Scholar
  15. PMI (2013a) A guide to the project management body of knowledge (PMBOK® guide), 5th edn. Project Management Institute, Newtown Square, PAGoogle Scholar
  16. PMI (2013b) Software Extension to the PMBOK Guide, 5th edn. Project Management Institute, IEEE Computer Society, Newtown Square, PAGoogle Scholar
  17. PMI (2013c) The Standard for Portfolio Management, 3rd edn. Project Management Institute, Newtown Square, PAGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2014

Authors and Affiliations

  1. 1.University of CalgaryCalgaryCanada
  2. 2.Blekinge Institute of TechnologyKarlskronaSweden

Personalised recommendations