Scribd
Upload
11 views2 pages

Agile Manifesto

Agile is a software development approach focused on continual improvement, team collaboration, and early delivery, originating from a 2001 meeting of 17 individuals who sought to prioritize customer satisfaction over excessive planning. The Agile Manifesto emphasizes four key values: prioritizing individuals and interactions, delivering working products over comprehensive documentation, fostering customer collaboration, and responding to change rather than strictly adhering to plans. Since its inception, Agile principles have been widely adopted, transforming the software development landscape.

Uploaded by

abhijitsingh3rdtime
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
11 views2 pages

Agile Manifesto

Agile is a software development approach focused on continual improvement, team collaboration, and early delivery, originating from a 2001 meeting of 17 individuals who sought to prioritize customer satisfaction over excessive planning. The Agile Manifesto emphasizes four key values: prioritizing individuals and interactions, delivering working products over comprehensive documentation, fostering customer collaboration, and responding to change rather than strictly adhering to plans. Since its inception, Agile principles have been widely adopted, transforming the software development landscape.

Uploaded by

abhijitsingh3rdtime
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/ 2

Agile is a term used to describe software development approaches that employ

continual planning, learning, improvement, team collaboration,


evolutionary development, and early delivery.
The origin story
In early 2001, against the backdrop of the Wasatch Mountains, in Snowbird,
Utah, 17 people met to discuss the future of software development. The group’s
members shared a frustration about the current state of affairs, even if they
disagreed about how to remedy the situation.
The problem, they agreed, was that companies were so focused on excessively
planning and documenting their software development cycles that they lost
sight of what really mattered—pleasing their customers.
Companies may have touted corporate values like “excellence” and “integrity,”
but these values did little to guide people—especially software developers—
toward a better way. That needed to change. The Agile Manifesto composed of
just 68 words, and the short and sweet document went on to change software
development forever. In the nearly two decades since its creation, these words
(and the 12 principles that follow) have been embraced (in varying degrees) by
countless individuals, teams, and companies.
Agile Manifesto
1. Individuals and interactions over processes and tools

This value of the Agile manifesto focuses on giving importance to communication with the clients.
There are several things a client may want to ask and it is the responsibility of the team members to
ensure that all questions and suggestions of the clients are promptly dealt with.

2. Working product over comprehensive documentation

In the past, more focus used to be on proper documentation of every aspect of the project. There
were several times when this was done at the expense of the final product. The Agile values dictate
that the first and foremost duty of the project team is completing the final deliverables as identified
by the customers.

3. Customer collaboration over contract negotiation

Agile principles require customers to be involved in all phases of the project. The Waterfall
approach or Traditional methodologies only allow customers to negotiate before and after the
project. This used to result in wastage of both time and resources. If the customers are kept in the
loop during the development process, team members can ensure that the final product meets all the
requirements of the client.

4. Responding to change over following a plan

Contrary to the management methodologies of the past, Agile values are against using elaborate
plans before the start of the project and continue sticking to them no matter what. Circumstances
change and sometimes customers demand extra features in the final product that may change
the project scope. In these cases, project managers and their teams must adapt quickly in order to
deliver a quality product and ensure 100% customer satisfaction.

You might also like