Download - [2017/2018] Agile development
![Page 1: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/1.jpg)
Ivano Malavolta
Agile development
VRIJEUNIVERSITEITAMSTERDAM
![Page 2: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/2.jpg)
Waterfall vs agile: poor visibility
![Page 3: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/3.jpg)
Waterfall vs agile: poor quality
![Page 4: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/4.jpg)
Waterfall vs agile: too risky
![Page 5: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/5.jpg)
Waterfall vs agile: can’t handle change
![Page 6: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/6.jpg)
The agile approach
![Page 7: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/7.jpg)
Risks and features
http://www.testingthefuture.net/wp-content/uploads/2011/12/waterfall_versus_agile_development.png
![Page 8: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/8.jpg)
Agile manifesto
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 tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding 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.
http://www.agilemanifesto.org
![Page 9: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/9.jpg)
How does it work in practice?
You make a list You start executing
You estimate You update the plan “@run-time”
You set priorities
![Page 10: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/10.jpg)
Agile iterations
![Page 11: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/11.jpg)
Technical tools: unit tests
Snippet of test code for exercising some functionality of the product à codified requirements
We will have a dedicated course on testing
![Page 12: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/12.jpg)
Technical tools: test-driven development
Write tests firstRefactoring is less risky now
![Page 13: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/13.jpg)
Technical tools: continuous integrationMerging all the developers’ working copies many times a day à it allows to make sure that all the code integrates, all the unit tests pass, and a warning if anything goes wrong
image from http://newmedialabs.com/
![Page 14: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/14.jpg)
An implementation: SCRUM
AAA
![Page 15: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/15.jpg)
An implementation: SCRUM
http://www.flickr.com/photos/magia3e/6233729753/
![Page 16: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/16.jpg)
An implementation: SCRUM
Burndown chart = how much work is left
Scope changes• The engineering team
missed features in the UI mockups when we created the release backlog
• Integrations into other AdWords features were overlooked
• The rate of change in AdWords APIs is very high.
![Page 17: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/17.jpg)
Critical evaluation of the agile method+ Acceptance of change à less risky+ Frequent and short iterations+ Emphasis on working code+ Associating a test with every piece of functionality
+ tests are a key resource within the project
+ Continuous integration (and delivery)+ Planned– Tests as a replacement for specifications– Feature-based development & ignorance of
dependencies– No quality plan– Dismissal of a priori architecture work
– actually, dismissal of everything which is non-shippable
![Page 18: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/18.jpg)
References
![Page 19: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/19.jpg)
Suggested readings
1. Striebeck, M., "Ssh! We are adding a process... [agile practices],"Agile Conference, 2006 , vol., no., pp.9 pp.,193, 23-28 July 2006
2. Nicolò Paternoster, Carmine Giardino, Michael Unterkalmsteiner,Tony Gorschek, Pekka Abrahamsson, Software development instartup companies: A systematic mapping study, Information andSoftware Technology, Volume 56, Issue 10, October 2014, Pages1200-1218, ISSN 0950-5849
3. Alfonso Fuggetta and Elisabetta Di Nitto. 2014. Software process. InProceedings of the on Future of Software Engineering (FOSE 2014).ACM, New York, NY, USA, 1-12.
![Page 20: [2017/2018] Agile development](https://reader031.vdocuments.us/reader031/viewer/2022030318/5a6d320d7f8b9ae5418b4f65/html5/thumbnails/20.jpg)
ContactIvano Malavolta |
Assistant professorVrije Universiteit Amsterdam
iivanoo
www.ivanomalavolta.com