INTERNATIONAL RESEARCH JOURNAL OF SCIENCE ENGINEERING AND TECHNOLOGY

( Online- ISSN 2454 -3195 ) New DOI : 10.32804/RJSET

Impact Factor* - 6.2311


**Need Help in Content editing, Data Analysis.

Research Gateway

Adv For Editing Content

   No of Download : 127    Submit Your Rating     Cite This   Download        Certificate

A STUDY OF CRITICISMS & RISKS WITH AGILE METHODS IN RISK MANAGEMENT

    2 Author(s):  SHABNAM ARORA, DR. Y. RAMA DEVI

Vol -  2, Issue- 2 ,         Page(s) : 67 - 73  (2012 ) DOI : https://doi.org/10.32804/RJSET

Abstract

Nimble strategies are a take-off from plan-driven conventional methodologies, where the emphasis is on creating early arrivals of working software utilizing community oriented procedures, code refactoring, and on location client contribution. Research and overviews have demonstrated that nimble techniques are an effective method for creating software with huge focal points underway costs, time-to-market, intricacy, and quality improvement over overwhelming weight conventional approaches. Indeed, even with such obvious favorable circumstances the data innovation, industry has not seen an enormous scale selection of dexterous techniques. Drawing data from the writing issues like structure for spry authoritative change and appropriation procedures are inspected. Contributions from the business recommend that most associations are most appropriate in receiving a blend of conventional and dexterous techniques. There is no coordinated procedure that can be all around connected and they all must be custom fitted to incorporate into existing procedures.

[1] J. Astemark, “ Agile@ITTE“, Internal Ericsson Documentation, Sweden 2011
[2] D. Duka, “Agile approach in Software Development“, Proceedings of the 35th Mipro CTI conference, 2012
[3] J. Sääskilahti, J. Röning “Challenges with Software Security on Agile Software development, Internal Ericsson Documentation, Sweden 2011
[4] R. Winston, “Managing The Development of Large Software Systems“, Proceedings, IEEE WESCON, August 1970, pages 1-9. http://www.cs.umd.edu/class/spring2003/cmsc838p/Process/waterfal l.pdf
[5] K. Beck, “Manifesto for Agile Software Development”, 2012 http:// Agilemanifesto.org
[6] M. and T. Poppendieck, “Lean Software Development Principles”, http://www.poppendieck.com/
[7] T. Stober, U. Hansmann. "Overview of Agile Software Development", Agile Software Development: Best Practices for Large Software Development Projects, Springer. 2010.
[8] S. W. Ambler, “Agile Enterprise Architecture”, http://www. Agiledata.org
[9] S. W. Ambler, “Agile Architecture: Strategies for Scaling Agile development”, http://www. Agilemodeling.com.org
[10] K. Mikkonen, “How We Learned to Stop Worrying and Live with the Uncertainties“, Internal Ericsson Documentation, Sweden 2012
[11]. Boehm, B., & Turner, R. (2005). Management challenges to implementing agile processes in traditional development organizations. IEEE software, 22(5), 30-39.
[12]. Schwaber, C., Leganza, G., & D’Silva, D. (2007). The truth about agile processes. Forrester Research.
[13]. Laanti, M., Salo, O., & Abrahamsson, P. (2011). Agile methods rapidly replacing traditional methods at Nokia: A survey of opinions on agile transformation. Information and Software Technology, 53(3), 276-290.
[14]. Nikitina, N. & Kajko-Mattsson, M. (2011). DeveloperDriven Big Bang Process Transition from Scrum to Kanban, ICSSP, ACM.

*Contents are provided by Authors of articles. Please contact us if you having any query.






Bank Details