Advertisement

Exploring Key Factors of Pilot Projects in Agile Transformation Process Using a Grounded Theory Study

  • Taghi Javdani Gandomani
  • Hazura Zulzalil
  • Abdul Azim Abd Ghani
  • Abu Bakar Md. Sultan
  • Khaironi Yatim Sharif
Part of the Communications in Computer and Information Science book series (CCIS, volume 403)

Abstract

Changing development approach from disciplined to agile methods is an organizational mutation that requires many issues to be considered to increase its chance of success. Selecting an appropriate pilot project as initial project that is going to be done through an Agile method is a critical task. Due to the impact of such a pilot project on successful Agile transformation, understanding its critical factors helps organizations choose the most suitable project to start Agile transition. Conducting a Grounded Theory, showed that organization should considered some key factors of a pilot: Criticality, Duration, Size and Required resources. Besides these factors, the results showed that organization should be aware of the risk of successful pilot project in their next Agile projects. The study also showed that pilot selection mostly is done by Agile coaches or is forced by customer.

Keywords

gile Software Development Agile Transformation Agile Pilot Project Grounded Theory 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
  2. 2.
    Highsmith, J.A.: Agile Software Development Ecosystems. Addison-Wesley Professional, Boston (2002)Google Scholar
  3. 3.
    Gandomani, T.J., Zulzali, H., Ghani, A.A.A., Sultan, A.M., Nafchi, M.Z.: Obstacles to moving to agile software development; at a glance. Journal of Computer Science 9, 620–625 (2013)CrossRefGoogle Scholar
  4. 4.
    Conboy, K., Coyle, S., Wang, X., Pikkarainen, M.: People over process: Key challenges in agile development. IEEE Software 28, 48–57 (2011)CrossRefGoogle Scholar
  5. 5.
    Cohn, M.: Succeeding with Agile: Software Development Using Scrum. Addison-Wesley Professional, Boston (2009)Google Scholar
  6. 6.
    Pikkarainen, M., Salo, O., Kuusela, R., Abrahamsson, P.: Strengths and barriers behind the successful agile deployment-insights from the three software intensive companies in Finland. Empirical Software Engineering 17, 675–702 (2012)CrossRefGoogle Scholar
  7. 7.
    Ganesh, N., Thangasamy, S.: Lessons learned in transforming from traditional to agile development. Journal of Computer Science 8, 389–392 (2012)CrossRefGoogle Scholar
  8. 8.
    Sidky, A., Arthur, J., Bohner, S.: A disciplined approach to adopting agile practices: The agile adoption framework. Innovations in Systems and Software Engineering 3, 203–216 (2007)CrossRefGoogle Scholar
  9. 9.
    Qumer, A., Henderson-Sellers, B.: A framework to support the evaluation, adoption and improvement of agile methods in practice. Journal of Systems and Software 81, 1899–1919 (2008)CrossRefGoogle Scholar
  10. 10.
    Tolfo, C., Wazlawick, R.S., Ferreira, M.G.G., Forcellini, F.A.: Agile methods and organizational culture: Reflections about cultural levels. Journal of Software Maintenance and Evolution 23, 423–441 (2011)CrossRefGoogle Scholar
  11. 11.
    Vijayasarathy, L., Turk, D.: Drivers of agile software development use: Dialectic interplay between benefits and hindrances. Information and Software Technology 54, 137–148 (2012)CrossRefGoogle Scholar
  12. 12.
    Sutharshan, A.: Enhancing Agile methods for multi-cultural software project teams. Modern Applied Science 5, 12–22 (2011)Google Scholar
  13. 13.
    Sohaib, O., Khan, K.: Integrating usability engineering and agile software development: A literature review, pp. V232–V238 (2010)Google Scholar
  14. 14.
    Srinivasan, J., Lundqvist, K.: Agile in India: Challenges and lessons learned. In: 3rd India Software Engineering Conference, ISEC 2010, pp. 125–130. ACM, New York (2010)Google Scholar
  15. 15.
    Gandomani, T.J., Zulzalil, H., Ghani, A.A.A., Sultan, A.B.M.: Towards comprehensive and disciplined change management strategy in agile transformation process. Research Journal of Applied Sciences, Engineering and Technology 6, 2345–2351 (2013)Google Scholar
  16. 16.
    Glaser, B.: Basics of Grounded Theory Analysis: Emergence Vs. Forcing. Sociology Press, Mill Valley (1992)Google Scholar
  17. 17.
    Glaser, B., Strauss, A.: The Discovery of Grounded Theory: Strategies for Qualitative Research. Aldine Transaction Chicago (1967)Google Scholar
  18. 18.
    Glaser, B.G.: Theoretical Sensitivity: Advances in the Methodology of Grounded Theory. The Sociology Press, Mill Valley (1978)Google Scholar
  19. 19.
    Glaser, B.G.: The Grounded Theory Perspective III: Theoretical Coding. Sociology Press, Mill Valley (2005)Google Scholar
  20. 20.
    Corbin, J.M., Strauss, A.C.: Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory (3e). SAGE Publications, Inc., Thousand Oaks (2008)Google Scholar
  21. 21.
    Hoda, R., Noble, J., Marshall, S.: Using grounded theory to study the human aspects of software engineering. In: Human Aspects of Software Engineering, pp. 1–2. ACM, USA (2010)Google Scholar
  22. 22.
    Dingsøyr, T., Nerur, S., Balijepally, V., Moe, N.B.: A decade of agile methodologies: Towards explaining agile software development. Journal of Systems and Software 85, 1213–1221 (2012)CrossRefGoogle Scholar
  23. 23.
    Ghanam, Y., Maurer, F., Abrahamsson, P.: Making the leap to a software platform strategy: Issues and challenges. Information and Software Technology 54, 968–984 (2012)CrossRefGoogle Scholar
  24. 24.
    Hoda, R., Noble, J., Marshall, S.: The impact of inadequate customer collaboration on self-organizing Agile teams. Information and Software Technology 53, 521–534 (2011)CrossRefGoogle Scholar
  25. 25.
    Baskerville, R., Pries-Heje, J., Madsen, S.: Post-agility: What follows a decade of agility? Information and Software Technology 53, 543–555 (2011)CrossRefGoogle Scholar
  26. 26.
    Hoda, R., Noble, J., Marshall, S.: Developing a grounded theory to explain the practices of self-organizing Agile teams. Empirical Software Engineering 17, 609–639 (2011)CrossRefGoogle Scholar
  27. 27.
    Coleman, G., O’Connor, R.: Using grounded theory to understand software process improvement: A study of Irish software product companies. Information and Software Technology 49, 654–667 (2007)CrossRefGoogle Scholar
  28. 28.
    Parry, K.W.: Grounded theory and social process: A new direction for leadership research. Leadership Quarterly 9, 85–105 (1998)CrossRefGoogle Scholar
  29. 29.
    Glaser, B.: Doing Grounded Theory: Issues and Discussions. Sociology Press, Mill Valley (1998)Google Scholar
  30. 30.
  31. 31.
    Charmaz, K.: Constructing Grounded Theory: A Practical Guide through Qualitative Analysis. SAGE Publications Ltd., London (2006)Google Scholar
  32. 32.
    Drobka, J., Noftz, D., Raghu, R.: Piloting XP on four mission-critical projects. IEEE Software 21, 70–75 (2004)CrossRefGoogle Scholar
  33. 33.
    Cohen, D., Lindvall, M., Costa, P.: An Introduction to Agile Methods. Advances in Computers 62, 1–66 (2004)CrossRefGoogle Scholar
  34. 34.
    Boehm, B., Turner, R.: Using risk to balance agile and plan-driven methods. Computer 36, 57–66 (2003)CrossRefGoogle Scholar
  35. 35.
    Honious, J., Clark, J.: Something to believe in. In: AGILE Conference, pp. 203–210 (2006)Google Scholar
  36. 36.
    Hajjdiab, H., Taleb, A.S.: Agile adoption experience: A case study in the U.A.E. In: IEEE 2nd International Conference on Software Engineering and Service Science (ICSESS 2011), pp. 31–34. IEEE Computer Society, Washington, DC (2011)Google Scholar
  37. 37.
    Fulgham, C., Johnson, J., Crandall, M., Jackson, L., Burrows, N.: The FBI gets agile. IT Professional 13, 57–59 (2011)CrossRefGoogle Scholar
  38. 38.
    Heidenberg, J., Matinlassi, M., Pikkarainen, M., Hirkman, P., Partanen, J.: Systematic piloting of agile methods in the large: Two cases in embedded systems development. In: Ali Babar, M., Vierimaa, M., Oivo, M. (eds.) PROFES 2010. LNCS, vol. 6156, pp. 47–61. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  39. 39.
    Adolph, S., Hall, W., Kruchten, P.: A methodological leg to stand on: Lessons learned using grounded theory to study software development. In: 2008 Conference of the Center for Advanced Studies on Collaborative Research: Meeting of Minds, pp. 166–178. ACM, Ontario (2008)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Taghi Javdani Gandomani
    • 1
  • Hazura Zulzalil
    • 1
  • Abdul Azim Abd Ghani
    • 1
  • Abu Bakar Md. Sultan
    • 1
  • Khaironi Yatim Sharif
    • 1
  1. 1.Faculty of Computer Science and Information TechnologyUniversity Putra Malaysia (UPM)SerdangMalasyia

Personalised recommendations