Top 4 values of Agile Manifesto and Introduction to Agile Manifesto | Graspskills Training

The Agile Manifesto - Introduction to Agile Manifesto

Manifesto for Agile Software Development is a formal proclamation of values andprinciples that guide and support an iterative approach to software development and also project teams to successfully implement the agile methodology.

" In 1990, a group of software developers uncovered lightweight software development methods.

Later in the year 2001, the seventeen software developers met to discuss these lightweight development methods. And, together they published Manifesto for Agile Software Development."

The 4 values of Agile Manifesto

Individuals and Interactions over processes and tools
Working Software over comprehensive documentation
Customer Collaboration over contract negotiation
Responding to Change over following a plan

1. Individuals and Interactions over processes and tools

It suggests valuing people on a project team rather than processes and tools used. Though processes and tools are one of the most important substances of any project, it's the people who develop and deliver a software product. This value requires forming a team of skilled software developers, acquiring the right set of skill, communicate, cooperate and owns the outcome altogether that results in success or failure.

2. Working Software over comprehensive documentation

Any working software would leave a better impression on the clients in comparison to the documents presented. Though documentation takes a tremendous amount of time to be presented, it is not an exception. It will help the users and co-workers refer and understand what the software is and how it works.

This value as a whole highlight that the aim of implementing agile methodology is to develop a software which is definite and serves the business needs.

3. Customer Collaboration over contract negotiation

Agilemanifesto proclaims customer collaboration over contract negotiation as no one can tell you an end user's needs for software better than them. The development team may not analyze the business requirements as the beginning of software development lifecycle. Collaboration with customer facilitates regular feedback's which makes it easier for the development team to meet the business's end-users requirement.

4. Responding to Change over following a plan

The agile manifesto proclaims that an agile development team must be capable of responding to changes and proceed with the development lifecycle to deliver efficient software that provides organizations with a competitive edge over competitors.