Agile perversion at Barcelona Software Craftsmanship 2015

1. AGILE PERVERSION
by /Javier Salinas @MuSTa1nE

2. ABOUT ME

3. WHAT IS THIS TALK ABOUT?

4. AGENDA
Waterfall
Scrum
Agile

5. Waterfall model
Product requirements documentProduct requirements document
Software architectureSoftware architecture
Implementation
Design
Requirements
Maintenance
Verification
SoftwareSoftware

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.

9. SCRUM

10. XP - EXTREMME PROGRAMMING

11. 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.

12. "Agile is ordering tapas until you're full, not
ordering a 10-course meal" - Neil Killick

13. "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

14. "Customer collaboration over contract
negotiation" - Agile Manifesto

15. "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.

16. date estimated 2011 - terminated on 2015
cost estimated 288 millions - final cost 506 millions

17. WHY ESTIMATE?

18. PREDICTION
"Working software is the primary measure of
progress." - 7th Principle from Agile Manifesto

19. PRIORITISATION
Focus on value not in cost

20. ANALYSIS & UNDERSTANDING
Do it but don't make magic numbers from it

23. 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

24. SLICING HEURISTIC
“A user story ready to be worked on must
have only one acceptance test." - Neil Killick

25. THANK YOU!
CONTACT ME
jsalinaspolo@gmail.com
@MuSTa1nE
blog: http://www.jspcore.com