The document discusses different software development processes, including Waterfall and Agile. Waterfall involves sequential development in phases without overlap or iteration, which can lead to problems if requirements change. Agile follows four values: individuals and interactions, working software, customer collaboration, and responding to change. It emphasizes iterative development, collaboration between self-organizing cross-functional teams and business people, and adapting to changing priorities. Overall, the document analyzes the advantages of Agile over Waterfall for accommodating changing requirements through continuous planning, development, integration and testing.

1. Choosing commercial software development processUladzimir Liashkevich, © 2009

2. Development processSoftware engineering – systematic and disciplined approachCode & fix - hack until it works Software development methodologiesWaterfallSpiral modelRational Unified ProcessAgile developmentLean development

3. Waterfall: theory

4. Waterfall: how it works

5. Waterfall: time-to-marketSafeguard – Ballistic Missile Defense SystemNo late changes in requirements6 years of development5k person-years$25 blnTerminated after 133 days of operation – new missiles were faster, than anti-missile missiles

6. Waterfall: target aiming

7. Waterfall: target aiming

8. Waterfall: target aiming

9. Waterfall: cost of change

10. Waterfall: problemsPlanning doesn’t workBusiness may change faster than software is developedChanges in requirements are not easyCost of changeProgress is not clear

11. SolutionCommunication & FeedbackContinuousSoftware development as social activityIt is not about applying math methods

12. Agile manifestoIndividuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan

13. Agile vs Waterfall

14. Team buildingFeature teamSits togetherCommon goalMotivated individualsTeam building is hard

15. Involve customerProduct ownerDaily collaborationProduct backlogUser storiesPrototypingPrioritizing backlog

16. Iterative developmentWorking software is the measure of successContinuously deliver valueEarly and oftenValuable feedbackIteration planningHigh priority user storiesStory estimatesAcceptance criteriaIteration scopeImplementationTough things firstTechnical tasks as a part of user storiesComplete featuresContinuous communication

17. Typical Agile life-cycle

18. Agile: target aiming

19. Agile: target aiming

20. Agile: target aiming

21. QualityQuality is freeOnly if you are ready to pay for itExternal qualityZero defect principleInternal qualityTechnological debt

22. Questions?