Skip to main content

Analysis of Agile Software Development from the Knowledge Transformation Perspective

  • Conference paper
Perspectives in Business Informatics Research (BIR 2014)

Part of the book series: Lecture Notes in Business Information Processing ((LNBIP,volume 194))

Included in the following conference series:

Abstract

While the Agile Software Development (ASD) has been successfully promoted in the last 15 years, there is no agreement on how to determine whether a particular project is agile or not. Some practitioners consider agility as strict usage of a specific methodology, e.g. SCRUM, others consider agility as adhering to Agile Manifesto. The lack of common view on ASD prevents creating common guidelines on when the usage of ASD is appropriate. This paper presents a model of ASD that helps to differentiate it from the traditional, phase-based development, and more strictly defines the area of its applicability. The model has been built based on the knowledge transformation perspective, as the author considers it to be the most differentiating perspective when comparing ASD to traditional software development. For building the model, the ideas from SECI model of Nonaka have been exploited. The results, in the form of requirements to be fulfilled for successful employment of ASD, are demonstrated through analysis of completed ASD projects.

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

Access this chapter

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 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

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Highsmith, J., Orr, K., Cockburn, A.: E-Business Application Delivery, pp. 4–17 (2000), http://www.cutter.com/freestuff/ead0002.pdf

  2. Shore, J., Warden, S.: The art of agile. O’Reilly (2008)

    Google Scholar 

  3. Weaver, M.: Do you agree or disagree that Scrum is not Agile (May 2011), http://www.linkedin.com/groups/Do-you-agree-disagree-that-81780.S.52354777

  4. Bider, I., Karapantelakis, A., Khadka, N.: Building a High-Level Process Model for Soliciting Requirements on Software Tools to Support Software Development: Experience Report. In: PoEM 2013, Riga, Latvia. CEUR, vol. 1023, pp. 70–82 (2013)

    Google Scholar 

  5. Agile Alliance. Manifesto for Agile Software Development (2001), http://agilemanifesto.org/

  6. Conboy, K., Fitzgerald, B.: Toward a conceptual framework of agile methods: a study of agility in different disciplines. In: Proceedings of the 2004 ACM Workshop on Interdisciplinary Software Engineering Research, Newport Beach, pp. 37–44 (2004)

    Google Scholar 

  7. Conboy, K., Fitzgerald, B.: Toward a conceptual framework of agile methods. In: Extreme Programming and Agile Methods-XP-Agile Universe 2004, pp. 105–116 (2004)

    Google Scholar 

  8. Nonaka, I.: A dynamic theory of organizational knowledge creation. Organization Science 5(1), 14–37 (1994)

    Article  Google Scholar 

  9. Bider, I., Johannesson, P., Perjons, E.: Design science research as movement between individual and generic situation-problem-solution spaces. In: Organizational Systems. An Interdisciplinary Discourse, pp. 35–61. Springer (2013)

    Google Scholar 

  10. Andersson, T., Bider, I., Svensson, R.: Aligning people to business processes experience report. SPIP 10(4), 403–413 (2005)

    Google Scholar 

  11. Conant, R., Ashby, R.: Every good regulator of a system must be a model of that system. Int. J. Systems Sci. 1(2), 89–97 (1970)

    Article  Google Scholar 

  12. Flood, R.L., Carson, E.R.: Dealing with complexity: an introduction to the theory and application of systems science. Springer (1993)

    Google Scholar 

  13. Boehm, B., Turner, R.: Balancing Agility and Discipline. Addison-Wesley (2004)

    Google Scholar 

  14. IbisSoft, ibisSoft (2012a), http://www.ibissoft.se/node/7

  15. Lacey, M.: Agile Aliance (2008a), http://conferences.agilealliance.org/sessions/20083058

  16. Lacey, M.: Mitch Lacey & Associates (2010), http://www.mitchlacey.com/resources/working-software-is-not-enough

  17. Lacey, M.: InfoQ (2008b), http://www.infoq.com/presentations/A-Story-of-Project-Failure-Mitch-Lacey

  18. Krigsman, M.: ZDNet (2008), http://www.zdnet.com/blog/projectfailures/agileanatomy-of-a-failed-project/1100

  19. Wendorff, P., Apshvalka, D.: The Knowledge Management Strategy of Agile Software Development. In: ECKM, Reading, UK, pp. 607–614 (2005)

    Google Scholar 

  20. Armour, P.G.: The Case for a New Business Model. Is software a product or a medium? Communications of the ACM 43(8), 19–22 (2000)

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2014 Springer International Publishing Switzerland

About this paper

Cite this paper

Bider, I. (2014). Analysis of Agile Software Development from the Knowledge Transformation Perspective. In: Johansson, B., Andersson, B., Holmberg, N. (eds) Perspectives in Business Informatics Research. BIR 2014. Lecture Notes in Business Information Processing, vol 194. Springer, Cham. https://doi.org/10.1007/978-3-319-11370-8_11

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-11370-8_11

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-11369-2

  • Online ISBN: 978-3-319-11370-8

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics