Agile Engineering and Software Craftsmanship

  • 390 views
Uploaded on

Agile Engineering and Software Craftsmanship was presented at the 2012 DC Agile Engineering Conference on 12/7/2012 by Excella Agile Xpert Fadi Stephan (@FadiStephan).

Agile Engineering and Software Craftsmanship was presented at the 2012 DC Agile Engineering Conference on 12/7/2012 by Excella Agile Xpert Fadi Stephan (@FadiStephan).

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
390
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
7
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Agile Engineering By Fadi StephanSoftware 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 HistoryTowards a Software Architecture Handbook
  • 4. OOPSLA 1998 HistorySoftware as a Studio Discipline
  • 5. Craftsman• =
  • 6. HistoryIndividuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan
  • 7. HistorySoftware 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
  • 8. Manifesto of Software Craftsmanship
  • 9. Not only working software, but also well crafted softwareNot only responding to change, but also steadily adding valueNot only individuals and interactions, but also a community of professionalsNot only customer collaboration, but also productive partnerships
  • 10. SCRUM
  • 11. Change Risk Analyzer and PredictorCRAP(m) = comp(m)^2 (1 - cov(m)/100)^3 + comp(m)
  • 12. I pity the foolwho doesn’t writetest cases! Test Driven Development
  • 13. I pity the foolwho breaks thebuild! Continuous Integration
  • 14. I pity the foolwho doesn’tcollaborate Pair Programming
  • 15. tQA Should PrideFind Nothing
  • 16. http://www.meetup.com/DC-Scrum/