Advertisement

Perspectives on Productivity and Delays in Large-Scale Agile Projects

  • Deepika Badampudi
  • Samuel A. Fricker
  • Ana M. Moreno
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 149)

Abstract

Many large and distributed companies run agile projects in development environments that are inconsistent with the original agile ideas. Problems that result from these inconsistencies can affect the productivity of development projects and the timeliness of releases. To be effective in such contexts, the agile ideas need to be adapted. We take an inductive approach for reaching this aim by basing the design of the development process on observations of how context, practices, challenges, and impacts interact. This paper reports the results of an interview study of five agile development projects in an environment that was unfavorable for agile principles. Grounded theory was used to identify the challenges of these projects and how these challenges affected productivity and delays according to the involved project roles. Productivity and delay-influencing factors were discovered that related to requirements creation and use, collaboration, knowledge management, and the application domain. The practitioners’ explanations about the factors’ impacts are, on one hand, a rich empirical source for avoiding and mitigating productivity and delay problems and, on the other hand, a good starting point for further research on flexible large-scale development.

Keywords

Inductive process improvement large-scale agile development grounded theory 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Abrahamsson, P., et al.: Agile software development methods: Review and analysis, vol. 478. VTT Publications, Espoo (2002)Google Scholar
  2. 2.
    Basili, V.R., Briand, L., Melo, W.: How Reuse Influences Productivity in Object-Oriented Systems. Communications of the ACM 39(10), 104–116 (1996)CrossRefGoogle Scholar
  3. 3.
    Blackburn, J., Scudder, G., Van Wassenhove, L.: Improving Speed and Productivity of Software Development: A Global Survey of Software Developers. IEEE Transactions on Software Engineering 22(12), 875–885 (1996)CrossRefGoogle Scholar
  4. 4.
    Boehm, B., Turner, R.: Management Challenges to Implementing Agile Processes in Traditional Development Organizations. IEEE Software 22(5), 30–39 (2005)CrossRefGoogle Scholar
  5. 5.
    Briand, L., El Emam, K., Melo, W.: An inductive method for software process improvement: concrete steps and guidelines. In: El Emam, K., Madhavji, N. (eds.) Elements of Software Process Assessment & Improvement. Wiley-IEEE Computer Society (2001)Google Scholar
  6. 6.
    Bruckhaus, T., et al.: The Impact of Tools on Software Productivity. IEEE Software 13(5), 29–38 (1996)CrossRefGoogle Scholar
  7. 7.
    Cain, J., McCrindle, R.: An Investigation into the Effects of Code Coupling on Team Dynamics and Productivity. In: 26th Annual International Computer Software and Applications Conference (COMPSAC 2002), Oxford, UK (2002)Google Scholar
  8. 8.
    Cardozo, E., et al.: SCRUM and productivity in software projects: a systematic literature review. In: 14th International Conference on Evaluation and Assessment in Software Engineering (EASE 2010), Keele, UK (2010)Google Scholar
  9. 9.
    Chow, T., Cao, D.-B.: A survey study of critical success factors in agile software projects. Journal of Systems and Software 81(6), 961–971 (2007)CrossRefGoogle Scholar
  10. 10.
    CMMI Product Team, CMMI for Development, Version 1.3. Carnegie Mellon University (2010) Google Scholar
  11. 11.
    Cohn, M., Ford, D.: Introducing an Agile Process to an Organization. IEEE Computer 36(6), 74–78 (2003)CrossRefGoogle Scholar
  12. 12.
    Damian, D., et al.: Requirements payoff: An empirical study of the relationship between requirements practice and software productivity, quality and risk management. University of Victoria (2003) Google Scholar
  13. 13.
    Fricker, S., et al.: Handshaking with Implementation Proposals: Negotiating Requirements Understanding. IEEE Software 27(2), 72–80 (2010)CrossRefGoogle Scholar
  14. 14.
    Fricker, S., Schumacher, S.: Release Planning with Feature Trees: Industrial Case. In: Regnell, B., Damian, D. (eds.) REFSQ 2011. LNCS, vol. 7195, pp. 288–305. Springer, Heidelberg (2012)CrossRefGoogle Scholar
  15. 15.
    Garcia, R., Calantone, R.: A Critical Look at Technological Innovation Typology and Innovativeness Terminology: A Literature Review. The Journal of Product Innovation Management 19(2), 110–132 (2002)CrossRefGoogle Scholar
  16. 16.
    Garvin, D.: Building a Learning Organization. Harvard Business Review 71(4), 78–91 (2000)Google Scholar
  17. 17.
    Genuchten, V.: Why is Software Late? An Empirical Study of Reasons For Delay in Software Development. IEEE Transactions on Software Engineering 17(6), 582–590 (1991)CrossRefGoogle Scholar
  18. 18.
    Herbsleb, J., Moitra, D.: Global Software Development. IEEE Software 18(2), 16–20 (2001)CrossRefGoogle Scholar
  19. 19.
    Hoda, R., et al.: Agility in Context. In: OOPSLA/SPLASH 2010, Reno/Tahoe, Nevada, USA (2010)Google Scholar
  20. 20.
    Karlsson, L., et al.: Requirements Engineering Challenges in Market-Driven Software Development - An Interview Study with Practitioners. Information and Software Technology 49(6), 588–604 (2007)CrossRefGoogle Scholar
  21. 21.
    Kruchten, P.: Scaling Down Large Projects to Meet the Agile Sweet Sport. In: IBM developerWorks. IBM (2004)Google Scholar
  22. 22.
    Leffingewell, D.: Scaling Software Agility: Best Practices for Large Enterprises. Addison-Wesley (2007)Google Scholar
  23. 23.
    Lindvall, M., et al.: Agile Software Development in Large Organizations. IEEE Computer 37(12), 26–34 (2004)CrossRefGoogle Scholar
  24. 24.
    Lynn, G., Morone, J., Paulson, A.: Marketing and Discontinuous Innovation. California Management Review 38(3), 8–37 (1996)CrossRefGoogle Scholar
  25. 25.
    Nerur, S., Mahapatra, R.K., Mangalaraj, G.: Challenges of Migrating to Agile Methodologies. Communications of the ACM 48(5), 73–78 (2005)CrossRefGoogle Scholar
  26. 26.
    Petersen, K., Wohlin, C.: Measuring the flow in lean software development. Software Practice and Experience 41(9), 975–996 (2010)CrossRefGoogle Scholar
  27. 27.
    Pettersson, F., et al.: A practitioner’s guide to light weight software process assessment and improvement planning. Journal of Systems and Software 81(6), 972–995 (2007)CrossRefGoogle Scholar
  28. 28.
    Ramesh, B., et al.: Can Distributed Software Development be Agile? Communications of the ACM 49(10), 41–46 (2006)CrossRefGoogle Scholar
  29. 29.
    Reifer, D., Maurer, F., Erdogmus, H.: Scaling Agile Methods. IEEE Software 20(4), 12–14 (2003)CrossRefGoogle Scholar
  30. 30.
    Robson, C.: Real World Research: A Resource for Social Scientists and Practitioner Researchers, 2nd edn. Blackwell Publishing (2002)Google Scholar
  31. 31.
    Strauss, A., Corbin, J.: Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory. SAGE Publications (1998)Google Scholar
  32. 32.
    Sutherland, J., et al.: Fully Distributed Scrum: Linear Scalability of Production between San Francisco and India. In: Agile Conference (AGILE 2008), Toronto, Canada (2009)Google Scholar
  33. 33.
    Sutherland, J., et al.: Disributed Scrum: Agile Project Management with Outsourced Development Teams. In: 40th Hawaii International Conference on System Sciecnes, Hawaii, USA (2007)Google Scholar
  34. 34.
    Yin, R.K.: Case study research: Design and methods. SAGE Publications (2008)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Deepika Badampudi
    • 1
  • Samuel A. Fricker
    • 1
  • Ana M. Moreno
    • 2
  1. 1.Blekinge Institute of TechnologyKarlskronaSweden
  2. 2.Universidad Politécnica de MadridBoadilla del MonteSpain

Personalised recommendations