Agile Web Development C. Daniel Chase University of Colorado at Boulder

Manifesto for Agile Software Development We are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value: Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan That is, while there is value in the items onthe right, we value the items on the left more. February 11-13, 2001

Principles behind the Agile Manifesto We follow these principles: 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.

Principles behind the Agile Manifesto 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.

Principles behind the Agile Manifesto 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.

Principles behind the Agile Manifesto 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.

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

Agile Methodologies Agile Modeling Agile Unified Process (AUP) Agile Data Method Dynamic Systems Development Method (DSDM) Essential Unified Process (EssUP) Extreme programming (XP) Feature Driven Development (FDD) Scrum

Agile Web Techniques Source Code Management Test Driven Development Unit Testing Functional Testing Continuous Integration Design Patterns Refactoring

Source Code Management Version Control Release tracking Development vs Production code lines

Test Driven Development 1. What does this section of code do? 2. Write the Test first! 3. Write code to pass the test 4. Repeat 1-3 as you add more operations

Test Driven Development Unit Testing Component level Finds basic logic & syntax errors Functional Testing Functional Testing Application level Finds business rule & systemic problems

Continuous Integration Automated Check-out Automated Build Automated Testing Immediate Feedback for failures

Refactoring Refactoring improves the readability of code Does not fix bugs or add new functionality! Code smells (Duplicate code, large class or method...) Test first! Refactor code Retest--should pass!

Design Patterns Most problems have been solved before and solutions optimized Using standard constructs makes it easier for both you & others to maintain code Object Oriented Programming (OOP)