Scribd
Upload
213 views

Agile Methodology

Agile methodology is an alternative to traditional project management that uses incremental, iterative work periods called sprints to allow for flexibility and incorporation of feedback. It focuses on collaborative work between self-organizing teams to deliver working software frequently, ideally every few weeks, with a priority on customer satisfaction and response to changing needs. The Agile Manifesto from 2001 laid out principles for agile development that emphasize individuals and interactions, working software, customer collaboration, and response to change.

Uploaded by

ravideshmukhsharp
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
213 views

Agile Methodology

Agile methodology is an alternative to traditional project management that uses incremental, iterative work periods called sprints to allow for flexibility and incorporation of feedback. It focuses on collaborative work between self-organizing teams to deliver working software frequently, ideally every few weeks, with a priority on customer satisfaction and response to changing needs. The Agile Manifesto from 2001 laid out principles for agile development that emphasize individuals and interactions, working software, customer collaboration, and response to change.

Uploaded by

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

Agile Methodology

What is Agile?

Agile methodology is an alternative to traditional project management, typically


used in software development. It helps teams respond to unpredictability through
incremental, iterative work cadences, known as sprints. Agile methodologies are an
alternative to waterfall, or traditional sequential development.
Agile means readiness for motion, nimbleness, activity, dexterity in
motion
Agile came about as a solution to the disadvantages of the waterfall methodology.
Instead of a sequential design process, the Agile methodology follows an
incremental approach.
Developers start off with a simplistic project design, and then begin to work on
small modules. The work on these modules is done in weekly or monthly sprints,
and at the end of each sprint, project priorities are evaluated and tests are run.
These sprints allow for bugs to be discovered, and customer feedback to be
incorporated into the design before the next sprint is run.
The process, with its lack of initial design and steps, is often criticized for its
collaborative nature that focuses on principles rather than process.
It is about how to work together to achieve a common goal. This article focus on
how technology team work together well to plan, build and deliver software.
its an on-going philosophy based on continuous improvement
It is about how to work together to achieve a common goal. This is not only suitable
for software developers but also for Team Leaders, Project Managers, Product
Managers, Development Managers, Testers, QA Managers, QA Engineers, Technical
Writers, UX Designers, anyone involved in the delivering software.
Trends :Many developers have lived through the nightmare of a project with no practices to
guide it. The lack of effective practices leads to unpredictability, repeated error, and
wasted effort. Customers are disappointed by slipping schedules, growing budgets,
and poor quality. Developers are disheartened by working ever-longer hours to
produce ever-poorer software.

We get very confused about deadlines, dates, estimates, and all of the things we
are supposed to be doing, and we do them badly. This will improve your professional
life and the effectiveness of your team.
Agile development is not a methodology in itself. It is an umbrella term that
describes several agile methodologies. At the signing of Agile Manifesto in 2001,
these methodologies included Scrum, XP, Crystal, FDD, and DSDM.
The principles and values of agile software development were formed as a way to
help teams to break the cycle of process inflation and mainly focus on simple
techniques for achieving their goals. The goal?? What is the the goal?
OK, the main goal of every software developer and every development team is to
deliver the highest possible value to employers and customers. Yet our projects fail,
or fail to deliver value.

Characteristics of Agile Software Development

Light Weighted methodology

Small to medium sized teams

vague and/or changing requirements

vague and/or changing techniques

Simple design

Minimal system into production

Modularity
Iterative
Time-bound
Incremental
Convergent
People-oriented

Collaborative

Existing Agile Methods


Extreme Programming (XP)

Agile Unified Process

Scrum

Scrum
It is an Agile S/w development method for project management
Characteristics:

Prioritized work is done.

Completion of backlog items

Progress is explained

Agile Software Development

Principles behind the Agile Manifesto


We follow these principles:
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.

Welcome changing requirements, even late in


development. Agile processes harness change for
the customer's competitive advantage.
Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale.
Business people and developers must work
together daily throughout the project.
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
The most efficient and effective method of
conveying information to and within a development
team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.
Continuous attention to technical excellence
and good design enhances agility.
Simplicity--the art of maximizing the amount
of work not done--is essential.
The best architectures, requirements, and designs
emerge from self-organizing teams.
At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.

Advanyages :

provide processes, tools, and techniques


Agile methodologies address many situations for which Plan-driven
methodologies are not well suited
Agile is still a disciplined approach to software development but with an
emphasis on different aspects of the process

Agile emphasizes continual communication and ability to adapt to changes


and uncertainty
Highly iterative to achieve quality over lots of gates to control quality
Inspect work as it is being done over Inspect product when it is complete
Start with a goal of filling a need over Start by predicting what will be
delivered

Customer satisfaction by rapid, continuous delivery of useful software.

People and interactions are emphasized rather than process and tools.

Customers, developers and testers constantly interact with each other.

Working software is delivered frequently (weeks rather than months).

Face-to-face conversation is the best form of communication.

Close, daily cooperation between business people and developers.

Continuous attention to technical excellence and good design.

Regular adaptation to changing circumstances.

Even late changes in requirements are welcomed.

The participants in an agile process are not afraid of change. They view changes to
the requirements as good things, because those changes mean that the team has
learned more about what it will take to satisfy the customer. Agile team members
work together on all aspects of the project. Each member is allowed input into the
whole. No single team member is solely responsible for the architecture or the
requirements or the tests. The team shares those responsibilities, and each team
member has influence over them.
There are many agile processes: SCRUM, Crystal, Behavior-Driven Development
(BDD), Test-Driven Development (TDD), Feature-Driven Development (FDD),
Adaptive Software Development (ADP), Extreme Programming (XP), and more...
However, the vast majority of successful agile teams have drawn from all these
processes to tune their own particular flavor of agility. These adaptations appear to
come together with the combination of SCRUM and XP, in which SCRUM practices
are used to manage multiple teams that use XP.
A good agile team picks and chooses the management and technical
practices that best work for them. When trying to adopt Agile practices, there

will be a ton of excuses as why it wont work. Those who understand the real
benefits of the approach and genuinely want to make the transition will
likely have success. Those who are searching for reasons why it will fail well,
they will likely find them and either abandon the effort entirely or end up
practicing what Elisabeth Hendrickson calls fake agile

When should you use Agile methodology?


1. When rapid production is more important than the quality of the product.
2. When clients will be able to chance the scope of the project.
3. When there isnt a clear picture of what the final product should look like.
4. When you have skilled developers who are adaptable and able to think
independently.
5. When the product is intended for an industry with rapidly changing standards.

You might also like