Your SlideShare is downloading. ×
0
Software CraftsmanshipSandro Mancuso       http://www.londonswcraft.com@sandromancuso       @londonswcraft
Software Craftsmen just care about          beautiful code
Agile Software DevelopmentWe are uncovering better ways of developing software by doing it and    helping others do it. Th...
We adopted Agile and now things will be OK … and the Agile Transformation Era began.
And then we spend 10 year focusing on... … people, interactions, team building, the ecosystemProcess and Interactions beca...
The Agile Hangover  Many Agile projects are now, steadily anditeratively, producing crap mediocre software.
We want to get things done...   … but we are under pressure
The wrong notion of time
But what is to be Agile anyway?
Agile Software DevelopmentWe are uncovering better ways of developing software by doing it and    helping others do it. Th...
The invisible threat Codequality                Time per feature
Manifesto for Software Craftsmanship                                raising the barAs aspiring Software Craftsmen we are r...
Manifesto for Software Craftsmanship                                raising the barAs aspiring Software Craftsmen we are r...
Manifesto for Software Craftsmanship                                raising the barAs aspiring Software Craftsmen we are r...
Manifesto for Software Craftsmanship                                raising the barAs aspiring Software Craftsmen we are r...
Manifesto for Software Craftsmanship                                raising the barAs aspiring Software Craftsmen we are r...
What is Software Craftsmanship?Software Craftsmanship is all about putting  responsibility, professionalism, pragmatism an...
Does context matter?Does it always matter?
How do we know we are building        the right thing?How do we know we are building        the thing right?
Adding value through practicel  Automated testingl  Test firstl  Test-Driven Developmentl  Pair-programmingl  Continu...
Dont discuss practices,     discuss value.
Healthy IntoleranceHow can you add more value and/or havesmaller feedback cycles when not using our                practic...
Mastering the practices is hard …    … and thats why we practice
Perfect practice  (narrowing the gap)
Software Craftsmanship is a   long journey to mastery
Software Craftsmanship Attitude- Owning your career- Not a 9 to 5 profession- Practice- Boy scout rule- Expecting promotions
The attitude towards    legacy code
Why would we want to be better        developers?
Software Craftsmanship Movement- Pragmatic Programmer and Software Craftsmanship books are   published (1999 and 2001)- De...
Software Craftsmanship is not...… a church, trying to convert all developers  Its about leading by example and showing how...
Raising the Bar
Stop...    … being miserable and negative    … spreading your frustrations
The only way to have people buying into what you believe is if they see you happy.
Craftsmanship is not enough to guarantee the success of a project but the lack of it can be the main cause of its failure
Agile and Craftsmanship complement each other and both are necessary.Agile processes assume technical excellence and a pro...
London Software Craftsmanship     Community - LSCC    http://www.londonswcraft.com
Thank YouSandro Mancuso           http://craftedsw.blogspot.com@sandromancuso          http://www.londonswcraft.com
Software Craftsmanship - Sandro Mancuso - BCS Agile Methods SG
Upcoming SlideShare
Loading in...5
×

Software Craftsmanship - Sandro Mancuso - BCS Agile Methods SG

1,879

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,879
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
16
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Software Craftsmanship - Sandro Mancuso - BCS Agile Methods SG"

  1. 1. Software CraftsmanshipSandro Mancuso http://www.londonswcraft.com@sandromancuso @londonswcraft
  2. 2. Software Craftsmen just care about beautiful code
  3. 3. Agile Software DevelopmentWe 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. 4. We adopted Agile and now things will be OK … and the Agile Transformation Era began.
  5. 5. And then we spend 10 year focusing on... … people, interactions, team building, the ecosystemProcess and Interactions became more important than technical practices
  6. 6. The Agile Hangover Many Agile projects are now, steadily anditeratively, producing crap mediocre software.
  7. 7. We want to get things done... … but we are under pressure
  8. 8. The wrong notion of time
  9. 9. But what is to be Agile anyway?
  10. 10. Agile Software DevelopmentWe 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. 11. The invisible threat Codequality Time per feature
  12. 12. Manifesto for Software Craftsmanship raising the barAs 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:
  13. 13. Manifesto for Software Craftsmanship raising the barAs 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
  14. 14. Manifesto for Software Craftsmanship raising the barAs 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
  15. 15. Manifesto for Software Craftsmanship raising the barAs 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
  16. 16. Manifesto for Software Craftsmanship raising the barAs 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
  17. 17. What is Software Craftsmanship?Software Craftsmanship is all about putting responsibility, professionalism, pragmatism and pride back into software development
  18. 18. Does context matter?Does it always matter?
  19. 19. How do we know we are building the right thing?How do we know we are building the thing right?
  20. 20. Adding value through practicel  Automated testingl  Test firstl  Test-Driven Developmentl  Pair-programmingl  Continuous Integration
  21. 21. Dont discuss practices, discuss value.
  22. 22. Healthy IntoleranceHow can you add more value and/or havesmaller feedback cycles when not using our practices?
  23. 23. Mastering the practices is hard … … and thats why we practice
  24. 24. Perfect practice (narrowing the gap)
  25. 25. Software Craftsmanship is a long journey to mastery
  26. 26. Software Craftsmanship Attitude- Owning your career- Not a 9 to 5 profession- Practice- Boy scout rule- Expecting promotions
  27. 27. The attitude towards legacy code
  28. 28. Why would we want to be better developers?
  29. 29. Software Craftsmanship Movement- Pragmatic Programmer and Software Craftsmanship books are published (1999 and 2001)- Dec, 2008: Meeting in US defining a set of principles for Sofware Craftsmanship- Feb, 2009: First Software Craftsmanship Conference in London- Mar, 2009: Software Craftsmanship Manifesto- Apr, 2009: Craftsman swap between Obtiva and 8th Light- Aug, 2009: First SCNA conference in Chicago- Oct, 2009: Apprenticeship Patterns is published- Aug, 2010: LSCC was founded- Oct, 2010: Second edition of conferences in London and Chicago- Sep, 2011: Software Craftsmanship Conference in Germany
  30. 30. Software Craftsmanship is not...… a church, trying to convert all developers Its about leading by example and showing how we can be better… about beautiful code Its about continuously delivering value not writing crap code
  31. 31. Raising the Bar
  32. 32. Stop... … being miserable and negative … spreading your frustrations
  33. 33. The only way to have people buying into what you believe is if they see you happy.
  34. 34. Craftsmanship is not enough to guarantee the success of a project but the lack of it can be the main cause of its failure
  35. 35. Agile and Craftsmanship complement each other and both are necessary.Agile processes assume technical excellence and a professional attitude.Software Craftsmanship takes technical excellence and professionalism to a whole new level.
  36. 36. London Software Craftsmanship Community - LSCC http://www.londonswcraft.com
  37. 37. Thank YouSandro Mancuso http://craftedsw.blogspot.com@sandromancuso http://www.londonswcraft.com
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×