We apologize for a recent technical issue with our email system, which temporarily affected account activations. Accounts have now been activated. Authors may proceed with paper submissions. PhDFocusTM
CFP last date
20 November 2024
Call for Paper
December Edition
IJCA solicits high quality original research papers for the upcoming December edition of the journal. The last date of research paper submission is 20 November 2024

Submit your paper
Know more
Reseach Article

Risk Management Board for Effective Risk Management in Scrum

by B. Reddaiah, Satya Prasad Ravi, Lakshmi Sridhar Movva
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 65 - Number 12
Year of Publication: 2013
Authors: B. Reddaiah, Satya Prasad Ravi, Lakshmi Sridhar Movva
10.5120/10976-6117

B. Reddaiah, Satya Prasad Ravi, Lakshmi Sridhar Movva . Risk Management Board for Effective Risk Management in Scrum. International Journal of Computer Applications. 65, 12 ( March 2013), 16-23. DOI=10.5120/10976-6117

@article{ 10.5120/10976-6117,
author = { B. Reddaiah, Satya Prasad Ravi, Lakshmi Sridhar Movva },
title = { Risk Management Board for Effective Risk Management in Scrum },
journal = { International Journal of Computer Applications },
issue_date = { March 2013 },
volume = { 65 },
number = { 12 },
month = { March },
year = { 2013 },
issn = { 0975-8887 },
pages = { 16-23 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume65/number12/10976-6117/ },
doi = { 10.5120/10976-6117 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T21:21:04.384104+05:30
%A B. Reddaiah
%A Satya Prasad Ravi
%A Lakshmi Sridhar Movva
%T Risk Management Board for Effective Risk Management in Scrum
%J International Journal of Computer Applications
%@ 0975-8887
%V 65
%N 12
%P 16-23
%D 2013
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Projects that are developed by using agile methods are projected to give good results and more successful in producing high quality software that satisfies the needs of customer effectively at a faster pace. Software developing organizations that have been employing Scrum are recommended as starting point for organizations with small teams and with no distinct processes. Actually while using scrum it is able to identifying risks that occur in project development but it has no practices to identify the cause, factors to evaluate and handle the risk management effort. This study aims to introduce new roles and new team for Risk management that are effective in Risk management activity. The new roles and new teams of Scrum are useful for organizations that are experiencing high failure rates with respect to risk while using Scrum.

References
  1. Dr. Satya Prasad Ravi, B. Reddaiah, Lakshmi Sridhar Movva " Framework to mitigate dynamic and static risks with respect to agile" ESTIJ, Vol. 2, No. 1, 2012: PP. 63-68,2012.
  2. Dr. Satya Prasad Ravi, B. Reddaiah, Lakshmi Sridhar Movva, Rajasekhar Kilaparthi "A Critical review and empirical study on success of risk management activity with respect to scrum" ESTIJ, Vol. 2, No. 3, June 2012: PP. 467-473, 2012.
  3. Sprint Planning (January-February 2009). Sprint Planning Rules. Retrieved March 30, 2009.
  4. SchwaberK (2004) Agile project management with Scrum Microsoft Press, Redmond. ISBN 978-0-7356-1993-7.
  5. Ken Schwaber – Scrum Guides, Scrum Developer Courses, Scrum Knowledge Assessment, Scrum Guide. Scrum. org. 2009. Retrived April 3,2010.
  6. Sutherland, Jeff (2004-10). " Agile Development Lessons learned from the first Scrum". Retrieved September 26, 2008.
  7. Software Engineering Institute (2006) CMMI-DEV: CMMI for development, V1. 2 model, CMU/SEI-2006-TR-008, http://www. sei. cmu. edu/cmmi/general/
  8. Ana sofia C. Marcal (2008). Blending scrum practices and cmmi project management process areas, Springer.
Index Terms

Computer Science
Information Sciences

Keywords

Scrum Risk management Sprint Transition product backlogs Enterprise Transition team(ETC) Scrum rollout team(SRT) Scrum development team(SDT) Risk Management Board(RMB) Risk Management Team(RMT)