Content uploaded by Sabbir M. Saleh
Author content
All content in this area was uploaded by Sabbir M. Saleh on Dec 15, 2019
Content may be subject to copyright.
2019 International Conference on Electrical, Computer and Communication Engineering (ECCE), 7-9 February, 2019
978-1-5386-9111-3/19/$31.00 ©2019 IEEE
Comparative Study within Scrum, Kanban, XP
Focused on Their Practices
Sabbir M. Saleh
Department of Computer Science and
Enginering
City University
Dhaka, Bangladesh
saleh.sabbir.aiub@gmail.com
Syed Maruful Huq
Department of Electrical and Computer
Engineering
Presidency University
Dhaka, Bangladesh
maruf@pu.edu.bd
M. Ashikur Rahman
Department of Computer Science and
Enginering
University of South Asia
Dhaka, Bangladesh
ashiknsu@gmail.com
Abstract— There are quite a few up-to-date and every so
habitually used Agile style but among those Scrum, Kanban
and XP (Extreme Programming) are generally the most
mutual. On instance, organizations use typically tools and
techniques from any but rather a lot they use roughly of the
amalgamations of those approaches. Devouring in cognizance
that those approaches are just a framework they allow firms to
adapt it for their particular tasks as well as for other limits.
Scrum, Kanban, and XP frameworks manage and deal with
the advancement of Software Development. These frameworks
are utilized in various circumstances and work processes.
Subsequently, they are compelling for various Agile
collaborators and tasks in different circumstances. However,
the utilization of a wrong approach or practice prompts
Software System Development procedures that are unbendable
and inefficient, affecting the association and instigating
wasteful advancement. Incorporators of Scrum, Kanban, XP
trust that the erroneous performs of these frameworks remain
hazardous and in this manner, Agile workmates ought to be
aided in their basic leadership. The idea of this paper is to
decide the fundamental variables to ruminate amid the
determination of Scrum, XP and Kanban frameworks. The
recognizable proof of elements was directed over a top to
bottom audit of the essential task, subsequently, the documents
scrutiny was utilized in the investigation concerning
information. By way of found, system recommendation, people,
and tasks, adoption phase, team capacity, group stature,
prioritizing of requirements, functionality scope, prime
interval, operational observes, budget, and eminence were the
primary aspects that lead Agile coworkers in preference
Scrum, XP or Kanban and in accumulation their practices.
This paper portrays a strategy to perform inspections on Agile
approaches, in view of an arrangement of important highlights
and characteristics.
Keywords— Comparative Study, Scrum, Kanban, XP, Agile
I. I
NTRODUCTION
Agile technique is the fundamental idea because a
gathering of developing a software strategy that relate to
standards of the Agile Manifesto. The three techniques –
Scrum, Kanban, XP are created in light of these qualities and
standards. The qualities underscore on: "people and
communications, working software, client cooperation, and
reacting to change". Collusion refines the qualities caught in
their statement into 12 standards, following are some of the
standards [1]:
i. Our most noteworthy need is to fulfill the client
through right on time and constant conveyance of
cherished software.
ii. Welcome evolving necessities, even late being
developed. Agile procedures bridle change for the
client's upper hand.
iii. Often provide workable software with a tendency to
a short time from a little time to several months.
The former depend on the Agile Manifesto [1]. A scope
of practices has been produced to use on Scrum, XP and
Kanban strategies to cross and accomplish the qualities and
these standards. This paper exhibits a method to analyze and
order Agile Frameworks, utilizing as criteria an arrangement
of chose properties. The procedure expects to be a
commitment for the making of a manual for help developers
and Agile coworkers on the choice of the product
advancement strategy (concentrating on Agile strategies) that
best fits a given improvement setting.
A few overview results certified the prevalence of Agile
techniques with deference over viability and accomplishment
instead of the customary strategies [2-4]. Scrum is among the
original Agile techniques [5, 7]. It is between the splendidly
chosen Agile strategies when managements change to Agile
pattern [6, 8-10, 13, 14, 15]. In the interim, Kanban is the
instant-age Agile techniques [3, 7]. This strategy is
prevalently utilized by associations universally [11, 12]. The
other most well-known Agile pattern is Extreme
Programming (XP) [18]. XP comprises in IV stages:
Designing, Writing in code, Projecting, and Testing. XP can
adjust modifications whenever [18]. These techniques have
been utilized by a large number of firms the world over [16].
In any case, Agile coworkers concur that single strategy does
not meet at all [11, 17], neither Scrum nor Kanban or XP is
appropriate for completely undertakings [11]. Consequently,
a correlation must require for thrice of them center around
software design and development direction.
Scrum is an immaterial group of patterns used broadly
inside the business [8] equally portrayed near the Scrum
Alliance. The three sections of a Scrum assemble are the
Scrum Master (SM), Product Owner (PO), and a
Development Team [19, 20]. In Scrum, from each one
gathering deals their assignments by the strategy for four
collectibles: a Product Backlog, a Sprint Backlog, a Product
Increase, and Definition of Done [21]. The Scrum gather is
required to execute five actions to attain its destinations.
These actions are Backlog Elaboration, Sprint Planning,
Daily Scrum Meeting, Sprint Reviews, plus Sprint
Retrospective. Scrum is in this manner saw as a prescriptive
procedure [21].
Interestingly with Scrum, the Kanban strategy is in all
actuality less unequivocal to the extent its required patterns
and norms; Kanban is to a lesser extent unbending
conversely with Scrum [3, 5]. Regardless, Kanban is seen as
an earth-shattering method acting as of this procedure can
manage the challenges that the past systems couldn't [8] and
winds up being all the more intense for bunches in passing
on business regard additive [8]. In the execution of Kanban,
typically, the essential patterns that engage system
improvement are; imagining the work procedure by applying
Kanban board, confining act ahead of time by abridging the
amount of characteristics to be realized, administer and
evaluate stream, build techniques unequivocal, completing
feedback finally surrounding plus upgrading agreeably and
reliably [22]. Like Scrum, Kanban is extremely subject to
self-dealt with gatherings. The system moreover requires the
irregular condition of relationship of expert really taking
shape of various practices, which encourage the Agile use in
the affiliation.
Other than these, in 1990, Beck contemplated that
correspondence, ease, visit feedback and quality are the key
characteristics for upgrading the system of Software change
[24]. In light of these characteristics, XP was suggested in
1999 [29] to calm the issues induced by broad stretches of
headway less evaluation from the customer that was till by
and so (plus even) essential in various Software wanders. To
achieve this point, XP suggests a course of action of 12
patterns that should be used in computer programming
wanders [25], [26]. XP advises a course of action of patterns
and thoughts that assistance the resolution, the evocation and
the examination of the necessities (i.e., examination time of
the presence cycle, and importance of the customer stories)
[27]. Regardless, picking the right system will choose the
accomplishment of an item headway [23].
Consequently, this research basically directs to ascertain
the modules that assist the affiliates from the Agile groups in
foremost from Scrum, Kanban, plus XP or by utilizing these
approaches together in the use of different problems,
considering the methods' tendency and obstructions with the
objective that productive outcome can be developed.
Laterally, these methods are considered first to gain data
on their practices, norms, complexities, and likenesses, while
thinking the authorization of assurance aspects.
Particular segments must be considered while picking the
sensible Agile system [28] or scaling Agile strategies [29].
To ensure productive Software wanders, partners of any
affiliation must be stressed over endeavor organization [21].
In such way, Kanban, Scrum and XP systems are fitting in
managing the assignments and making them adequately [30].
This method study of the present inspection establishes that
the determination to pick the Scrum or Kanban or the XP
system or develop a blend methodology for these requires an
insight of the components influencing the assurance. It is in
like manner indispensable to alter the characteristics of each
procedure according to the estimation of system
arrangement, parts and commitments, choice time, aggregate
measure, bunch gauge, essentials priorities, functionality
measure, time interval, specific patterns, price and caliber as
this would aid the gathering in picking whether to habit a one
corresponding methodology or grasping a creamer [30].
II. R
ELATED
WORK
Such area talks about a concise foundation of Scrum,
Kanban, and XP techniques when they began to develop and
also every one of their fundamental parts, patterns, and
resolutions.
A. Scrum
Scrum alludes to a structure that empowers the Agile
colleagues to make and keep up composite items and it is
esteemed to be the strategy portrayed aside
straightforwardness and whippersnapper. In any case, the
technique is as yet difficult to completely acquire and
actualize [19]. Furthermore, Scrum empowers the colleagues
to utilize diverse procedures and techniques [19]. Scrum is
attached by decides that articulate the occasions, parts, plus
antiquities, oversee connections plus associations amid them.
It puts weight on the self-association of groups that are not
repelled by outside individuals. Besides, Agile individuals
utilizing Scrum need to involve a group that is sufficiently
little to stay adaptable however sufficiently expansive to
accomplish extensive work in a run. All the more
particularly, five to eleven colleagues in a group, on the
consideration of the Product Owner plus Scrum Master, is
thought to be the fairest size towards the advancement group
[19].
Differentiating to Kanban, Scrum sets down different
parts [12, 32, 33]. For example, the item proprietor is
basically in charge of the administration of item build-up, the
advancement group is in charge of conveying a releasable
addition of the item after each dash, while the Scrum ace is
in charge of ensuring that Scrum technique is fathomed by
all and is viably utilized [19, 32]. The Scrum Master is a
worker pioneer of the individuals from the advancement
group. Table 1 displays the Scrum strategy works on
including a concise meaning of every one.
As to characterization, the broke down techniques are
fundamentally the same as, both XP and Scrum relate an
offered need to every one of the evoked necessities in view
of the business esteem that every prerequisite has for the
customer, which may now and again uncover to be a
shortsighted priorities framework. Also, Scrum does not
propose systems for discovery and goals of contentions
within software prerequisites [27].
TABLE I. SCRUM
REHEARSES
EXPLANATIONS
Rehearses Explanation
Product Backlog
(PBL) [19]
Product Backlog is depicted as the rundown of
the whole highlights and necessities that should
be executed [19, 33, 34]. The debut and support
of the Backlog of Product dwell the custody of
the item proprietor, plus on everything/highlight
in the item overabundance, a need plus assessed
exertion are reserved [19, 36].
Sprint Backlog
(SBL) [19]
A Backlog of Sprint is depicted by means of an
arrangement of exercises that need doing all
through a Sprint [19, 33, 34]. Each movement or
adjust exercises remains a portrayal of a thing of
PBL that must remain incorporated into the
following discharge, to be presented after the
present Sprint closes [19, 33].
Sprint Burn down
Chart [19]
This outline speaks to the rest of the Sprint
Backlog work that must be every day refreshed,
inside which the appraisal of the advancement is
evaluated against the cycle objectives [19, 15].
Specialists by and large need to evaluate the
achievement of the rest of the
assignments/stories for each Sprint Backlog [19].
Effort Estimation
[19]
The whole individuals that comprise the group
utilizing Scrum strategies build utilization of
trouble neck and neck and exertion layer for
function approximation [19, 33]. Exertion
topping, a preoccupied system of measurement,
is likewise utilized [19].
Sprint [19] Within the core of Scrum dwells Sprint, which is
alluded to while a period package of poly
calendar month or fewer, plus inside a term, a
finished, usable and releasable item addition is
created [19, 35]. Based on this exact research,
the discoveries demonstrated that larger part of
sources that connected Scrum remained inside a
fourteen-day length Sprint [19]. Be that as it
may, it very well may be a four or half year's
Sprint [33, 20]. Besides, changes can't be made
after the group settles on the Sprint to be taken
after however in a few occasions, the item
proprietor can drop the said Sprint despite the
fact that it might bring about assets [19].
Sprint Planning [19] Sprint Planning principally expects to achieve a
choice with respect to what can be conveyed in
the present 2 to about a month Sprint and the
manner in which the work will be accomplished
to convey the augmentation [19, 20].
Daily Stan
d
-up
Meetings [19]
This mirrors the meetings that are held day by
day for around 15 minutes with the point
towards breaking down the venture advance,
with positive and negative criticism [19].
Additionally, in the gathering, the sudden issues
that could postpone the venture are raised,
alongside the work to be directed preceding the
following gathering [19, 35, 17]. For expansive
groups, every day Scrum won't give the normal
incentive to the colleagues [19, 37].
Sprint Review [19] After each Sprint, the individuals from the group
including the client, hold a survey meeting that
is gone to by the whole partners, amid which
every one of the highlights of the new discharge
is exhibited [19, 33]. It was demonstrated that
client input amid the Sprint audit meeting
expanded the nature of each Sprint [32]. Thus,
client inclinations and criticism are required [38,
39].
Sprint Retrospective
[19]
A Sprint Retrospective means to advance talks
among the coworkers concerning the issues that
they experience and how they can be dealt with
later on Sprints [19, 35]. This empowers
designers to sharpen their adequacy through
conduct change in view of the conditions
experienced [19, 35, 32].
B. Kanban
Taiichi Onho created KANBAN in the late 1940s to
control production among forms and to actualize Just-in-
Time (JIT) producing at Toyota fabricating plants in Japan.
In Agile, the Kanban technique was presented by David
J. Anderson on 2003/2004 when he was endeavoring to help
a little Microsoft group of coming up short [12]. Be that as it
may, Anderson just sent the subtle elements of Kanban to
Developing of a Software following 6 years, in 2010 [22,
31]. Kanban basically means to defend the group from the
unending errands appropriated by an administration, with an
endeavor to acknowledge progressing improvement pace
with adaption like other Agile strategies, where almost no
protection from change emerges [31, 41]. All the more
particularly, Kanban technique has its premise on the Just-in-
Time (JIT) preface, especially when it manages Software
Development, demonstrating that the group should abstain
from the advancement of Software highlights before their
interest. At the end of the day, the group isn't upheld to
create or convey highlights that are not required keeping in
mind the end goal to relieve squander and keep up the same
to be more like zero [42].
The Kanban strategy makes utilization of visual Kanban
board to enhance Software Development through the
showcase of various periods of the procedure of
advancement. It isn't as prescriptive as Scrum in that it
doesn't have characterized jobs, no accentuation on
gatherings and no ancient rarities [4]. The significant
standards of Kanban are work process representation through
the board of Kanban, restricting entity advance by limiting
the amount of highlights to represent executed,
administration with estimation of a stream, clarifying
arrangements, actualizing input, circling and improving
coordinated effort in a ceaseless way [22]. The patterns plus
meaning for Kanban are exhibited in the following table 2 as
takes after.
TABLE II. KANBAN
REHEARSES
EXPLANATIONS
Rehearses Explanation
Visualize the
workflow [22]
Visualizing the work process involves making the work
required to be noticeable for the whole coworkers as
undetectable work adds to the danger of undertaking
usage. Through the Kanban board, the work process
can be plainly visualized [32, 30].
Limit work in
progress [22]
This is the primary practice in Kanban that alludes to
restricting the measure of work in progress (WIP) or
diminishing the WIP highlights [32, 43]. In such a
manner, it was confirmed that when the measure of
performing multiple tasks is decreased, an opportunity
to convey the highlights is additionally diminished [7,
32].
Manage and
measure flow
[22]
Flow management team fundamentally expects to
complete the product in a method that individually
state in the work process is checked and detailed in
what is known as estimating stream. In this manner, the
development will be convenient and smooth, making
opportune esteem, alleviating hazard and maintaining a
strategic distance from the expense of postponement
[32].
Make explicit
policies [22]
The larger part of associations has certain arrangements
considering the different work composes to be dealt
with. Kanban groups set out the strategies expressly for
their predictable application [7, 32, 30].
Feedback
Implementatio
n [22]
Kanban needs criticism circles to work and in that
capacity [32, 43], it utilizes the standup meeting,
benefit conveyance audit, activities survey and hazard
survey to empower the correlation between expected
results and real results and to make the compulsory
changes [32].
Continuous
development
[22]
The cleared up and shared the understanding in regards
to work speculations, workflow, process, and hazard
help the coworkers to build up a common
comprehension of an issue and to propose
improvements that can be concurred on consistently
[32]. The group should utilize a mind called Kaizen
[29, 44] that esteemed to remain a noteworthy piece of
viable utilization in Kanban.
C. XP
Extreme Programming (XP) is one of the famous Agile
Practices. It has just been set up to be exceptionally
successful at numerous associations of every extraordinary
size and preparations worldwide [40].
XP is a trifling plan technique created through Kent
Beck, Ward Cunningham, and others. After prominent
successes, XP has been producing gigantic intrigue, and no
little measure of debate. A significant part of the intrigue
originates from XP's realistic way to deal with improvement.
Key practices incorporate combine programming, composing
tests forthright, visit refactoring and revamp constant joining
and testing. Key standards incremental and iterative
improvement, working with the most straightforward
arrangement, removing superfluous documentation, and
aggregate code possession [45].
XP is actualized with 12 practice. In [46] these are
known as the hover of life. They are the soul of extreme
programming. Each practice all by itself can be portrayed as
far as their adherence to the 4 estimations of XP. They
likewise cooperate to shape an entire that is substantially
more noteworthy than the total of the parts. The practices and
meaning of XP are exhibited in table 3 as takes after.
TABLE III. XP
REHEARSES
EXPLANATIONS
Rehearses Explanation
Small
Releases [47]
Get the framework into generation apace. This is a key
factor in aiming input on the real programming [47].
Metaphor
[47]
See how the entire framework functions. It is similar
critical for the client to comprehend the representation
alon
g
side the software en
g
ineers [47].
Simple
design [47]
One from the central qualities is straightforwardness.
The framework ought to exist intended on behalf of the
highlights that follow executed today. Let the futurity
direct how the framework develops to that degree, don't
attempt or foresee the imminent, you’ll likely not be
right [47].
Testing [47] Criticism is additionally the another key quality.
Testing incorporates unit tests, which developers
compose, acknowledgment tests, which clients
compose. Test is the pointer of fruition [47].
Refactor [48] Developers are in charge of enhancing the plan of
existing programming without changing its conduct.
Refactoring is a piece of the software engineer's regular
exercises [47].
Pair
Programming
[47]
Functioning with an accomplice remains a prerequisite
during writing the implementation code [47].
Collective
ownership
[47]
Anybody on the group can change any piece of the
framework [47].
Continuous
integration
[47]
Developers incorporate and assemble the product all
the time [47].
Sustainable
working
hours [47]
A superior name is a work until tired. Be that as it may,
know about the drawbacks of working an excessive
number of hours numerous weeks in succession [47].
On-site client
[47]
The client is in the group, accessible to response
inquiries in time. The client is likewise in charge of
com
p
osin
g
acknowled
g
ment tests [47].
Coding
standards
[47]
Correspondence is a key esteem. Receiving coding
models enhances correspondence in light of the fact
that the code is
p
redictable from class-to-class [47].
III. R
ESEARCH
M
ETHOD
These studies are mainly carried out to examine and
determine the suitability of Scrum, Kanban and Extreme
Programming frameworks. A review was thus conducted to
assess the relevant and accessible studies in the description
of methodological standards. These frameworks then
highlight the divergences and resemblances. This study also
examines the elements affecting the choice of these methods.
The critique was based on keywords, the type of study, the
language and publishing year. We have used keywords for
searching for papers in English from the year 1997 and
review on-
• Review on the approaches of Scrum, Kanban, and XP.
• Review on the comparison between miscellaneous
approaches of Scrum, Kanban, and XP.
• Review on the patterns, parts, and duties on the
approaches in Scrum, Kanban, and XP.
• Review on the chosen arguments from the approaches in
Scrum, Kanban, and XP.
In this research, we are going to consider about which
method to choose between Scrum, Kanban, and XP for the
best practice by the team members to deliver the quality
software to the customer. This study selected the publications
as early as 1997. In 1997, it was when Refactoring was
followed by the programmers and later a practice in XP [48],
though XP was proposed in 1999 by Kent Beck [47]. In
2001, the Agile strategies turned into the theme of
enthusiasm inside the analysis network and organizations
after the publishing of AGILE Manifesto [2]. The qualitative
study was executed on the chosen contextual analyses, with
regards to this investigation, the detections involve the
comparisons and correlations of Scrum, Kanban, and XP and
also the components indicating the determination of these
strategies. The research aspire wants to find out the gains and
restrictions of practicing Agile frameworks in software
industries. In this paper, we develop further research queries
for exploration.
RQ1: In the implementation of software practices, what
factors should be addressed?
RQ2: What are the main features of the factors chosen?
RQ3: How can the team members help with these
characteristics?
We aim to classify with RQ1, the main components
linked with the development of software teams want to
benefit from agile methodologies. We intend to classify the
main elements that will impact the Agile working place. RQ2
plan to inquire the proper definitions, characterizations, and
explanations of those elements. On the basis of qualifying
practices, we try to develop an policy in order to help the
developers take advantage of Agile procedures by using
RQ3.
A
NSWERS AND
D
ISCUSSION
In light of this audit, it was discovered that the Scrum
technique has been broadly received more than Kanban or
XP [8-10, 58]. The contrasts between these strategies as
featured in writing are specified in Table IV beneath.
The comparative study between these that the previous is
a recommended strategy with unmistakable jobs and
obligations regarding the improvement group [19, 3, 4]. In
addition, the group size is more adjustable in Kanban and XP
than in Scrum, whereas the WIP size of Scrum is one, two or
one month in the sprint, but the estimate of Kanban and XP
WIP is relatively low (it very well may be as little as hourly
cluster) [5, 56]. In connection to this, Kanban permit
organized prerequisites day by day and XP permits organized
necessities continually, while prerequisites must be
organized based upon the length in the run while adopting
Scrum [5, 59, 49]. Furthermore, in Kanban the component
extent is little compared to that of Scrum and XP[ 7, 57], but
one industry is halved when moving from Scrum to Kanban
[7] in timeframes between proposing another element and
building a requirement and sending it on its customer site.
In addition, writing shows that evaluations and time
boxes that are not precise given longer lead times are
squandering [31]. Likewise, Kanban is more expensive than
Scrum’s [10] focal points especially for activities [11], but
XP relies more on the simplicity of expense revision[ 57].
Kanban and XP also focus more on improving quality
software [11, 31, 57]. Both Scrum and Kanban have no
specialized practices in terms of their comparability,
although XP has specialized practices [55, 56]. In view of
our third research question RQ3, Agile software
development workers have difficulty in receiving Scrum and
Kanban techniques. Agile coworkers believe that they are
trying to select Scrum over Kanban, or Scrum over XP, or
Kanban over Scrum, or Kanban over XP, or XP over
Kanban, or XP over Scrum, or these three strategies in a mix
when they are updating a given undertaking. In determining
the Scrum, Kanban and XP strategies, consideration must be
given to the choice of elements. Agile collaborators should
be helped by this important decision. In this analysis, an
internal and external survey of the letter was conducted to
inspect the elements of choice for those systems. They can
all work a couple. However, the main factors that can help
Agile employees identify themselves for a large number of
purposes are the jobs, duties, acceptance times, team
measurement, WIP size, requirement arrangements, size
features, time, methodologic preparation, budget and
software quality. These factors lead to limited waste and the
probability that project delays will occur.
TABLE IV. SCRUM,
KANBAN,
XP
REHEARSES
EXPLANATIONS
ANSWERS RQ2 MAIN FEATURES OF THE CHOSEN FACTORS
RQ1 Scrum Kanban XP
Jobs & Duties Predefined jobs and duties regarding each
colleague, including Product Owner, Scrum Master,
and others [19, 5, 51, 17, 44]
No predefined jobs and duties [4,
5, 51, 17, 44]
Predefined jobs and duties including
customer, programmer, coach, and
others [54, 55]
Acceptance
time
Snags facing major change might be expert [7]. In
any case, the majority of the links receive Scrum
b
efore Kanban [11]
Less hard change [7], mainly
when groups that keep up and
leaders need to move from [11]
Effect possibly littler if the group
effectively received with SCRUM
[58].
Team
Measurement
With consideration of Scrum Master and Product
Owner, a team contains 5-11 members [19, 36]. On
the off chance that the group is wide, it will be
difficult to offer some benefit to all Agile
coworkers [36]. So, for huge groups, Kanban is
su
p
erior to Scrum [53]
Kanban has greater adaptability
when contrasted with Scrum [53],
in that group can have under 5
colleagues [52], or it very well
may be more than 11 (up to 14
collea
g
ue
)
[53]
Team size should be 5 or less people
[57], XP groups exist tiny. Some of
the time they are even single
individual group. Be that as it may,
they can play out the hardest software
industr
y
actions [54].
WIP Size Substantial clump measure (short of what multi-
month Sprint) is thought to be enormous
particularly when managing consistent changes [5,
11]. The group should focus on conveying runs on
time [5, 51, 17]
It must have little groups with
little measure of WIP [4, 7, 11,
51]. This shows day by day/hourly
carriage of vital kits should be
possible [5]. Duty isn't obligatory
[5, 51, 17]
Small batch size (less than two weeks
sprint) is considered, normally one
week [56]
Requirements
plan
The requisites require listing based on the length of
the run, each two, three or a month [5, 44]
The listing of basics is done
always, which can be every
da
y
/hourl
y
[5, 44]
The listing of prerequisites is done
always [26, 49]
Features size It is portrayed by little component measure [7, 11] It can be classified into little
pieces, which can show helpful
when the expert group needs
q
uicker criticism [7, 11]
Acmes to be created are organized by
the client. Much the same as Scrum,
XP centers around business esteem
[57]
Principal time Scrum abstains from cutting principal time
dissimilar to Kanban [21]
Kanban cuts principal time by
avoiding performing various tasks
and restricting the WIP highlights
[11, 13, 22, 17]
XP is an approach that was calm
mostly to bear the major trials of
group inside the most partial events of
time [54].
Technical
p
re
p
aratio
n
There has no adept drills in Scrum [24, 44] There has no specialized uses in
Kanban [25, 44]
XP has specialized practices [55, 56]
Budget Not at all like Kanban, Scrum keeps away from cost
sparing yet it focuses more on info, skill and basic
control in li
g
ht of what is known [11]
Spotlights on slicing cost when
contrasted with Scrum [11],
p
articularl
y
for activities [11]
XP always follow the ease way to
amended the cost in a reasonable way
[57]
Software
Quality
The Sprint evaluation gathering represents the main
technique for quality improvement in the Scrum
framework [26]
When we want to compare with
Scrum, it fixates mostly on
performance improvement in
Kanban [11, 21]
The more test, the more be adept and
viable in their accent tasks [57]
IV. C
ONCLUSION
AND
F
UTURE
W
ORKS
Project managers and other leaders constantly find it
difficult to select the most reasonable agile framework for a
especial project. When choosing an Agile framework, a
range of choice elements should be deliberated. A
Systematic Literature Review must be adopted to help
project managers to make this critical choice, so that the
most definite Agile Strategies are identified by the essential
factors.
Agile frameworks have a few downsides as well, we are
arranging in our future work to propose an advanced
framework based on the Agile technique for espousing it
better by the Agile Team members.
R
EFERENCES
[1] Agile Alliance, "Agile Manifesto," Online at <http://www.
agilemanifesto.org>, vol. 6, 2001.
[2] S. W. Ambler, “The Non-Existent Software Crisis: Debunking the
Chaos Report,” Available: <http://www.drdobbs.com/architecture-
and-design/the-non-existent-software-crisis-debunki/240165910>,
11 September, 2014.
[3] N. Nikitina and M. Kajko-Mattsson, "Developer-driven big-bang
process transition from SCRUM to Kanban," in Proceedings of the
2011 international conference on software and systems process, 2011,
pp. 159-168.
[4] H. Kniberg and M. Skarin, Kanban and SCRUM-making the most of
both: Lulu. com, 2010.
[5] R. Cuellar, "Kanban for Help Desks: Managing the Unplannable,"
Cutter IT Journal, vol. 24, p. 23, 2011.
[6] R.H. Al-Ta’ani and R. Skarin, "A Framework for Requirements
Prioritisation Process in an Agile Software Development
Environment: Empirical Study," International Journal on Advanced
Science, Engineering and Information Technology, vol. 6, pp. 846-
856, 2016.
[7] A. Shalloway, "Demystifying Kanban," Cutter IT Journal, vol. 24, p.
12, 2011.
[8] A.M.M. Hamed and H. Abushama, "Popular agile approaches in
software development: Review and analysis," in Computing,
Electrical and Electronics Engineering (ICCEEE), 2013 International
Conference on, 2013, pp. 160-166.
[9] R.V. Anand and M. Dinakaran, "Popular Agile Methods in Software
Development: Review and Analysis," International Journal of
Applied Engineering Research, vol. 11, pp. 3433-3437, 2016.
[10] A.S. Campanelli and F. S. Parreiras, "Agile methods tailoring–A
systematic literature review," Journal of Systems and Software, vol.
110, pp. 85-100, 2015.
[11] D. Verweij and O. Maassen, "Kanban at an Insurance Company in the
Netherlands," The Viral Growth of Kanban in the Enterprise, Cutter
IT Journal, 2011.
[12] D. J. Anderson and A. Roock, "An agile evolution: why Kanban is
catching on in Germany and around the world," Cutter IT Journal,
vol. 24, p. 6, 2011.
[13] R. H. AL-TA'AN I and R. Razali, "Process Model for Systematic
Requirements Prioritisation Process in an Agile Software
Development Environment Based on 5S Approach: Empirical Study,"
Journal of Theoretical & Applied Information Technology, vol. 95,
2017.
[14] O. N. Al-Allaf, "The Adoption of Agile Processes in Large Web
Development Enterprises: A Survey in Jordan," IJWA, vol. 2, pp.
206-216, 2010.
[15] F. Ahmad, F. Baharom, and M. Husni, "Agile development methods
for developing web application in small software firms," in
Knowledge Management International Conference (KMICe), 2012.
[16] S. Denning, "Why Agile can be a game changer for managing
continuous innovation in many industries," Strategy & Leadership,
vol. 41, 2013, pp. 5-11.
[17] M. Alqudah and A.A. Abdallah, "Implementing computer-aided
language learning tool using hybrid agile method: A case study," in
Informatics and Creative Multimedia (ICICM), 2013 International
Conference on, 2013, pp. 174-180.
[18] S. S. Samarawickrama and I. Perera, "Continuous scrum: A
framework to enhance scrum with DevOps," 2017 Seventeenth
International Conference on Advances in ICT for Emerging Regions
(ICTer), Colombo, 2017, pp. 1-7.
[19] J. Sutherland and K. Schwaber, "The SCRUM guide. The definitive
guide to SCRUM: The rules of the game," SCRUM. orgOctober,
2013.
[20] J. López-Martínez, R. Juárez-Ramírez, C. Huertas, S. Jiménez, and C.
Guerra-García, "Problems in the Adoption of Agile-Scrum
Methodologies: A Systematic Literature Review," in Software
Engineering Research and Innovation (CONISOFT), 2016 4th
International Conference in, 2016, pp. 141-148.
[21] A.A. Hamid and Z. Mansor, "Client’s Readiness Assessment Success
Factors for Outsourcing Software Projects," International Journal on
Advanced Science, Engineering and Information Technology, vol. 6,
2016.
[22] D. J. Anderson, "Kanban," ed: Blue Hole Press Sequim, WA, 2010.
[23] Z. Mansor, S. Yahya, and N. H. Arshad, "Towards the Development
of Success Determinants Charter for Agile Development
Methodology," International Journal of Information technology and
Engineering, vol. 2, pp. 1-7, 2011.
[24] M. C. Paulk. Extreme Programming from a CMM Perspective. IEEE
Softw., 18(6):19–26, 2001.
[25] K. Beck. Embracing Change with Extreme Programming. Computer,
32(10):70–77, 1999.
[26] K. Beck, C. Andres. Extreme Programming Explained: Embrace
Change. Addison-Wesley, 2nd edition, 2004.
[27] Fernandes, J. M., & Almeida, M. (2010). Classification and
Comparison of Agile Methods. 2010 Seventh International
Conference on the Quality of Information and Communications
Technology. doi:10.1109/quatic.2010.71
[28] M.K. Alqudah and R. Razali, "Key Factors for Selecting an Agile
Method: A Systematic Literature Review," International Journal on
Advanced Science, Engineering and Information Technology, vol. 7,
pp. 526-537, 2017.
[29] M. Alqudah and R. Razali, "A Review of Scaling Agile Methods in
Large Software Development," International Journal on Advanced
Science, Engineering and Information Technology, vol. 6, 2016.
[30] H. Lei, F. Ganjeizadeh, P.K. Jayachandran, and P. Ozcan, "A
statistical analysis of the effects of SCRUM and Kanban on software
development projects," Robotics and Computer-Integrated
Manufacturing, vol. 43, pp. 59-67, 2017.
[31] D.I. Sjøberg, A. Johnsen, and J. Solberg, "Quantifying the effect of
using kanban versus SCRUM: A case study," IEEE software, vol. 29,
pp. 47-53, 2012.
[32] S. Govindaraj and S. Tadipatri, "Use of Kanban in distributed
offshore environments," The Viral Growth of Kanban in the
Enterprise, Cutter IT Journal, 2011.
[33] V.T. Heikkila, M. Paasivaara, and C. Lassenius, "Scrumbut, but does
it matter? a mixed-method study of the planning process of a multi-
team scrum organization," in Empirical Software Engineering and
Measurement, 2013 ACM/IEEE International Symposium on, 2013,
pp.85-94.
[34] S. Ashraf and S. Aftab, "Latest Transformations in Scrum: A State of
the Art Review," International Journal of Modern Education and
Computer Science(IJMECS), Vol.9, No.7, pp.12-22, 2017.DOI:
10.5815/ijmecs. 2017.
[35] Y. Andriyani, "Knowledge Management and Reflective Practice in
Daily Stand-Up and Retrospective Meetings," in International
Conference on Agile Software Development, 2017, pp. 285-291.
[36] C. Kaur1st and V. Kumar 2nd, "Product Backlog Prioritization in
Scrum: A Review," International Journal of Modern Computer
Science (IJMCS) vol. Volume 3, Issue 2, June, 2015.
[37] V.G. Stray, Y. Lindsjorn, and D.I. Sjoberg, "Obstacles to efficient
daily meetings in agile development projects: A case study," in
Empirical Software Engineering and Measurement, 2013 ACM/IEEE
International Symposium on, 2013, pp. 95-102.
[38] M. Alqudah, Y. Yusof, S. A. M. Noah, and A. Almabhouh,
"Incorporating Prioritized User Preferences in Search System,"
International Journal on Advanced Science, Engineering and
Information Technology, vol. 2, pp. 401-404, 2012.
[39] M. K. Al-Qudah, "A Weighted-Based Approach To Prioritize User
Preferences In Information Retrieval," Universiti Utara Malaysia,
2008.
[40] Saleh, S.M., Rahman, A.M., Asgor, K.A. Comparative Study on the
Software Methodologies for Effective Software Development.
International Journal of Scientific & Engineering Research, Volume
8, Issue 4, April-2017
[41] A. Bolaji, "A cross-disciplinary systematic literature review on
Kanban," Master’s Thesis. University of Oulu. 62 p. Available at:
<http://jultika. oulu. fi/files/nbnfioulu-201502111073.pdf>, 2015.
[42] T. Skeie, "Does Limit on Work-In-Progress (WIP) in Software
Development Matter?," 2014.
[43] M.O. Ahmad, J. Markkula, and M. Oivo, "Kanban in software
development: A systematic literature review," in Software
Engineering and Advanced Applications (SEAA), 2013 39th
EUROMICRO Conference on, 2013, pp. 9-16.
[44] G.S. Matharu, A. Mishra, H. Singh, and P. Upadhyay, "Empirical
study of agile software development methodologies: A comparative
analysis," ACM SIGSOFT Software Engineering Notes, vol. 40,
2015, pp. 1-6.
[45] Beck, K. (1999). Extreme Programming. Proceedings Technology of
Object-Oriented Languages and Systems. TOOLS 29 (Cat.
No.PR00275). doi:10.1109/tools.1999.779100
[46] Jeffries, R, Hendrickson, C., Anderson, A., Extreme Programming
Installed, Addison-Wesley, 200 1
[47] Newkirk, J. (2002). Introduction to agile processes and extreme
programming. Proceedings of the 24th International Conference on
Software Engineering - ICSE ’02. doi:10.1145/581441.581450
[48] Fowler, M. Refactoring: Improving the Design of Existing Code,
Addison-Wesley, Reading MA, 1997
[49] Beck, K., & Fowler, M. Planning extreme programming: Addison-
Wesley Professional; 2001
[50] Harris, R., & Cohn, M Incorporating Learning and Expected Cost of
Change in Prioritizing Features on Agile Projects. Extreme
Programming and Agile Processes in Software Engineering;
2006.p.175-180.
[51] M.O. Ahmad, P. Kuvaja, M. Oivo, and J. Markkula, "Transition of
software maintenance teams from Scrum to Kanban," in System
Sciences (HICSS), 2016 49th Hawaii International Conference on,
2016, pp. 5427-5436.
[52] P. Brodzinski, “When Kanban is the Best Choice”. Available:
<http://brodzinski.com/2010/06/kanban-best-choice.html>.
(2010,April).
[53] V. Moskalenko, “SCRUM vs. Kanban: Which to Choose for Agile
Development?"Available:<https://www.luxoft.com/blog/vmoskalenk
o/SCRUM-vs-kanban-which-to-choose-for-agile-development/>.
(2015, March).
[54] Ira Maniuk, “Extreme Programming Team”, April 11, 2016
Available: <https://hygger.io/blog/extreme-programming-team/>
[55] <https://www.agilealliance.org/glossary/xp>
[56] Mike Cohn, “Differences Between Scrum and Extreme
Programming”.Available:<https://www.mountaingoatsoftware.com/bl
og/differences-between-scrum-and-extreme-programming>, April 6,
2017.
[57] Sanjeev Raman, “eXtreme Programming The Methodology”.
Available:<https://www.infoq.com/articles/implementing-xp-
methodology>, April 02, 2014.
[58] Tolfo, C., & Wazlawick, R. S. (2008). The influence of organizational
culture on the adoption of extreme programming. Journal of Systems
and Software, 81(11), 1955–1967. doi:10.1016/j.jss.2008.01.014
[59] F. Kanwal, K. Junaid, and M.A. Fahiem, "A hybrid software
architecture evaluation method for fdd-an agile process model," in
Computational Intelligence and Software Engineering (CiSE), 2010
International Conference on, pp. 1-5, 2010.
