Open Access   Article Go Back

Role of agile methodology for software product development

Jyoti Kharade1 , Sneha Prajapati2 , Dakshata Narkar3 , Dhanaji S. Kharade4

  1. Bharati Vidyapeeth’s Institute of Management and Information Technology, Navi Mumbai, India.
  2. Bharati Vidyapeeth’s Institute of Management and Information Technology, Navi Mumbai, India.
  3. Bharati Vidyapeeth’s Institute of Management and Information Technology, Navi Mumbai, India.
  4. Bharati Vidyapeeth’s College of Engineering, Navi Mumbai, India.

Section:Review Paper, Product Type: Journal Paper
Volume-6 , Issue-5 , Page no. 424-427, May-2018

CrossRef-DOI:   https://doi.org/10.26438/ijcse/v6i5.424427

Online published on May 31, 2018

Copyright © Jyoti Kharade, Sneha Prajapati, Dakshata Narkar, Dhanaji S. Kharade . This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

View this paper at   Google Scholar | DPI Digital Library

How to Cite this Paper

  • IEEE Citation
  • MLA Citation
  • APA Citation
  • BibTex Citation
  • RIS Citation

IEEE Style Citation: Jyoti Kharade, Sneha Prajapati, Dakshata Narkar, Dhanaji S. Kharade, “Role of agile methodology for software product development,” International Journal of Computer Sciences and Engineering, Vol.6, Issue.5, pp.424-427, 2018.

MLA Style Citation: Jyoti Kharade, Sneha Prajapati, Dakshata Narkar, Dhanaji S. Kharade "Role of agile methodology for software product development." International Journal of Computer Sciences and Engineering 6.5 (2018): 424-427.

APA Style Citation: Jyoti Kharade, Sneha Prajapati, Dakshata Narkar, Dhanaji S. Kharade, (2018). Role of agile methodology for software product development. International Journal of Computer Sciences and Engineering, 6(5), 424-427.

