Software Craftsmanship - Sandro Mancuso - BCS Agile Methods SG
Upcoming SlideShare
Loading in...5
×
 

Software Craftsmanship - Sandro Mancuso - BCS Agile Methods SG

on

  • 1,679 views

 

Statistics

Views

Total Views
1,679
Views on SlideShare
1,241
Embed Views
438

Actions

Likes
1
Downloads
13
Comments
0

4 Embeds 438

http://codurance.com 402
http://localhost 33
https://twimg0-a.akamaihd.net 2
http://www.arolla.fr 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Software Craftsmanship - Sandro Mancuso - BCS Agile Methods SG Software Craftsmanship - Sandro Mancuso - BCS Agile Methods SG Presentation Transcript

  • 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. 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.
  • 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 became more important than technical practices
  • 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. 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.
  • The invisible threat Codequality Time per feature
  • 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:
  • 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
  • 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
  • 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
  • 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
  • What is Software Craftsmanship?Software Craftsmanship is all about putting responsibility, professionalism, pragmatism and pride back into software development
  • 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  Continuous Integration
  • Dont discuss practices, discuss value.
  • Healthy IntoleranceHow can you add more value and/or havesmaller feedback cycles when not using our practices?
  • 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)- 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
  • 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
  • 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 professional attitude.Software Craftsmanship takes technical excellence and professionalism to a whole new level.
  • London Software Craftsmanship Community - LSCC http://www.londonswcraft.com
  • Thank YouSandro Mancuso http://craftedsw.blogspot.com@sandromancuso http://www.londonswcraft.com