SCRUM Agile Development

Frameworks
UNIVERSIDAD DE MANIZALES - SOFTWARE
ARCHITECTURE

• ALEJANDRO GIRALDO. 
• HENRY SANTIAGO CASTRILLON. 
•  SEBASTIAN MARIN.
 Process in which a set of good practices are applied on
a regular basis to work collaboratively, as a team, and
obtain the best possible result of a project, These
practices support each other and their selection is
based on a study of how highly productive teams
work. characterized by:

Adopt a strategy of incremental

SCRUM development, instead of planning and
complete execution of the product.

It is justified in the quality of the result

more in the tacit knowledge of people in
self-organized teams, than in the quality
of the processes used.
 Open the different phases of
development, instead of doing one
after another in a sequential or
cascade cycle.

SCRUM
The project is executed in short time cycles
and fixed duration (iterations that are
usually two weeks, although in some teams
are three and up to four weeks, maximum
limit of real product feedback and
reflection). Each iteration must provide a
complete result.
 SCRUM defines a set of practices and roles, and that can
be taken as a starting point to define the development
process that will be executed during a project.

The main roles in Scrum are:

Characteri
stics Of The Scrum Master: Try to facilitate the application of

SCRUM scrum and manage changes.

The Product Owner: Represents the stakeholders (external

or internal stakeholders).

The Team: Executes the development and other elements

related to it.
01
The auxiliary roles in
"Scrum teams" are those
that do not have a formal
role and are not frequently
involved in the "Scrum
process", however they
must be taken into account.
02
An important aspect is the
practice of involving users,
business experts and other
stakeholders in the process
("stakeholders").
03
There are several
implementations of systems
to manage the Scrum
process, ranging from
yellow "post-it" notes and
blackboards to software
packages.
 Flexibility to changes: Great capacity to react to the changing
requirements generated by the needs of the client or the
evolution of the market. The framework is designed to adapt to
new demands, involve complex projects.

Time to Market reduction: The client starts using the most

Benefits
important features of the project before it is completely
finished.

of
SCRUM Higher software quality: The methodical work and the need to
obtain a functional working version after each iteration, helps
to obtain high quality software.

Greater productivity: This is achieved, among other reasons,

due to the elimination of bureaucracy and the motivation of
the equipment provided by the fact that they can be structured
autonomously.
Maximizes the return on investment (ROI): Creation of software only with
the features that contribute to a higher business value thanks to the
prioritization of return on investment.

Time predictions: Through this working SCRUM framework, the average

speed of the equipment is known, with which it is possible to estimate easily
when you can make use of a certain functionality that is still in the Backlog.

Reduction of risks The fact of developing: The highest value functionalities

and knowing the speed at which the team advances in the project, allows to
effectively clear risks in advance.
THANK YOU