BibTex Style Citation:
@article{Kharade_2018,
author = {Jyoti Kharade, Sneha Prajapati, Dakshata Narkar, Dhanaji S. Kharade},
title = {Role of agile methodology for software product development},
journal = {International Journal of Computer Sciences and Engineering},
issue_date = {5 2018},
volume = {6},
Issue = {5},
month = {5},
year = {2018},
issn = {2347-2693},
pages = {424-427},
url = {https://www.ijcseonline.org/full_paper_view.php?paper_id=1998},
doi = {https://doi.org/10.26438/ijcse/v6i5.424427}
publisher = {IJCSE, Indore, INDIA},
}

RIS Style Citation:
TY - JOUR
DO = {https://doi.org/10.26438/ijcse/v6i5.424427}
UR - https://www.ijcseonline.org/full_paper_view.php?paper_id=1998
TI - Role of agile methodology for software product development
T2 - International Journal of Computer Sciences and Engineering
AU - Jyoti Kharade, Sneha Prajapati, Dakshata Narkar, Dhanaji S. Kharade
PY - 2018
DA - 2018/05/31
PB - IJCSE, Indore, INDIA
SP - 424-427
IS - 5
VL - 6
SN - 2347-2693
ER -

VIEWS PDF XML
433 340 downloads 191 downloads
  
  
           

Abstract

Increasing complexities in the requirements set on programming solution due to change in the business activities has lead to need of modern approaches, also known as agile methodologies also known as lightweight, which claim to provide solution to above said problem. Knowledge Management (KM) can be easily accepted into agile software development (ASD) environments. Agile software development processes include some practices that support Knowledge Management (KM). KM is about learning, and ASD set up an environment that supports learning processes. In this paper, attempt is made to study the role of Agile methodology in software development, find barriers in applying agile methodologies in software development and to propose the role of agile methodologies for enhancing software development.

Key-Words / Index Term

Agile Methodology, Software Development, Knowledge Management

References

[1] Kittlaus, H.-B. 2003. Software Engineering und Software Fabrik - vom Nutzen und Schaden der Metapher in der Informatik, In: Informatik-Spektrum 26: p. 8 - 12, and p. 291 – 292
[2] Davis, M. 2011. “Will Software Engineering Ever Be Engineering?”, in: CACM 54 (11), p. 32-34
[3] White, J., Simons, B. 2002. ACM’s Position on the Licencing of Software Engineers, CACM 45 (11), p. 91
[4] Spek, R. Kruizinga, E Annelies Kleijsen, 2009 Strengthening lateral relations in organisations through knowledge management, Journal of Knowledge Management, Vol. 13 Iss: 3, pp.3 – 12
[5] Awad, M. A. 2005 Comparison between Agile and Traditional Software Development Methodologies, Honours Programme Thesis, University of Western Australia.
[6] Highsmith, J. Orr, K. and Cockburn, A. 2000 Extreme Programming, E- Business Application Delivery, pp. 417
[7] Job Trends www.indeed.com/jobtrends?q=agile%2C+scrum%2C+% 22extreme+programming%22%2C+%22test+driven%22 &l=,
[8] AmitojSingh ,Kawaljeet Singh , Neeraj Sharma “Managing Knowledge in Agile Software Development” International Conference on Recent Advances and Future Trends in Information Technology (iRAFIT2012) Proceedings published in International Journal of Computer Applications® (IJCA)
[9] Williams, L. (2010) Agile Software Development Methodologies and Practices. Advances in Computers, 80, 1-44. https://doi.org/10.1016/S0065-2458(10)80001-4
[10] Tudor, D.2006 An update on Agile methods, ITadviser, Issue 56.
[11] El-Haik, B.S. and Shaout, A. (2010) Software Design for Six Sigma: A Roadmap for Excellence. Wiley, Hoboken. https://file.scirp.org/pdf/JCC_2017033115471602.pdf
[12] Highsmith, J. and Cockburn, A. (2001) Agile Software Development: The Business of Innovation. Computer, 34, 120-127. https://doi.org/10.1109/2.947100
[13] Highsmith, J and Cockburn, A. 2001 Agile Software Development: The Business of Innovation, Computer, Vol. 34,No. 9, pp. 120-122.
[14] Version one, 2008 3rd Annual Survey: The State of Agile Development, www.versionone.com/pdf/3rdAnnualStateOfAgile_FullD ataReport.pdf.
[15] Version one, 2007 Agile development: Result Delivered, http://www.versionone.net/pdf/AgileDevelopment_Resul tsDelivered.pdf.
[16] Versiion One, 2009 4th Annual Survey 2009, www.versionone.com/agilesurvey
[17] Bennet, D. and Bennet, A. 2003 The Rise of the Knowledge Organisation, chapter 1 in Holsapple, C.W. (ed.), Handbook on Knowledge Management,Vol 1, Springer, Berlin, pp. 5–20.
[18] Reifer, D. J. 2002 How to Get the Most out of Extreme Programming/Agile Methods , In proceeding Proc. Extreme Programming and Agile Methods - XP/Agile Universe
[19] Jeffry S. Babb1 , RashinaHoda 2, and Jacob Nørbjerg3 “Barriers to Learning in Agile Software Development Projects” Department of Computer Information and Decision Management, West Texas A&M University, 2403 Russell Long Blvd. Canyon, Texas USA, 79016 jbabb@mail.wtamu.edu
[20] Martin McHugh, Fergal McCaffery, and Valentine Casey “Barriers to Adopting Agile Practices when Developing Medical Device Software” Regulated Software Research Group, Department of Computing and Mathematics, Dundalk Institute of Technology &Lero, Dundalk Co. Louth, Ireland {martin.mchugh, fergal.mccaffery, val.casey}@dkit.ie
[21] Erande, Ameya S., and Alok K. Verma. "Measuring agility of organizations-a comprehensive agility measurement tool (CAMT)." International Journal of Applied Management and Technology 6.3 (2008).
[22] Pressman R. S. ―Software Engineering: a Practitioner`s Approach‖ (2010) 7th ed.(McGraw-Hill, New York).
[23] Arun Kumar Kamepally ,TejaswiniNalamothu “Agile Methodologies in Software Engineering and Web Engineering” Department of Computer Science, Kennesaw State University, Kennesaw, Georgia, USA
[24] PekkaAbrahamsson, OutiSalo, JussiRonkainen and JuhaniWarsta “Agile Software Development Methods: Review and Analysis“ https://arxiv.org/ftp/arxiv/papers/1709/1709.08439.pdf
[25] Agile Manifesto, 2001. Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B., Martin, R., Mellor, S., Schwaber, K., Sutherland, J. & Thomas, D. Manifesto for Agile Software Development. http://AgileManifesto.org.
[26] Abrahamsson, P., Salo, O., Ronkainen, J. &Warsta, J. 2002. Agile Software Development Methods: Review and Analysis. Espoo. 408. VTT Publications 478. 107 p. http://www.vtt.fi/inf/pdf/publications/2002/P478.pdf