Agile Software Development of Mobile Information Systems

  • Pekka Abrahamsson
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4495)

Abstract

Agile software development methods are quickly being adopted by the software industry. Concerns have been raised whether agile methods are suitable for any given information systems development domain. Indeed, quite little is known empirically about the validity of agile methods in most of the industrial domains. Mobile information systems present no exception in this sense. Yet, they are subject to frequent requirements changes in terms of changing business needs and technology, and their market is highly competitive. Moreover, most of these systems are far away from so called agile home ground. This talk presents the need for agile methods in the focal domain, identifies their shortcomings on the basis of three large-scale case studies from industry. All of the cases deal with the development of mobile information system and come from Nokia, F-Secure and Philips. The talk also discusses the possible strategies for deploying agile solutions in practice.

Keywords

Agile software development case study mobile information systems 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Larman, C., Basili, V.R.: Iterative and incremental development: A brief history. IEEE Software 20, 47–56 (2003)Google Scholar
  2. 2.
    Melnik, G., Williams, L., Geras, A.: Empirical Evaluation of Agile Processes. In: Wells, D., Williams, L. (eds.) Extreme Programming and Agile Methods - XP/Agile Universe 2002. LNCS, vol. 2418, Springer, Heidelberg (2002)Google Scholar
  3. 3.
    Lindvall, M., Basili, V.R., Boehm, B.W., Costa, P., Dangle, K., Shull, F., Tesoriero, R., Williams, L.A., Zelkowitz, M.V.: Empirical findings in agile methods. In: Wells, D., Williams, L. (eds.) Extreme Programming and Agile Methods - XP/Agile Universe 2002. LNCS, vol. 2418, Springer, Heidelberg (2002)CrossRefGoogle Scholar
  4. 4.
    Fenton, N.: Viewpoint Article: Conducting and presenting empirical software engineering. Empirical Software Engineering 6, 195–200 (2001)CrossRefGoogle Scholar
  5. 5.
    Iskanius, P.: An agile supply chain for a project-oriented steel product network, in Department of Industrial Engineering, University of Oulu, Oulu (2006)Google Scholar
  6. 6.
    Baskerville, R., Levine, L., Pries-Heje, J., Ramesh, B., Slaughter, S.: How Internet companies negotiate quality. IEEE Computer 5, 51–57 (2001)Google Scholar
  7. 7.
    Baskerville, R., Balasubramaniam, R., Levine, L., Pries-Heje, J.: High-speed software development practices: What works, what doesn’t. IT Professional 4, 29–36 (2006)CrossRefGoogle Scholar
  8. 8.
    Lal, D., Pitt, D.C., Beloucif, A.: Restructuring in European telecommunications: Modeling the evolving market. European Business Review 3, 152–156 (2001)CrossRefGoogle Scholar
  9. 9.
    Blazevic, V., Lievens, A., Klein, E.: Antecedents of project learning and time-to-market during new mobile service development. International Journal of Service Industry Management 1, 120–147 (2003)CrossRefGoogle Scholar
  10. 10.
    Truex, D.P., Baskerville, R., Travis, J.: Amethodological systems development: The deferred meaning of systems development methods. Accounting, Management and Information Technology 10, 53–79 (2001)CrossRefGoogle Scholar
  11. 11.
    van Solingen, R.: Measuring the ROI of Software Process Improvement. IEEE Software 3, 32–38 (2004)CrossRefGoogle Scholar

Copyright information

© Springer Berlin Heidelberg 2007

Authors and Affiliations

  • Pekka Abrahamsson
    • 1
  1. 1.VTT Technical Research Centre of Finland, P.O.Box 1100, FIN-90571 OuluFinland

Personalised recommendations