The Agile Manifesto and Agile Software Development, Slides of Software Engineering

Download The Agile Manifesto and Agile Software Development and more Slides Software Engineering in PDF only on Docsity!

AGILE SOFTWARE

DEVELOPMENT

Lecture 4

Recap

■ Agile software development

■ Agile Model

The Agile Manifesto

■ In February 2001, the below mentioned 17 software developers met at the Snowbird resort in Utah to discuss lightweight development methods. They published the Manifesto for Agile Software Development.

■ The authors were:

Kent Beck, James Grenning, Robert C. Martin, Mike Beedle, Jim Highsmith, Steve Mellor, Arie van Bennekum, Andrew Hunt, Ken Schwaber, Alistair Cockburn, Ron Jeffries, Jeff Sutherland, Ward Cunningham, Jon Kern, Dave Thomas, Martin Fowler and Brian Marick.

The Agile Manifesto (cont…)

■ We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

— Individuals and interactions over Processes and tools

— Working software over Comprehensive documentation

— Customer collaboration over Contract negotiation

— Responding to change over Following a plan

■ That is, while there is value in the items on the right, we value the items on the left more.

Working Software

over

Comprehensive Documentation

■ Working software is more useful and welcome than just presenting documents to clients in meetings.

■ We’re not paid to develop documentation, we’re paid to develop software.

■ Of course that doesn’t mean that documentation is unimportant, but it has to be considered relative to its cost in delivering functionality (i.e, software).

Customer collaboration over Contract negotiation

■ Requirements cannot be fully collected at the beginning of the software development cycle, therefore continuous customer or stakeholder involvement is very important.

■ The primary purpose of collaboration is to work with the customer to make sure that they are involved in delivering the final product they need.