Page 467 - confbook2022

The Tenth International Arab Conference on Quality Assurance in Higher Education ﻲﻟﺎﻌﻟا ﻢﯿﻠﻌﺘﻟا ةدﻮﺟ نﺎﻤﻀﻟ ﺮﺷﺎﻌﻟا ﻲﻟوﺪﻟا ﻲﺑﺮﻌﻟا ﺮﻤﺗﺆﻤﻟا

Background and Literature Review:
1.4 Definition and Background:

Agile software development (ASD). It has been formally introduced by a group of software practitioners and
consultants in 2001 in the “agile manifesto”, which establishes four fundamental: individuals and interactions over
processes and tools, working software over comprehensive documentation, customer collaboration over contract
negotiation, and responding to change over following a plan [1]. In addition to twelve principles, Agile people follow.
Agile classified as a lightweight methodology in where it is incremental, iterative, cooperative, straightforward and
adaptive [12]. Also minimizes the risk by centering on short iterations [4].
The different ASD Methods are: XP (Beck 1999b), scrum (Schwaber 1995; Schwaber and Beedle 2002), crystal
methodologies (Cockburn 2002a), feature driven development (Palmer and Felsing 2002), the rational unified process
(Kruchten 1999), dynamic systems development (Stapleton 1997), adaptive software development (Highsmith 2000),
open source development (O'Reilly 1999), Agile modeling (Ambler 2002a) and pragmatic programming (Hunt 2000).

Scrum Methodology. The most important approaches are: Scrum, extreme, adaptive and dynamic. Of these, the most
used is Scrum. Scrum is simply an agile, lightweight process for controlling development in rapidly changing
environment, as customers change their mind about the product and the development challenges are unpredictable
by their nature. So Scrum focuses on maximizing the ability of the team to quickly deliver in response to emerging
requirements [8].
This model is built on three major components [4] [12]:
Scrum Roles. Three not boundaries-crossed roles: Scrum Master, Scrum team and product owner.
Scrum Artifacts. .Product backlog, sprint backlog and burndown chart.
Scrum Process activities. Kick-off, sprint planning meeting, sprint, daily Scrum and sprint review meeting (see fig.
1).

Fig. 1. Scrum Process Loop (Andreas Schroeder 2012).

Why Scrum. There is a revolutionary transmit from prescriptive approaches to empirical processes, which maximizes
the results, managers’ works with team, creativity and collaboration are the stamp of this method [22,23]. It
overcomes any unexpected changes [12]. However, there is no method is a “silver bullet”, savvy is where to use each.
Scrum and XP are mostly applicable in studies, having common structures, roles, and values. But fine differences,
for example XP pays more attention on engineering practices [5], which is not our interest here. Whereas Scrum
focuses on management practices, in addition to its spread in industry, it is easy to comprehend, accessible and
effective to introduce agility to undergraduates [2]. And it worth highlighting some orientations weaving that two or
more ASD approaches together were acceptable and productive [6,24].

1.5 Literature Review:

Literature shows no related studies prior to 2001, which were published in Extreme Programming and Agile
Processes [14,15]. In few universities, ASD laboratories and centers appeared. Most authors from North America
and Europe. However, in Arab World there was single Jordanian research [9]. An early literature recommends two
points, all subsequent papers confirm: practices should be one assignment consists of all SWE aspects and creating
heterogeneous groups of student capabilities and interests, which leads to homogeneity among groups [14].
Agile was evolved and utilized widespread in industry, so its teaching in the academia is just a natural response.
It deals with human aspects according to agile manifesto. It is naturally taught in a teamwork-oriented environment.
It promotes diversity. Also supports learning processes. Furthermore, it develops mind habits. Agile emphasizes

٤٤٦