The document discusses the waterfall and agile approaches to software development. The waterfall approach is sequential with distinct phases of planning, analysis, design, implementation, and support. It focuses on documentation and following a strict plan. However, it does not allow for feedback or changes once a phase is complete. The agile approach uses iterative cycles to develop software in smaller portions with customer feedback at each stage, allowing for changes and continual learning throughout the process. While less documentation-focused, agile enables quicker response to changes.

1. Breaking from the Waterfall [email_address]

2. My experience as a developer Leading development teams and managing software projects Differences between the academe and the industry

3. Waterfall/”SDLC” What is it? Advantages and disadvantages Agile and Iterative Development What is it? How it differs from waterfall Advantages and Disadvantages Discussion

4. “ Traditional” approach to software dev’t Sequential Design Process Planning, Analysis, Design, Implementation, Support 1970: Paper by Winston Royce Focus on documentation and detail Have a plan (or plans) and stick to it “ Measure twice, cut once” Developers standpoint: clear, but flexible

5. Planning Analysis Design Implementation Support

6. Perfection at every step No progress until each step is completed Documentation Discipline Clearly defined milestones Predict problems before they occur

7. Problems are rarely fully understood Resistance to change Mistakes made at previous steps “trickle down the waterfall” Response to problems that can’t be known before completion No feedback loop Royce’s example

8. Cyclic software development Plan-Do-Check-Act Methods: Agile Scrum Extreme Programming RUP RAD Develop a system in cycles and smaller (functional) portions at a time

10. Feedback Loop Quick response to change (with less investment) Continued learning about the problem Take advantage of what is learned at each iteration Always have a complete functioning system

11. Less focus on documentation Difficult to implement Tendency to start coding before planning Communication overhead Requires a very efficient change control mechanism Requirements are always at risk of changing

12. Test Driven Development Unit Testing Continuous Integration Automated Testing Pair Programming Software Tools Pivotal Tracker

13. Questions?