This document provides an overview of Scrum, an agile software development framework. It discusses Scrum's iterative and incremental approach. The document includes an abstract, introduction discussing the benefits of Scrum, a literature review covering research on Scrum, descriptions of common Scrum terms and processes, the author's review methodology, results from studies on Scrum, and conclusions. It aims to evaluate current research on Scrum and provide context for professionals interested in agile methods.

1. Presented By-
Ashish Agrawal
SRMS CET
Bareilly
SCRUM:An Iterative and Incremental
Method from Agile Family

2. CONTENTS
9 August 2014SACTA20142
 Abstract
 Introduction
 Literature Survey
 Basic Terms
 Review Method
 Review Result
 Conclusion
 References

3. ABSTRACT
 Scrum, an Agile method has been a topic of much
discussion among today’s software industry people and
professionals. Unlike many other software development
and management processes, Scrum is a framework that
favors an iterative and incremental approach.
 Scrum methods were broken by keeping changing
requirements of the clients in mind, and supports self-
organizing manner of work.
 As scrum seems so fruitful, in this paper authors done a
review on Scrum for finding out the current working and
adaptations in Scrum implementation and this paper will be
an add on literature for other professionals interested in
Scrum and agile methods development.
9 August 20143 SACTA2014

4. INTRODUCTION
 From 2001, with the release of agile manifesto, scrum also
made its position in the literature of the software industry.
Scrum focuses on project management in situations where
it is difficult to plan ahead. Software is developed by a self-
organizing team in increments (called ‘‘sprints”), starting
with planning and ending with a review.
 Based on experience, one report claims that Scrum
practices such as daily scrum, scrum of scrums, sprint
planning and retrospective meetings engage distributed
team members in collaboration, help visualization of
hidden problems, develop trust and increase team spirit [1].
9 August 20144 SACTA2014

5.  This review tries to evaluate and present the research
findings on Scrum up to present day. This systematic
review provides an overview of fields researched, their
results and future implications.
 We hope this review shall be very helpful for the
researchers who are enthusiast for discovering something
new in the field of Scrum and software engineering.
9 August 20145 SACTA2014

6. LITERATURE SURVEY
9 August 2014SACTA20146
 According to Rising and Janoff, Scrum can improve
communications and maximize co-operation. This method
is scalable from small single projects to entire organizations
[5].
 For a complex systems development project to be
successful it should be implemented in small steps, each
with a clear measure of successful achievement and with an
option of rolling back to a previous successful step upon
failure [6]
 Agile methodologies put a great emphasis on people and
their talents, skills, and knowledge, suggesting that for agile
development to be effective team members must be
responsive, competent, and collaborative [7][8].

7.  In 2013, Scrum Alliance had conducted a survey on the
current state of Scrum in the world, in which 499
participants from 70 countries took part
 This report has shown that Scrum is the most used
method from agile methods and it also shown that
more than 80% of their participants have been
involved in at least one or more Agile projects, it is no
surprise that a majority use Scrum regularly [9]
 Figure 1 shows the use of different agile methods in
organizations(scrum is mostly used)
 Figure 2 shows use of Scrum(27%) in organizations
and fig.3 shows the highest business priorities for
Scrum projects which is fulfillment of user needs.
9 August 20147 SACTA2014

8. Fig 1: Use of Agile Methods [9]
9 August 20148 SACTA2014

9. Fig 2: Use of Scrum [9]
9 August 20149 SACTA2014

10. Fig 3: Highest Business Priorities for Scrum [9]
9 August 201410 SACTA2014

11. BASIC TERMS OF SCRUM
 The Scrum Master
 The Product Owner
 The Scrum team
 A Sprint
 The Sprint Backlog
 The Sprint Backlog Burn-down
 The Sprint Planning Meeting
 The Sprint Retrospective meeting
 The daily stand-up meeting
9 August 201411 SACTA2014

12. REVIEW METHOD
 Data Sources and Data Collection-The data searching
strategy included online electronic data searches and
manual searches of various national and international
conference proceedings. In this context, following online
journal’s databases were searched-
-ASQ Digital Library
-IEEE Explore
-Springer Link
-Academia.edu
-Research Gate
-Agile Alliance
-Science Direct –Elsevier
9 August 201412 SACTA2014

13.  Acceptance and Rejection Criteria-The studies which
presented quality data on Scrum or agile methods were
accepted. We included the studies of both students and
professionals. Some very old studies were rejected if they
were not up to the mark. The author’s main focus was to
accept qualitative and agile methods based research studies.
 Search Strategy- For searching research papers, we used
