1) Software Craftsmanship focuses on producing well-crafted, high-quality software through practices like automated testing, test-driven development, and pair programming. 2) It values not only working software and responding to change, but also steadily adding value and a community of skilled professionals. 3) Being a software craftsman requires continuously improving one's skills through practice and experience over many years to master the craft of software development.

1. Software Craftsmanship
Sandro Mancuso
@sandromancuso
http://leanpub.com/socra

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
~ Corey Haines

24. Mastering the practices is hard …
… and that's why we practice

25. Perfect practice
(narrowing the gap)

26. Software Craftsmanship is a
long journey to mastery

27. Seniority is relative and
transient

28. Software Craftsmanship Attitude
- Owning our careers
- Not a 9 to 5 profession
- Practice
- Boy scout rule
- Promotions

29. The attitude towards
legacy code

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

31. Craftsmanship is not enough to guarantee the
success of a project but the lack of it can be the
main cause of its failure

32. What does it mean to be a
software craftsman?

34. How it is done is as important as having it done
~ Eduardo Namur

36. Are you a software crafter?

37. Thank You
http://leanpub.com/socr
a
Sandro Mancuso
@sandromancuso