This document discusses software craftsmanship. It outlines an agenda for a weekend code session including exercises on what skills belong to software craftsmanship. It summarizes a book on software craftsmanship which uses the metaphor of traditional craftsmanship with masters, journeymen and apprentices. The document proposes establishing a software craftsmanship think tank to improve skills through mentoring, lunch sessions and defining engineering skills. It outlines upcoming activities like courses and guest speakers to further the topic of software craftsmanship.

1. Sw Craftsmanship- Sioux weekend of code -Roy NitertOctober 2011

2. Agenda© Sioux Embedded Systems 2010 | Confidential | 2What is SW craftsmanship ?Exercise 1Background craftsmanship based on Pete McBreens bookSW Craftsmanship within SiouxExercise 2Wrap-up

3. What is SW Craftsmanship ?© Sioux Embedded Systems 2010 | Confidential | 3What do you think that it is?What activities/skills/attitude belong to it?Lets make a list

4. Exercise© Sioux Embedded Systems 2010 | Confidential | 4Determine what belongs to SW craftsmanship and what notIn two groupsUse flipover and notes with ‘skills’You can make new notes10 minutes to cover all notesKeep discussions to a minimum

5. Skills© Sioux Embedded Systems 2010 | Confidential | 5active listeningarchitectureASDBDD/ATDDbuild automationC#C++clean codecode reviewcoding dojo/katacoding standardcommunicerenconfiguration managementconflict managementcontinuous integrationdesign patternsdocument reviewdocumentingdon’t repeat yourselfeclipseestimatingjavakanbanleadershipmentoringmodel driven developmentOOA/Dpair programmingpeer recognitionpresenterenprojectmatigwerkenreadingrefactoringrequirements engineeringretrospectionRUPscrumSQSSVNTDDteam buildingtest automationtestingUMLunit testingVisual StudioV-model

6. SW Craftsmanship manifesto© Sioux Embedded Systems 2010 | Confidential | 6

7. Agile ManifestoSW craftsmanship manifestoTwo Manifestos© Sioux Embedded Systems 2010 | Confidential | 7Individuals and interactionsWorking softwareCustomer collaborationResponding to changeProcesses and toolsComprehensive documentationContract negotiationFollowing a planA community of professionalsWell-crafted softwareProductive partnershipsSteadily adding value

8. Software Craftsmanship book The New Imperative (1)The software business resides in a constant crisisEngineering only considers development as science, but does not address the social aspectsA different metaphor would be more suitable© Sioux Embedded Systems 2010 | Confidential | 8

9. Software Craftsmanship book The New Imperative (2)Traditional craft: Technical knowledge, practiced skill and aesthetics© Sioux Embedded Systems 2010 | Confidential | 9Roles: Master craftsman, Journeyman, ApprenticeSoftware Craftsmanship book The New Imperative (3)© Sioux Embedded Systems 2010 | Confidential | 10ObjectiveObtain mastery over science and engineering so that we can continually refine our craftRaising the barContinually work to improve your skillsPerpetual learning encourage participation in conferences

10. create a learning environmentSoftware Craftsmanship book The New Imperative (4)© Sioux Embedded Systems 2010 | Confidential | 11Master craftsmanLeads a team of journeymen and apprentices

11. Infects the team with enthusiasm and passion for the craft

12. Has delivered many successful, robust, high-quality applications

13. Is recognized by users, customers and developers

14. Is responsible for passing on the craft

15. Chooses his own teamSoftware Craftsmanship book The New Imperative (5)JourneymanHas worked for several years with a master

16. Small teams

17. Coach apprentices

18. Learn from masters

19. Spread knowledge between masters

20. Focused on delivering applications

21. Does not work without master or other journeyman© Sioux Embedded Systems 2010 | Confidential | 12

22. Software Craftsmanship book The New Imperative (6)© Sioux Embedded Systems 2010 | Confidential | 13ApprenticeContribute to simple tasks

23. Learn from journeyman

24. Situated learning

25. Review work of the master

26. Progression through demonstrated progressSoftware Craftsmanship book The New Imperative (7)© Sioux Embedded Systems 2010 | Confidential | 14Put back pride into SW developmentSign your work

27. Take credit

28. Accountability

29. ReputationNo licensing/certificationCraftsmanship is personal

30. Peer recognition

31. Peer recommendationSoftware Craftsmanship book The New Imperative (8)© Sioux Embedded Systems 2010 | Confidential | 15Management styleNo horde of average programmers

32. Small team of good developers

33. No detailed instructions or command and control

34. Facilitating and coordinating

35. Knowledge workers

36. Pay them well (3 times as much as average developers)

37. More information© Sioux Embedded Systems 2010 | Confidential | 16Books:McBreen, Pete (2001). Software Craftsmanship: The New Imperative. Addison Wesley. ISBN 0201733862.

38. Martin, Robert C. (2008). Clean Code: A Handbook of Agile Software Craftsmanship. Prentice Hall. ISBN 0132350882.

39. Martin, Robert C. (2011). The Clean Coder: A Code of Conduct for Professional Programmers. Prentice Hall. ISBN 0137081073.

40. Hoover, Dave; Oshineye, Adewale. (2009) Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman. O'Reilly. ISBN 0596518382.

41. Hunt, Andrew; Thomas, Dave (1999). The Pragmatic Programmer: From Journeyman to Master. Addison Wesley. ISBN 020161622XManifesto: http://manifesto.softwarecraftsmanship.org/Wiki: http://en.wikipedia.org/wiki/Software_Craftsmanship

42. Think tank© Sioux Embedded Systems 2010 | Confidential | 17SW Craftsmanship Think tankMembers: Duncan Stiphout, Roy Nitert, Tjakko KleinhuisGoal: Improve SW engineering skills by creating a continuous learning environmentActivities:Define engineering skills

43. Follow up on DC survey (Roy)

44. Mentoring (Duncan)

45. Lunch sessions (Tjakko)Mentoring© Sioux Embedded Systems 2010 | Confidential | 18Mentoring is a first step towards master-journeyman-apprentice modelFacilitate pairs of coach and coacheeList of potential coaches availableCoachees are approached during PM talks You can also subscribe yourselfIndication: 2 to 4 hours a monthPaid by personal training budget

46. Lunch sessions© Sioux Embedded Systems 2010 | Confidential | 19Monthly session by different speakerCase driven / with codePossible subjects:Explain one design pattern in depth

47. Explain ‘don’t repeat yourself’

48. Explain one of the SOLID principles

49. Refactoring

50. TDD

51. BDD

52. Code reviewsExercise© Sioux Embedded Systems 2010 | Confidential | 20Againdeterminewhatbelongs to SW craftsmanship and whatnotAdd more skills5 minutes

53. Discussion© Sioux Embedded Systems 2010 | Confidential | 21Do these skillsbelong to SW craftsmanship?Skill1Skill2…

54. Coming up© Sioux Embedded Systems 2010 | Confidential | 22Cursus cafetariaHot-or-notCraftsmanshipPremium courseCraftsmanshipLunch sessionsMentoringKevlinHenney

55. SW Craftsmanship© Sioux Embedded Systems 2010 | Confidential | 23Verbeter je skills,begin bijjezelf

56. 24© Sioux Embedded Systems 2010 | Confidential | roy.nitert@sioux.eu+31 40 2677100roy.nitert