Skip to main content
SpringerLink
Log in
Book cover

Software Project Management in a Changing World pp 277–300Cite as

Agile Project Management

  • Chapter
  • First Online:

Abstract

Agile software development represents a new approach for planning and managing software projects. It puts less emphasis on up-front plans and strict control and relies more on informal collaboration, coordination, and learning. This chapter provides a characterization and definition of agile project management based on extensive studies of industrial projects. It explains the circumstances behind the change from traditional management with its focus on direct supervision and standardization of work processes, to the newer, agile focus on self-managing teams, including its opportunities and benefits, but also its complexity and challenges. The main contribution of the chapter is the four principles of agile project management: minimum critical specification, autonomous teams, redundancy, and feedback and learning.

This is a preview of subscription content, log in via an institution.

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   54.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    www.prince-officialsite.com

  2. 2.

    http://agilemanifesto.org/

  3. 3.

    A kanban is a visual card system for organizing production according to demand, central in lean production.

  4. 4.

    A burndown chart shows the estimated remaining work in an iteration, and is updated daily when teams use the Scrum development process.

References

  • Abramson P, Oza N, Siponen MT (2010) Agile software development methods: a comparative review. In: Dingsøyr T, Dybå T, Moe NB (eds) Agile software development. Current research and future directions. Springer, Berlin, pp 31–59

    Google Scholar 

  • Argyris C, Schön DA (1996) On organizational learning II: theory method and practise. Addison Wesley, Reading, MA

    Google Scholar 

  • Augustine S, Payne B, Sencindiver F, Woodcock S (2005) Agile project management: steering from the edges. Commun ACM 48(12):85–89

    Article  Google Scholar 

  • Aurum A, Wohlin C, Porter A (2006) Aligning software project decisions: a case study. Int J Softw Eng Knowl Eng 16(6):795–818

    Article  Google Scholar 

  • Bazerman MH, Giuliano T, Appelman A (1984) Escalation of commitment in individual and group decision making. Organ Behav Hum Perform 33:141–152

    Article  Google Scholar 

  • Besner C, Hobbs B (2008) Project management practice, generic or contextual: a reality check. Proj Manage J 39:16–33

    Article  Google Scholar 

  • Birk A, Dingsøyr T, Stålhane T (2002) Postmortem: never leave a project without it. IEEE Softw 19(3):43–45, Special issue on knowledge management in software engineering

    Article  Google Scholar 

  • Bjørnson FO, Dingsøyr T (2008) Knowledge management in software engineering: a systematic review of studied concepts and research methods used. Info Softw Technol 50(11):1055–1168. doi:10.1016/j.infsof.2008.03.006

    Article  Google Scholar 

  • Cohen SG, Bailey DE (1997) What makes teams work: group effectiveness research from the shop floor to the executive suite. J Manage 23(3):239–290

    Google Scholar 

  • Conboy K, Coyle S, Wang X, Pikkarainen M (2011) People over process: key challenges in agile development. IEEE Softw 28(4):48–57

    Article  Google Scholar 

  • Constantine LL (1993) Work organization: paradigms for project management and organization. Commun ACM 36(10):35–43

    Article  Google Scholar 

  • De Meyer A, Loch CH, Pich MT (2002) Managing project uncertainty: from variation to chaos. MIT Sloan Management Review Winter 2002:60–67

    Google Scholar 

  • Derby E, Larsen D (2006) Agile retrospectives: making good teams great. The Pragmatic Bookshelf, Raleigh, NC

    Google Scholar 

  • Dingsøyr T (2005) Postmortem reviews: purpose and approaches in software engineering. Info Softw Technol 47(5):293–303

    Article  Google Scholar 

  • Dingsøyr T, Lindsjørn Y (2013) Team performance in agile development teams: findings from 18 focus groups. In: Baumeister H, Weber B (eds) Agile processes in software engineering and extreme programming, vol 149. Springer, Berlin, pp 46–60

    Google Scholar 

  • Dingsøyr T, Dybå T, Moe NB (2010) Agile software development: current research and future directions. Springer, Berlin

    Book  Google Scholar 

  • Dingsøyr T, Nerur S, Balijepally V, Moe NB (2012) A decade of agile methodologies: towards explaining agile software development. J Syst Softw 85(6):1213–1221. doi:10.1016/j.jss.2012.02.033

    Article  Google Scholar 

  • Dybå T (2000) Improvisation in small software organizations. IEEE Softw 17(5):82–87

    Article  Google Scholar 

  • Dybå T (2011) Special section on best papers from XP2010. Info Softw Technol 53(5):507–508

    Article  Google Scholar 

  • Dybå T, Dingsøyr T (2008) Empirical studies of agile software development: a systematic review.Info Softw Technol 50(9–10):833–859. doi:10.1016/j.inf-sof.2008.01.006

  • Dybå T, Maiden N, Glass R (2014) The reflective software engineer: reflective practice. IEEE Softw 31(4):32–36

    Article  Google Scholar 

  • Fægri TE (2010) Adoption of team estimation in a specialist organizational environment. In: Sillitti A, Martin A, Wang X, Whitworth E (eds) 11th international conference on agile software development, Trondheim, Norway, 1–4 June 2010. Springer, pp 28–42

    Google Scholar 

  • Fægri TE, Dybå T, Dingsøyr T (2010) Introducing knowledge redundancy practice in software development: experiences with job rotation in support work. Info Softw Technol 52(10):1118–1132

    Article  Google Scholar 

  • Faraj S, Sambamurthy V (2006) Leadership of information systems development projects. IEEE Transact Eng Manage 53(2):238–249

    Article  Google Scholar 

  • Garel G (2013) A history of project management models: from pre-models to the standard models. Int J Proj Manage 31(5):663–669

    Article  MathSciNet  Google Scholar 

  • Guzzo RA, Dickson MW (1996) Teams in organizations: recent research on performance and effectiveness. Annu Rev Psychol 47:307–338

    Article  Google Scholar 

  • Hackman JR (1986) The psychology of self-management in organizations. In: Pallack MS, Perloff RO (eds) Psychology and work: productivity, change, and employment. American Psychological Association, Washington, DC

    Google Scholar 

  • Hewitt B, Walz D (2005) Using shared leadership to foster knowledge sharing in information systems development projects. In: Walz D (ed) Proceedings of the 38th Hawaii international conference on system sciences (HICCS), pp 1–5

    Google Scholar 

  • Hoare CAR (1984) Programming: sorcery or science? IEEE Softw 1(2):5–16

    Article  Google Scholar 

  • Hoegl M, Parboteeah P (2006) Autonomy and teamwork in innovative projects. Hum Resour Manage 45(1):67

    Article  Google Scholar 

  • Humphrey WS (1989) Managing the software process. Addison-Wesley, Reading, MA

    Google Scholar 

  • Keil M, Mann J, Rai A (2000) Why software projects escalate: An empirical analysis and test of four theoretical models. MIS Q 24(4):631–664

    Article  Google Scholar 

  • Kerth NL (2001) Project retrospectives: a handbook for team reviews. Dorset House Publishing, New York

    Google Scholar 

  • Kirkman BL, Rosen B (1999) Beyond self-management: antecedents and consequences of team empowerment. Acad Manage J 42(1):58–74

    Article  Google Scholar 

  • Kozlowski SWJ, Bell BS (2003) Work groups and teams in organizations In: Borman WC, Ilgen DR, Klimoski RJ (ed) Handbook of psychology (vol 12): industrial and organizational psychology. Wiley-Blackwell, New York, pp 333–375

    Google Scholar 

  • Kozlowski SWJ, Ilgen DR (2006) Enhancing the effectiveness of work groups and teams. Psychol Sci Public Inter 7:77–124

    Google Scholar 

  • Kransdorff A (1996) Using the benefits of hindsight - the role of post-project analysis. Learn Organ 3(1):11–15

    Article  Google Scholar 

  • Lehman MM (1989) Uncertainty in computer applications and its control through the engineering of software. Softw Maint Res Pract 1(1):3–27

    Article  Google Scholar 

  • Lipshitz R, Klein G, Orasanu J, Salas E (2001) Taking stock of naturalistic decision making. J Behav Decis Mak 14(5):331–352

    Article  Google Scholar 

  • Lynn GS, Skov RB, Abel KD (1999) Practices that support team learning and their impact on speed to market and new product success. J Prod Innov Manag 16:439–454

    Article  Google Scholar 

  • Menke MM (1997) Managing R&D for competitive advantage. Res Technol Manage 40(6):40–42

    Google Scholar 

  • Meso P, Troutt MD, Rudnicka J (2002) A review of naturalistic decision making research with some implications for knowledge management. J Knowl Manage 6(1):63–73

    Article  Google Scholar 

  • Moe NB, Dingsøyr T, Dybå T (2008) Understanding self-organizing teams in agile software development. In: 19th Australian conference on software engineering, pp 76–85

    Google Scholar 

  • Moe NB, Dingsøyr T, Dybå T (2009) Overcoming barriers to self-management in software teams. IEEE Softw 26(6):20–26

    Article  Google Scholar 

  • Moe NB, Dingsøyr T, Dybå T (2010) A teamwork model for understanding an agile team: a case study of a Scrum project. Info Softw Technol 52(5):480–491

    Article  Google Scholar 

  • Moe NB, Aurum A, Dybå T (2012) Challenges of shared decision-making: a multiple case study of agile software development. Info Softw Technol 54(8):853–865

    Article  Google Scholar 

  • Molokken-Ostvold K, Haugen NC, Benestad HC (2008) Using planning poker for combining expert estimates in software projects. J Syst Softw 81(12):2106–2117. doi:10.1016/j.jss.2008.03.058

    Article  Google Scholar 

  • Morgan G (2006) Images of organizations. Sage, Thousand Oaks, CA

    Google Scholar 

  • Nerur S, Balijepally V (2007) Theoretical reflections on agile development methodologies - the traditional goal of optimization and control is making way for learning and innovation. Commun ACM 50(3):79–83

    Article  Google Scholar 

  • Nerur S, Mahapatra R, Mangalaraj G (2005) Challenges of migrating to agile methodologies. Commun ACM 48(5):72–78

    Article  Google Scholar 

  • Outi S (2006) Enabling software process improvement in agile software development teams and organisations. VTT Publications, Espoo

    Google Scholar 

  • Pearce CL (2004) The future of leadership: combining vertical and shared leadership to transform knowledge work. Acad Manage Exec 18(1):47–57

    Article  Google Scholar 

  • Pich MT, Loch CH, De Meyer A (2002) On uncertainty, ambiguity, and complexity in project management. Manage Sci 48(8):1008–1023

    Article  MATH  Google Scholar 

  • Raelin JA (2001) Public reflection as the basis of learning. Manage Learn 32(1):11–30

    Article  Google Scholar 

  • Rittel HWJ, Webber MM (1973) Dilemmas in a general theory of planning. Policy Sci 4:155–169

    Article  Google Scholar 

  • Schwaber K, Beedle M (2001) Agile software development with Scrum. Prentice Hall, Upper Saddle River

    Google Scholar 

  • Sharp H, Robinson H (2010) Three ‘C’s of agile practice: collaboration, co-ordination and communication. In: Dingsøyr T, Dybå T, Moe NB (eds) Agile software development: current research and future directions. Springer, Berlin, p 13

    Google Scholar 

  • Sharp H, Robinson H, Segal J, Furniss D (2006) The role of story cards and the wall in Xp teams: a distributed cognition perspective. In: Agile. Minneapolis, MN. IEEE Computer Society, pp 65–75

    Google Scholar 

  • Šmite D, Moe NB, Ågerfalk PJ (2010) Agility across time and space: implementing agile methods in global software projects. Springer, Berlin

    Google Scholar 

  • Staw B (1976) Knee-deep in the big muddy: a study of escalating commitment to a chosen course of action. Organ Behav Hum Perform 16(1):27–44

    Article  Google Scholar 

  • Stray VG, Moe NB, Dingsøyr T (2011) Challenges to teamwork: a multiple case study of two agile teams. In: Sillitti A, Hazzan O, Bache E, Albaladejo X (eds) Agile processes in software engineering and extreme programming, vol 77. Lecture Notes in Business Information Processing, pp 146–161

    Google Scholar 

  • Stray VG, Moe NB, Dybå T (2012) Escalation of commitment: a longitudinal case study of daily meetings. In: Wohlin C (ed) Agile processes in software engineering and extreme programming. Lecture Notes in Business Information Processing. Springer, Berlin, pp 153–167. doi:10.1007/978-3-642-30350-0_11

  • Takeuchi H, Nonaka I (1986) The new product development game. Harv Bus Rev 64:137–146

    Google Scholar 

  • Trist E (1981) The evolution of socio-technical systems: a conceptual framework and an action research program. Occasional paper no 2. Ontario quality of working life centre, Toronto, ON

    Google Scholar 

  • Trist E, Bamforth KW (1951) Some social and psychological consequences of the longwall method of coal—getting. Hum Relat 4(1):3–38. doi:10.1177/001872675100400101

    Article  Google Scholar 

  • von Krogh G, Ichijo K, Nonaka I (2000) Enabling knowledge creation. Oxford University Press, New York

    Book  Google Scholar 

  • Whyte G (1993) Escalating commitment in individual and group decision making: a prospect theory approach. Organ Behav Hum Decis Process 54(3):430–455

    Article  Google Scholar 

  • Woodfield SN (1979) An experiment on unit increase in problem complexity. IEEE Trans Softw Eng 5(2):76–79

    Article  MATH  Google Scholar 

  • Yeh RT (1991) System development as a wicked problem. Int J Softw Eng Knowl Eng 1(2):117–130

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

  1. SINTEF, Trondheim, Norway

    Tore Dybå, Torgeir Dingsøyr & Nils Brede Moe

Authors
  1. Tore Dybå
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Torgeir Dingsøyr
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Nils Brede Moe
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Tore Dybå .

Editor information

Editors and Affiliations

  1. University of Calgary, Calgary, Alberta, Canada

    Günther Ruhe

  2. Blekinge Institute of Technology, Karlskrona, Sweden

    Claes Wohlin

Rights and permissions

Reprints and permissions

Copyright information

© 2014 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Dybå, T., Dingsøyr, T., Moe, N.B. (2014). Agile Project Management. In: Ruhe, G., Wohlin, C. (eds) Software Project Management in a Changing World. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-55035-5_11

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-55035-5_11

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-55034-8

  • Online ISBN: 978-3-642-55035-5

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation