1. Agile & Web Development NoVA Geek Girl Dinner #4
2.
3.
4.
5.
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
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.
![About Glennette Clark ,[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)