Robert Martin in his book The Clean Coder mention about the Professional Developer, later Sandro Mancuso repeat it in his book Software Craftsmanship. On the several Agile Transformation I coach around the world, I saw the same problem, the process is applied, but the developers continue to work the same way. It is even worse; some company expects process improvement without a new Developer mindset. In December 2008 the Software Craftsmanship manifesto was written. Since then several companies were created around the Software Craftsmanship communities. I will present you what it is about and what are the tools I used to promote Software Craftsmanship in my company and during my coaching missions around the world from Europe to Asia. This presentation is for the developers to become better, but also to the executive that wants to build a better company with excellent software developers than just basic one who at the end will cost more.

1. Professional Developer
XP / Software Craftsmanship / DevOp

2. SPONSORS & PARTNERS

3. Alexandre Cuva
• Co-founder, Agile Coach, Speaker and Trainer at Finix Asia
• Experience with distributed Scrum teams in Vietnam & India
• +19 years of international experience in software development and project manager
• Coached Agile Team in Europe and Asia
• Agile, Lean, DevOp, Craftsmanship, Spotify, SAFe
• Management 3.0, Certified Scrum Developer & SAFe Trainer
• Co-founder of Agile Communities in Vietnam and Switzerland
Speaker
2011 - 2018
Organizer | Speaker
Speaker 2015https://www.linkedin.com/in/cuvaalex
Alexandre.cuva@finix.asia

4. The Developer

5. 1996 – eXtreme Programing

6. 2001

7. 2008 – Craftsmanship / DevOp
Patrick Debois
Andrew Shafer
Sandro Mancuso
Uncle Bob

8. Agile Manifesto
Individuals and Interaction vs process and tools
But also well-crafted software
Working software vs comprehensive documentation
But also steadily adding value
Customer collaboration vs contract negotiation
But also a community of professional
Responding to change vs following a plan
But also productive partnership
Software Craftsmanship
Manifesto

9. Delivering what user want
9

10. Justify technology use
10

11. Keep it releasable
11

12. Automate deployment early
12

13. Get frequent feedback using
demo
13

14. Use short Iterations, release with
Increments
14

15. Coding Feedback
15

16. Use it before your build it
16

17. Automated acceptance test
17

18. Measure real progress
18

19. Listen to user
19

20. Your code must be readable as a
book
20

21. Baby steps
21

22. Keep it simple
22

23. Tell don’t ask
23

24. Schedule regular face time
24

25. Architect must write code
25

26. Be a mentor
26

27. Review code
27

28. Keep other informed
28

29. 29

30. Alexandre Cuva
• Co-founder, Agile Coach, Speaker and Trainer at Finix Asia
• Experience with distributed Scrum teams in Vietnam & India
• +19 years of international experience in software development and project manager
• Coached Agile Team in Europe and Asia
• Agile, Lean, DevOp, Craftsmanship, Spotify, SAFe
• Management 3.0, Certified Scrum Developer & SAFe Trainer
• Co-founder of Agile Communities in Vietnam and Switzerland
Speaker
2011 - 2018
Organizer | Speaker
Speaker 2015https://www.linkedin.com/in/cuvaalex
Alexandre.cuva@finix.asia