CFP last date
20 May 2024
Reseach Article

Analyzing the enablers and challenges for Successful Methodological Transition

Published on April 2012 by Jagpuneet Bajwa, Kawaljeet Singh, Neeraj Sharma
International Conference on Recent Advances and Future Trends in Information Technology (iRAFIT 2012)
Foundation of Computer Science USA
IRAFIT - Number 9
April 2012
Authors: Jagpuneet Bajwa, Kawaljeet Singh, Neeraj Sharma
10f84266-ada2-4f13-9a1f-6c7660ec78d0

Jagpuneet Bajwa, Kawaljeet Singh, Neeraj Sharma . Analyzing the enablers and challenges for Successful Methodological Transition. International Conference on Recent Advances and Future Trends in Information Technology (iRAFIT 2012). IRAFIT, 9 (April 2012), 1-4.

@article{
author = { Jagpuneet Bajwa, Kawaljeet Singh, Neeraj Sharma },
title = { Analyzing the enablers and challenges for Successful Methodological Transition },
journal = { International Conference on Recent Advances and Future Trends in Information Technology (iRAFIT 2012) },
issue_date = { April 2012 },
volume = { IRAFIT },
number = { 9 },
month = { April },
year = { 2012 },
issn = 0975-8887,
pages = { 1-4 },
numpages = 4,
url = { /proceedings/irafit/number9/5909-1065/ },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Proceeding Article
%1 International Conference on Recent Advances and Future Trends in Information Technology (iRAFIT 2012)
%A Jagpuneet Bajwa
%A Kawaljeet Singh
%A Neeraj Sharma
%T Analyzing the enablers and challenges for Successful Methodological Transition
%J International Conference on Recent Advances and Future Trends in Information Technology (iRAFIT 2012)
%@ 0975-8887
%V IRAFIT
%N 9
%P 1-4
%D 2012
%I International Journal of Computer Applications
Abstract

Agile methods are gaining popularity over a wider range of domains, predominantly in enterprise environments. Software methodologies are evolving due to the challenges imposed by ever changing software development scenarios. Agile methodologies particularly demand for an organizational culture which focuses on high responsibility and greater discipline of every individual in an organization. The transition from traditional methodology to agile is an overwhelming task and poses greater challenge for organizations which are striving for better customer satisfaction and producing higher quality products. This paper investigates the underlying reasons behind this 'methodological shift', discusses about the contrasting differences between the traditional or conventional software development methods and light weight or agile methodologies. Further in this paper we discuss the present need for methodological transitions. Third section provides an insight of 'preconditions' (core reasons), 'enablers' (changes required) and 'challenges' (risks involved) for a successful methodological transition in the form of a proposed framework.

References
  1. Buchalcevova. 2008. Research of the Use of Agile Methodologies in the Czech Republic. The Inter-Networked World: ISD Theory, Practice, and Education. Springer-Verlag: New York, ISBN 978-0387304038.
  2. Bohem, W. B. 1988. A Spiral Model of Software Development and Enhancement. IEEE Computer, (May 1988), pp. 61-72..
  3. Cockburn, A. and Highsmith, J. Agile Software development: The People Factor. Computer, Vol. 34 (11), pp. 131-133.
  4. Digital Focus, "Agile 2006 Survey: Results and Analysis", Herndon, Command Information, http://www.rallydev.com/agileblog/page/2/, 2006, as accessed on 19.7.10.
  5. Brooks, F. P., et al., 1987. Defense Science Board Task Force Report on Military Software, Office of the Under Secretary of Defense for Acquisition, Washington, DC 20301.
  6. Berteig, M. 2008. Experience Report: Extremly short Iterations as a Catalyst for Effective Prioritization of work. In the proceedings of Agile 2008 conference, IEEE explore, pp. 265-268.
  7. Alleman, G. B. 2002. Agile Project Management Methods for IT Projects, The story of Managing Projects: A global, Cross Disciplinary collection of Perspectives, Greenwood Press/ Quorum Books.
  8. Schatz, B. and Abdelshafi, I. 2005. Primavera Gets Agile: A successful Transition to agile development. IEEE Software, May/June 2005, pp. 36-42.
  9. Highsmith, J. and Cockburn, A. 2001. Agile Software Development: The Business of Innovation. IEEE Computer, Vol. 18(9), Sept 2001, pp. 120-122.
  10. Livermore, A. Jeffrey, "Factors that Significantly Impact the Implementation of an Agile Software development Methodology", Journal of Software, Vol. 3 (4), pp. 31-36, 2008.
  11. Jiang, L. and Eberlin, A. 2008. Towards a framework for understanding the relationships between classical software Engineering and Agile Methodologies. In proceedings of APSO' 08, ACM, May 2008, pp. 9-14.
  12. Aoyama, M. 1998. Agile Software Process and its Experience. In proceedings of 20th ICSE, Kyoto, Japan, pp. 3-12.
  13. Aoyama, M. 1998. Web-Based Agile Software development. IEEE Software, Vol. 15 (6), pp. 56-65.
  14. Cohn, M. and Ford, D. 2003. Introducing an Agile Process to an Organization, Computer, pp. 74-78.
  15. Griffiths, M. 2007. Developments in Agile Project Management. In proceedings PMI Global Congress, Atlanta Georgia.
  16. Laanti, M., Salo, O and Abrahamsson, P. 2010. Agile methods rapidly replacing traditional methods at Nokia: a Survey of opinions on agile transformation. Information and Software Technology, Elsevier, 2010, doi: 10.1016/j.infsof.2010.11.010, in press.
  17. Abrahamsson, P., Warsta, J., Simponen, M. T. and Ronkainen, J. 2003. New directions on Agile method : a comparative analysis. In the Proceedings of 25th International Conference on Software Engineering, Portland, Oregon, pp. 244-254.
  18. Jalote, P., Palit, A., Kurien, P. and Peethamber, V. T. 2004. Timeboxing: a model for iterative software development. The Journal of Systems and Software, Elsevier, Vol. 70, pp. 117-127.
  19. Rajamanickam. 2005. Successful Project Management using Agile Methodology. Journal of the Quality Assurance Institute, Vol. 19, pp. 15-18.
  20. Ambler, S. 2007. Examining the Effectiveness of Agile Practices. Dr. Dobb's journal, http://www.ddj.com/architect/200001986,accesed on 4.5.10.
  21. Misra, S. C., Kumar, V. and Kumar, U. 2009. Identifying some of the success factors in adopting agile software development practices. Journal of systems and software, Vol. 82 (11), pp. 1869-1890.
  22. Cronholm, S. 2009. Using Agile method ? – Expected effects. Information Systems Development, Springer US, Chapter 96, pp 913-921.
  23. Nerur, Mahapatra, R., Mangalaraj, G. 2005.Challenges of migrating to agile methodologies. Communications of the ACM, Vol. 48 (5), pp. 72-78.
  24. Shine Technologies.2007. Agile Methodologies Survey Results. http://www.shinetech.com.dowload/attachments/98/shinetechAgileSurvey2003-01-17.pdf, accessed on 10.10.09.
  25. Sidky, Arthur, J., Bohner, J. 2007. A disciplined approach to adopting agile practices: the agile adoption framework. Innovations in Systems and Software Engineering, Springer London, Vol. 3 (3), pp. 203-216.
  26. The Chaos report, 1994, http://www.projectsmart.co.uk/docs/ chaos-report.pdf, accessed on 8.1.10.
  27. Version One, 4th Annual Survey 2009, www.versionone.com/agilesurvey, accessed on 2.4.11.
  28. Version One, 3rd Annual Survey: The State of Agile Development. 2008. http:// www.versionone.com/pdf/3rdAnnualStateOfAgile_FullDataReport.pdf, accessed on 2.4.11.
  29. Rajlich, V. T. 2006. Changing the Paradigm of Software Engineering. Communications of the ACM, vol. 49 (8), pp. 67-70.
Index Terms

Computer Science
Information Sciences

Keywords

Agile Methods Xp Scrum Dsdm Spiral Model Waterfall Model