Practices and obstacles in agile development
-
Upload
grgur-grisogono -
Category
Technology
-
view
267 -
download
3
description
Transcript of Practices and obstacles in agile development
![Page 1: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/1.jpg)
Practices and Obstacles in Agile Development
![Page 2: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/2.jpg)
Who am I?
Thorsten Suckow-Homberg, born 1976PHP & Javascript since 1999Sencha since 2007Agile since 2008working for Germany's 1st certified Sencha Partner: eyeworkers interactive GmbH, Karlsruhe (jobs.eyeworkers.de)
@thorstensuckow
![Page 3: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/3.jpg)
All repairs tend to destroy the structure, to increase the entropy and disorder of the system. Less and less effort is spent on original design flaws; more and more is spent on fixing flaws introduced by earlier fixes. As time passes, the system becomes less and less well-ordered. Sooner or later the fixing ceases to gain any ground. Each forward step is matched by a backward one. Although in principle usable forever, the system has worn out as a base for progress.
![Page 4: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/4.jpg)
All repairs tend to destroy the structure, to increase the entropy and disorder of the system. Less and less effort is spent on original design flaws; more and more is spent on fixing flaws introduced by earlier fixes. As time passes, the system becomes less and less well-ordered. Sooner or later the fixing ceases to gain any ground. Each forward step is matched by a backward one. Although in principle usable forever, the system has worn out as a base for progress.
Frederick Brooks, The Mythical Man-Month, 1975
![Page 5: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/5.jpg)
Manifesto for Agile Software Development
[...]Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan[...]
http://agilemanifesto.org
![Page 6: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/6.jpg)
What exactly does „agile“ mean?being flexible
What is the goal of being agile?Delivering working software while adapting to changing circumstances
![Page 7: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/7.jpg)
For this talk, let's clearify:Agile development:SCRUM
Traditional Software DevelopmentWaterfall Model
![Page 8: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/8.jpg)
Introducing AD to your company
![Page 9: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/9.jpg)
„Start small“ vs „All-In“
choose pilot project and use it's success as an indicator whether your company will benefit from AD
Adapt to AD company wide overnight
![Page 10: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/10.jpg)
„Going Stealth“ vs „Public Display“
stealth keeps the pressure off your team
public display proves your commitment towards AD
![Page 11: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/11.jpg)
Patterns for spreading SCRUM
Split and Seed
![Page 12: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/12.jpg)
Patterns for spreading SCRUM
Split and SeedGrow and Split
![Page 13: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/13.jpg)
Patterns for spreading SCRUM
Split and SeedGrow and SplitInternal Coaching
![Page 14: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/14.jpg)
Different Roles for your Team
![Page 15: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/15.jpg)
http://sarahseeandersen.tumblr.com
![Page 16: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/16.jpg)
Reasons for resisting change
Lack of awarenessFear of the unknownLack of job securityFear of losing control and authority
![Page 17: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/17.jpg)
New Roles
Scrum MasterProduct Owner
The Team:DB administratorsArchitectsUI designerProgrammer
![Page 18: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/18.jpg)
Technical Practices
![Page 19: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/19.jpg)
„Later never comes.“
![Page 20: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/20.jpg)
Technical Practices
Test Driven Development
Write code
Fix compile errors
Step through code in debugger
Repeat (few
times a day)
Write failing test
Write just enough code to pass the test
Refactor
Repeat (few
times an hour)
![Page 21: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/21.jpg)
Technical Practices
Collective Code Ownership
Avoid Knowledge Islands!
![Page 22: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/22.jpg)
Technical Practices
Pair Programming (split and seed, CCO)
RefactoringHave some spare time?
Continuous Integration
![Page 23: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/23.jpg)
Thank you!
![Page 24: Practices and obstacles in agile development](https://reader035.fdocuments.in/reader035/viewer/2022081401/559ceb8d1a28ab1e708b4726/html5/thumbnails/24.jpg)
Resources
Books:
Succeeding with Agile, Mike Cohn, Addison Wesley
The Agile Samurai, Jonathan Rasmusson, Pragmatic Bookshelf
Scrum, Roman Pichler, dpunkt verlag
Agile Software Development, Robert C. Martin, Pearson Education
Refactoring, Martin Fowler, Addison Wesley
Continuous Integration, Paul M. Duvall, Addison Wesley