Professional Documents
Culture Documents
App Citas Medicas Ingles
App Citas Medicas Ingles
A. SCRUM METHODOLOGY
Agile Scrum Methodology: As written by Troy Dimes, this
methodology is the best solution for those companies that
have to face the obstacles of not having a methodology to
plan a software. This methodology is a function chart to
design software in a confused way and present it in time in
a simpler way. It is a framework within the methodology of
agile software development, which will provide you with the
design of an exquisite software applying a group of patterns
to be followed by the teams and using determined series [8].
1) Phase 1: Product Backlog:
In the Backlog Product the approximate time is 2 minutes,
the User Stories elaborated together with the client will be Fig. 1. Processes of the Scrum methodology
stored, in this stage the functional requirements that will be
implemented, the elaboration of the system will be shown [9].
3) SCRUM Team:
2) Phase 2: Sprint Backlog:
The team working on the methodology has certain charac-
The Sprint Backlog details a set of tasks or list to be performed
teristics such as being multifunctional and multidisciplinary,
by team members, the development of which will allow a bet-
in addition each team member chooses the Sprint that wants
ter implementation of the system. In this particular case, it was
to work and within the team there are analysts, architects,
divided into three main Sprints: Form Filling, Appointment
designers, programmers and testers. The team in the SCRUM
Recording and Appointment Reporting. The development of
methodology has to be formed by 5 or 10 people, each The
this app will be developed in Andoid Studio with kotlin and
member must work full time, and members can exchange
the MariaDB database management system.
Roles during the Sprint [13].
3) Phase 3: Daily Scrum:
Daily Scrum is all those daily meetings at the same time with C. MEETINGS IN THE SCRUM METHODOLOGY
the team that will be held with the client in order to make a
quick inspection of the progress of the current Sprint, i.e. to 1) Sprint Planning Meeting:
discuss the difficulties encountered and to adapt the tasks to It is usually held at the beginning of each meeting and usually
be carried out [9]. lasts about 8 hours. In this part of the meeting the objectives
of each project or Sprint are given, as well as the activities
4) Phase 4: Sprint Review:
and roles of the project [14].
This occurs at the end of each Sprint, to inspect the increment
2) Daily SCRUM Meeting:
and adapt if necessary, where discussions are held with the
This meeting is usually held daily and usually lasts 15 minutes,
development team and the customer on the integration of new
almost always the members are on their feet to save time
requirements based on the outcome of the inspected increment.
and because of the short duration of this meeting, it is not a
5) Phase 5: Retrospective of the Sprint:
meeting to solve problems, but to ask three questions, which
The Sprint Review is the last scrum event and comes after
are: What did you do yesterday, what will you do tomorrow
the Sprint Review, this stage ends the Sprint performed. It
and what are the obstacles to your task? [15].
identifies the improvements for the next Sprint by solving any
3) Sprint Review y Sprint Retrospective:
problems found in the code or application [10].
These are meetings that usually last between 2 and 4 hours,
We will now look at the processes of the Scrum methodol-
in which Sprint Review involves all the members of the
ogy and the steps to be followed to carry them out, as shown
team, whether managers, clients, and all those involved in the
in Fig. 1.
project, where the team has to present what has been achieved
in the Sprint and many times they do it by showing a DEMO.
B. ROLES IN THE SCRUM METHODOLOGY The Sprint Retrospective meeting is only held with members
1) Product Owner: of the Sprint team, it is a feedback meeting and each member
It is responsible for defining the characteristics of the product of the team indicates what is being done well or badly, it
and prioritizes the listing in the ProductBacklog in each also indicates everything that can be improved and how these
iteration. The ProductOwner represents the client, and is improvements will be used [16].
responsible for clarifying the client’s requirements [11].
III. CASE STUDY
2) SCRUM Master:
He is responsible for leading the project and for the successful With the methodology and steps mentioned above, the
completion of each Sprint, he also makes sure that the team processes detailed according to the prototypes of the mobile
works properly in a harmonious, functional and productive application will be explained below, for which a payroll
way [12]. control and monitoring system will be designed.
www.ijacsa.thesai.org 2|Page
(IJACSA) International Journal of Advanced Computer Science and Applications,
Vol. XXX, No. XXX, 2014
according to the previous day’s schedule. These meetings will suitable for the control and booking of medical appointments
be attended by the Area Directors, the General Manager, the in hospitals.
operators, the administrator and the system developer(s). The 1) Software development methodology:
following image shows the communications between the users Methodologies oriented towards customer interaction and in-
of the equipment, which must be constantly related during the cremental software development show partially functional ver-
sketch, as shown in Fig.6. sions of the software to the customer in short intervals of time,
so that he can evaluate and suggest changes to the product as it
develops [18]. These are called Agile methodologies, as shown
in Fig.7.
www.ijacsa.thesai.org 5|Page
(IJACSA) International Journal of Advanced Computer Science and Applications,
Vol. XXX, No. XXX, 2014
www.ijacsa.thesai.org 6|Page