Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile perversion - Barcelona Software Craftsmanship 2015


Published on

Agile perversion at Barcelona Software Craftsmanship 2015

Published in: Software
  • Be the first to comment

Agile perversion - Barcelona Software Craftsmanship 2015

  1. 1. AGILE PERVERSION by /Javier Salinas @MuSTa1nE
  2. 2. ABOUT ME
  4. 4. AGENDA Waterfall Scrum Agile
  5. 5. Waterfall model Product requirements documentProduct requirements document Software architectureSoftware architecture Implementation Design Requirements Maintenance Verification SoftwareSoftware
  6. 6. WATERFALL PROBLEMS No working software is produced until late. High amounts of risk and uncertainty. It is difficult to measure progress within stages. Cannot accommodate changing requirements. Integration is done as a "big-bang. at the very end, which doesn't allow identifying any technological or business bottleneck or challenges early.
  7. 7. SCRUM
  9. 9. MANIFESTO FOR AGILE SOFTWARE DEVELOPMENT We are uncovering better ways of developing software 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 on the right, we value the items on the left more.
  10. 10. "Agile is ordering tapas until you're full, not ordering a 10-course meal" - Neil Killick
  11. 11. "Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done." - 5th Principle from Agile Manifesto The necessity of estimates is the lack of trust
  12. 12. "Customer collaboration over contract negotiation" - Agile Manifesto
  13. 13. "Until each specific feature is understood in detail, it’s impossible to estimate the cost of a software project accurately." - McConnell That's not very Agile.
  14. 14. date estimated 2011 - terminated on 2015 cost estimated 288 millions - final cost 506 millions
  15. 15. WHY ESTIMATE?
  16. 16. PREDICTION "Working software is the primary measure of progress." - 7th Principle from Agile Manifesto
  17. 17. PRIORITISATION Focus on value not in cost
  18. 18. ANALYSIS & UNDERSTANDING Do it but don't make magic numbers from it
  19. 19. THE NATURE OF SOFTWARE DEVELOPMENT Organising By Feature Planning Feature by Feature Building the product, feature by feature Slice features thinly Build quality in every day
  20. 20. SLICING HEURISTIC “A user story ready to be worked on must have only one acceptance test." - Neil Killick
  21. 21. THANK YOU! CONTACT ME @MuSTa1nE blog: