System Development Methodologies - SCRUM & RAD

qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmqwertyuiopasdfghjkl
zxcvbnmqwertyuiopasdfghjklzxc
vbnmqwertyuiopasdfghjklzxcvb
nmqwertyuiopasdfghjklzxcvbnm
qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiop
asdfghjklzxcvbnmqwertyuiopasd
fghjklzxcvbnmqwertyuiopasdfgh
jklzxcvbnmrtyuiopasdfghjklzxcv
System Development Methodologies
SCRUM & RAD

System Development Methodologies
Table of Contents
Introduction...........................................................................................................................................2
System Development Methodologies Selected......................................................................................2
SCRUM.............................................................................................................................................2
Rapid Application Development (RAD)............................................................................................3
Comparison & Contrast.........................................................................................................................4
Benefits.............................................................................................................................................4
Drawbacks.........................................................................................................................................5
Comparison of RAD and SCRUM Methodologies............................................................................6
Recommendations & Conclusion..........................................................................................................7
References.............................................................................................................................................8
1

System Development Methodologies
Introduction
The organization has decided to develop and implement a mobile application that would be
synced with the existing system and database. It will allow the resources to access the
application using their mobile devices. There are different system development
methodologies that are available and can be used to carry out the development activities. The
report describes two such methodologies and recommends the one that suits to the
requirements in the best possible manner.
System Development Methodologies Selected
SCRUM
One of the methodologies that can be used for the development of the system for the
organization is SCRUM methodology. SCRUM is a sub-set of agile methodology for system
development and it is an ad-hoc methodology that is adaptive in nature. It is a methodology
that is currently being used by a majority of the business organizations as it provides agile,
flexible, and scalable products as the outcome. There are sprints involved in the SCRUM
system development in which a new capability is released at the gap of 2-4 weeks. The teams
that are involved in a SCRUM project are in the range of team size as 5 to 9 members. There
are three primary roles that are defined under this methodology as Product Owner, Scrum
Master, and development team (Carvalho & Mello, 2011). There are certain events that are
covered under this methodology as sprint, sprint planning, daily stand-up, sprint review, and
retrospective. In this methodology, there will be a product backlog that will be prepared in
which the requirements associated with the mobile application to be developed for the
organization will be stored. The working set for every sprint will be taken from the product
backlog and it will be referred as sprint backlog. The development team will take the
requirements from the sprint backlog and will execute it in the sprint cycle for providing a
working set of software at the end of the sprint. There will be a daily stand-up that will be
carried out by the Scrum Master to discuss the sprint progress and plan the activities for the
day. These sprints will continue until the product backlog will be empty. Scrum review will
be done at the end of every sprint and retrospective will be done at the end of the final sprint
(Mahnic, 2012).
2