COURAGEOUS SOFTWARE DEVELOPMENT

Through Craftsmanship

Courage is the ability and willingness to confront fear, pain, danger, uncertainty,

or intimidation.

-- Wikipedia

What forces (in software) require us to respond with courage?

How does lack of courage in software manifest?

Craftsmanship???

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

Software craftsmanship's not the "next big thing". It's an attempt to articulate what the

"thing" always was

-- @jasongorman

Dangers….

•  Elitism •  Cargo Cults

Developers are often frustrated saying "management wants more features, they don't

care about quality"

Martin Fowler’s Design Stamina Hypothesis

Reducing internal quality slows us down

Qualities of Software Craftsmanship

•  Place importance on skills and development

•  Focus on Quality •  Professionalism / Pride of Work /

Integrity

Techniques of Software Craftsmanship

•  Mentoring (sometimes even formalized) •  Deliberate practice - Code katas, etc. •  Pair programming, review, etc. •  Strong testing, Clean Code, TDD, and

other design/quality practices

A Source of Courage?

What courageous behaviors would you hope to see from

applying craftsmanship?

Website/Blog – AgileVelocity.com Twitter - @ericstewart and @Agile_Velocity Upcoming Training: ¨  March 26: Certified Scrum Master Workshop ¨  April 24 – Advanced Product Planning Workshop ¨  May 7 – Cucumber QuickStart Workshop ¨  May 12 – Certified Product Owner Workshop ¨  May 20 – Software Technical Practices Crash Course

Transforming Technology Organizations Copyright © 2014 Agile Velocity, LLC.  All Rights Reserved. AGILE VELOCITY PROPRIETARY

Thanks!