Google search engine and MSN search engine. For this
activity, we made some combinations from the area of agile
methodology. Some of those combinations are as follows-
-Agile Software Development
-Agile with Scrum
-Agile and scrum
-Scrum Method and Agile
-Scrum and Agile Benefits
-Pros and Cons of Scrum or Agile
9 August 201413 SACTA2014

14.  Quality Assessment-For doing quality assessment, the
authors did follow the criteria defined in [4]. The three
main issues defined in [4] are as follows-
1.Rigour-Has a thorough and appropriate approach been applied to key
research methods in the study?
2.Credibility-Are the findings well-presented and meaningful?
3.Relevance-How useful are the findings to the software industry and
the research community?
 Data Extraction- On this final stage, data was extracted
from each of the study. The data were extracted on the basis
of parameters like the research method used, agile methods,
domain, publication, and remarks.(Table 1)
9 August 201414 SACTA2014

15. REVIEW RESULT
9 August 2014SACTA201415
Table 1-A Comparative Study on some Scrum Work- A Result

16. CONCLUSION
 In this paper, authors did a systematic review on the
Scrum methodology and its uses. Various research
papers and surveys were included. This review
concludes that Scrum is one of the most talked about
concept of today’s era. This method not only provides
a significant way of working but also a great
atmosphere for work with support to self organizing
teams.
9 August 201416 SACTA2014

17. REFERENCES FOR TABLE1
 RP1- Kevin Vlaanderen, Slinger Jansen, Sjaak
Brinkkemper, Erik Jaspers, “The agile requirements
refinery: Applying SCRUM principles to software product
management”, Elsevier publications 2010, pp 58-70.
 RP2- Mark C. Paulk, “A Scrum Adoption Survey”, SQP
VOL15, No.2, ASQ, 2013, pp 27-34.
 RP3- Emam Hossain, Paul L. Bannerman, and D. Ross
Jeffery, “Scrum Practices in Global Software Development
Research Framework”, Springer-Verlag Berlin Heidelberg
2011, pp 88-102.
9 August 201417 SACTA2014

18.  RP4- Torgeir Dingsøyr1, Geir Kjetil Hanssen, Tore
Dybå Geir Anker, and Jens Olav Nygaard,
“Developing Software with Scrum in a Small Cross-
Organizational Project”, Springer-Verlag Berlin
Heidelberg, 2006, pp 5-15.
 RP5- Dr. Mark C. Paulk,Noopur Davis,Larry
Maccherone, “On Empirical Research Into Scrum”,
Carnegie Mellon University.
 RP6- Susan Mulder, “An Action Research Study on
the Use of Scrum to provide Agility in Data Warehouse
Development”, 2010,University of Pretoria, .
 RP7- Linda Rising and Norman S. Janoff, “The Scrum
Software Development Process for Small Teams”,
IEEE Software, 2000, pp 27-32.
9 August 201418 SACTA2014

19. REFERENCES
 Hansen M.T., Baggesen H., 2009, “From CMMI and
isolation to Scrum, Agile, Lean and collaboration” In
Proceedings of Agile, pp. 283-288.
 K. Schwaber, M. Beedle, Agile Software Development with
Scrum, Prentice Hall, Upper Saddle River, 2001.
 Paasivaara, M., Durasiewicz, S., Lassenius, C., (2009):
Distributed Agile development: Using Scrum in a large
project. Proceedings of ICGSE 2009, 195–204
 Tore Dyba˚ *, Torgeir Dingsøyr,(2008), “Empirical studies
of agile software development: A systematic review”,
Elsevier publications
 Rising, L., & Janoff, N, The Scrum Software Development
Process for Small Teams. IEEE Software, 17(4), 26–32.
9 August 201419 SACTA2014

20.  Larman, C., & Basili, V. R. (2003). Iterative and
Incremental Development: A Brief History. IEEE
Computer, 36(6), 47–56.
 Boehm, B. (2002). Get Ready for Agile Methods, with
Care. IEEE Computer, 35(1), 64–69.
 Cockburn, A., & Highsmith, J. (2001). Agile Software
Development: The People Factor. IEEE Computer, 34(11),
131–133.
 The State of Scrum (2013).: Benchmarks and Guidelines,
Scrum Alliance.
 Agrawal A., Singh S., Tripathi M., Maurya L.S.,(2014)
“Implementing Agile in Small Organizations”, IJICT,vol 4 ,
no.7,pp 687-692
9 August 201420 SACTA2014

21. THANK YOU
9 August 201421 SACTA2014