Scribd
Upload
159 views16 pages

DevOps Fundamentals: Agile Model Overview

The document discusses the Agile model of software development. It was designed for software teams to achieve continuous value delivery through iterative, time-boxed processes. Key aspects include breaking work into small, frequent iterations rather than large releases, getting work to a deployable state quickly and getting user feedback, and using sprints typically lasting 2-4 weeks. The Agile methodology focuses on collaborative decision making and a cyclical, iterative process to produce working software.

Uploaded by

Aryan Rathore
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
159 views16 pages

DevOps Fundamentals: Agile Model Overview

The document discusses the Agile model of software development. It was designed for software teams to achieve continuous value delivery through iterative, time-boxed processes. Key aspects include breaking work into small, frequent iterations rather than large releases, getting work to a deployable state quickly and getting user feedback, and using sprints typically lasting 2-4 weeks. The Agile methodology focuses on collaborative decision making and a cyclical, iterative process to produce working software.

Uploaded by

Aryan Rathore
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 16

AGILE MODEL

INT 331
Fundamentals of DevOps
 Success in today’s global marketplace hinges upon an
organization’s ability to deliver value, both to its customers
and to its employees. Organizations need to find ways to
move faster and deliver higher quality products and
services to customers, while providing the structure and
stability to promote a healthy organizational culture.

 This is no small feat, and it cannot be accomplished


through slow-moving, traditional corporate structures. To
survive, organizations across the world are adopting the
smarter, more efficient methods used by fast-moving, high-
growth companies.

History of Agile
Agile was designed for software development
teams, as a time-focused, iterative way of
achieving continuous value delivery.
The seeds of Agile were planted decades ago,
but many view a historic meeting of
17 developers at the Snowbird resort in Utah in
2001
as the beginning of modern Agile.
It was during this meeting that the Agile
Manifesto was written. The manifesto outlines
12 principles that have guided the practice of A
gile
throughout recent decades.
 Software development teams began practicing Agile
to improve flexibility, customer / user satisfaction, and
adaptability in the marketplace.

 Instead of deploying software in large, scheduled


releases, Agile promotes breaking work down into
small, frequent iterations. Rather than spending time
gold-plating new releases internally, teams get work to
a deployable state, release as it’s ready, and allow
users to provide feedback on what works, what
doesn’t, and what can be improved.

 Scrum is a subset of Agile used mostly by


development teams, which uses time boxes to iterate
on a product in two-week sprints
Agile SDLC model
 It is a combination of iterative and incremental process
models with focus on process adaptability and customer
satisfaction by rapid delivery of working software product.
Agile Methods break the product into small incremental
builds. These builds are provided in iterations. Each
iteration typically lasts from about one to three weeks.
Every iteration involves cross functional teams working
simultaneously on various areas like −
 Planning
 Requirements Analysis
 Design
 Coding
 Unit Testing and
 Acceptance Testing.
 Agile SDLC methodology is based on collaborative
decision making between requirements and solutions
teams, and a cyclical, iterative progression of
producing working software.

 Work is done in regularly iterated cycles, known as


sprints, that usually last two to four weeks.

 Agile model believes that every project needs to be


handled differently and the existing methods need to
be tailored to best suit the project requirements. In
Agile, the tasks are divided to time boxes (small time
frames) to deliver specific features for a release.
Plan-driven and agile specification
separate Iteration within stage
development Not
stages with the necessarily
outputs to be waterfall
produced at model – plan-
each of these driven,
stages planned incremental
in advance. development is
possible

User's full
agreement at
end, not before
code
Iteration of stage

You might also like