Sandro Mancuso - Software Craftsmanship

Over ten years on and Agile has become mainstream. However, many projects are still failing. Bugs, bad requirements, dedicated QA teams, long release cycles and a pile of code no one understands and everyone is scared to touch. Developers are still seen and treated as resources and companies are still outsourcing software development to cheaper places, disregarding software quality. So, what developers can do about that? How can we turn this situation around? In this talk we will be discussing what Software Craftsmanship is and how it addresses these problems. Are we really professional software developers? Do we act like professionals? Come along if you are interested to know what is to be a real software craftsman.

Transcript

1. Software Craftsmanship http://www.londonswcraft.com @londonswcraft Sandro Mancuso @sandromancuso
2. Software Craftsmen just care about beautiful code
3. 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.
4. We adopted Agile and now things will be OK … and the Agile Transformation Era began.
5. And then we spend 10 year focusing on... … people, interactions, team building, the ecosystem… .. and processes became more important than technical practices
6. Many Agile projects are now, steadily and iteratively, producing crap mediocre software. The Agile Hangover
7. We want to get things done... … but we are under pressure
8. The wrong notion of time
9. But what is to be Agile anyway?
10. 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.
11. The invisible threat Code quality Time per feature
13. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value:
14. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software
15. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value
16. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals
17. Manifesto for Software Craftsmanship raising the bar As aspiring Software Craftsmen we are raising the bar of professional software development by practising it and helping others learn the craft. Through this work we have come to value: Not only working software, but also well-crafted software Not only responding to change, but also steadily adding value Not only individuals and interactions, but also a community of professionals Not only customer collaboration, but also productive partnerships
18. What is Software Craftsmanship? Software Craftsmanship is all about putting responsibility, professionalism, pragmatism and pride back into software development
19. Does context matter? Does it always matter?
20. How do we know we are building the right thing? How do we know we are building the thing right?
22. Adding value through practices  Automated testing  Test first  Test-Driven Development  Pair-programming  Continuous Integration
23. Don't discuss practices, discuss value.
24. Healthy Intolerance What practices do you use instead that can provide more value?
25. Mastering the practices is hard … … and that's why we practice
26. Perfect practice (narrowing the gap)
27. Software Craftsmanship is a long journey to mastery
28. Software Craftsmanship Attitude - Owning your career - Not a 9 to 5 profession - Practice - Boy scout rule - Expecting promotions
29. The attitude towards legacy code
30. Raising the Bar
31. Software Craftsmanship is not... … a church, trying to convert all developers It's about leading by example and showing how we can be better … about beautiful code It's about continuously delivering value not writing crap code
32. Dogmas & Religious Thinking
33. What problem are you trying to solve? What’s your context?
34. Don’t look for a prescription Understand your context
35. Feedback Software Craftsmanship Lean Agile
36. Customer Satisfaction Software Craftsmanship Lean Agile
37. Craftsmanship is not enough to guarantee the success of a project but the lack of it can be the main cause of its failure
38. London Software Craftsmanship Community - LSCC http://www.londonswcraft.com
39. Thank You http://craftedsw.blogspot.com http://www.londonswcraft.com Sandro Mancuso @sandromancuso