Agile Engineering




          By Fadi Stephan
Software Craftsmanship
Fadi Stephan
• 15+ years of experience in software
  development
• Consultant with Excella Consulting
• Focused on Agile since 2006
   – Agile readiness & maturity assessments
   – Agile coaching & mentoring
   – Agile principles & software engineering
     training
• Founder of the DC Software Craftsmanship
  User Group
• Organizer of the DC Scrum User Group
OOPSLA 1991
             History
Towards a Software Architecture Handbook
OOPSLA 1998
       History
Software as a Studio Discipline
Craftsman
• =
History



Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
History



Software craftsmanship over CRAP!
Craftsmanship over execution
• Most software development teams execute,
  but they don’t take care
• We value execution, but we value
  craftsmanship more
Manifesto of Software 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
SCRUM
Change Risk Analyzer and Predictor
CRAP(m) = comp(m)^2 (1 - cov(m)/100)^3 + comp(m)
I pity the fool
who doesn’t write
test cases!

 Test Driven
 Development
I pity the fool
who breaks the
build!

 Continuous
 Integration
I pity the fool
who doesn’t
collaborate

 Pair
 Programming
t




QA Should          Pride
Find Nothing
http://www.meetup.com/DC-Scrum/

Agile Engineering and Software Craftsmanship

  • 1.
    Agile Engineering By Fadi Stephan Software Craftsmanship
  • 2.
    Fadi Stephan • 15+years of experience in software development • Consultant with Excella Consulting • Focused on Agile since 2006 – Agile readiness & maturity assessments – Agile coaching & mentoring – Agile principles & software engineering training • Founder of the DC Software Craftsmanship User Group • Organizer of the DC Scrum User Group
  • 3.
    OOPSLA 1991 History Towards a Software Architecture Handbook
  • 4.
    OOPSLA 1998 History Software as a Studio Discipline
  • 5.
  • 6.
    History Individuals and interactionsover processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
  • 7.
    History Software craftsmanship overCRAP! Craftsmanship over execution • Most software development teams execute, but they don’t take care • We value execution, but we value craftsmanship more
  • 8.
    Manifesto of SoftwareCraftsmanship
  • 9.
    Not only workingsoftware, 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
  • 11.
  • 17.
    Change Risk Analyzerand Predictor CRAP(m) = comp(m)^2 (1 - cov(m)/100)^3 + comp(m)
  • 19.
    I pity thefool who doesn’t write test cases! Test Driven Development
  • 20.
    I pity thefool who breaks the build! Continuous Integration
  • 21.
    I pity thefool who doesn’t collaborate Pair Programming
  • 22.
    t QA Should Pride Find Nothing
  • 23.