This document discusses Agile and Scrum methodologies for web development projects. It defines Agile as an iterative development process built around self-organizing teams. Scrum is described as one of the most commonly used Agile frameworks, with an emphasis on delivering working software in short iterations called sprints. The document contrasts the Waterfall and Agile approaches, and explains how Scrum's daily stand-up meetings help track progress, plan work, and identify impediments.

1. Agile & Web Development NoVA Geek Girl Dinner #4

2. About Glennette Clark Principal, Lazy Smart | UX Web Strategy, Design & Project Management Email: glennette@lazysmart.com Phone: 202-683-9508

3. What is Agile Founded as a methodologies for software development, Agile is an iterative development process built around self-organizing teams.

4. Agile Methodologies SCRUM Crystal Clear Extreme Programming Adaptive Software Development Feature Driven Development Dynamic Systems Development Method

5. Agile Basics Emphasis on obtaining the smallest workable piece of functionality to deliver business value early and continually improving and adding more functionality throughout the life of the project.

6. Agile vs Waterfall Emphasizes documentation and controlled processes as a measurement of success Emphasizes working software as the primary measure of progress Ill equipped to adapt to change because it tends to fall apart when the problem being measured is constantly changing due to requirement modifications and new realizations about the problem itself Breaks tasks into small increments with minimal planning, and do not directly involve long-term planning which makes it easier to adapt to changes in requirements Progress is generally measured in terms of deliverable artifacts: requirement specifications, design documents, test plans, code reviews Progress is measured by the production of completely developed and tested features (but a very small subset of the whole) every few weeks Structured of the methods, stepping through requirements-capture, analysis, design, coding, and testing in a strict, pre-planned sequence Iterative and incremental development methods' emphasis on building releasable software in short time periods Waterfall Agile

7. Traditional Web Development

8. SCRUM

9. Scrum Web Development 30 days 24 hours Product Backlog As prioritized by Product Owner Sprint Backlog Backlog tasks expanded by team Potentially Shippable Product Increment Daily Scrum Meeting Source: Adapted from Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.

10. Why Scrum Works Scrum revolves around the ethos of simplicity , resulting in delivery of something that moves the project forward: What have you done during the last 24 hours? What do you plan to do in the next 24 hours? What’s stopping you getting on with the work of the next 24 hours? This is useful because: This is progress , it’s work completed to date This is forward planning , it is work you are about to do These are your impediments or obstructions , it might be things you need in order to work…more forward planning. It’s also identification of immediate risks. Why Scrum Works by Craig Murphy, http://www.CraigMurphy.com

11. Why Scrum & Agile Work for Web Development Collaboration across interdisciplinary team Direct involvement of product owner (stakeholders) Flexibility to prioritize features based on budget and time constraints Adaptable to changing requirements and evolving solutions to problems Forward-moving iterative process

12. Resources Agile Software Development -http://en.wikipedia.org/wiki/Agile_software_development Waterfall Method - http://en.wikipedia.org/wiki/Waterfall_model Scrum - http://en.wikipedia.org/wiki/Scrum_(development) Manifesto for Agile Software Development - http://agilemanifesto.org/ Scrum Alliance - http://www.scrumalliance.org Mountain Goat Software - http://www.mountaingoatsoftware.com Agile Project Management with Scrum Ken Schwaber Microsoft Press, 2004 ISBN 073561993X Agile Software Development with Scrum Ken Schwaber, Mike Beedle Prentice Hall, 2002 ISBN 0130676349