agile day | think you don't need software craftsmanship? | sandro mancuso

Post on 20-May-2015

1.064 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

2011-11-01 | 12:10 PM - 01:00 PM | Victoria So you think you don't need craftsmanship? That it doesn't apply to your company? No time and it's just about silly exercises? Your company has no technical debt. Maybe you have a long career path ahead of you with lots of options besides management. Motivation, quality and agility are always high. If so, count yourself lucky. For everybody else: can you afford to ignore craftsmanship any more?

TRANSCRIPT

Think you don't need Software Craftsmanship?

http://www.londonswcraft.com@londonswcraft

Sandro Mancuso@sandromancuso

I'm an artist

I love my beautiful code

Customers, deadlines, adding value? You are kidding right?

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 onthe 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 ecosystem

Process and Interactions became more important than technical practices

  

Many Agile projects are now, steadily and iteratively, producing crap mediocre software.

The Agile Hangover

We want to get things done...

… but we are under pressure

The wrong notion of time

It's all about feedback!

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 onthe right, we value the items on the left more.

The invisible threat

Code quality

Time per feature

Manifesto for Software Craftsmanshipraising 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 

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 practice

Automated testing Test first Test-Driven Development Pair-programming Continuous Integration

Don't discuss practices, discuss value.

Healthy Intolerance

How can you add more value and/or have smaller feedback cycles when not using our

practices?

Mastering the practices is hard …

… and that's 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

The attitude towards legacy code

Why do 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 developersIt's about leading by example and showing how we can

be better

… about beautiful codeIt's 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 you

@sandromancuso

http://craftedsw.blogspot.com

http://www.londonswcraft.com

top related