Uploaded bySoftware Guru
Forget about Agile
The document discusses the importance of Agile methodologies in software development, emphasizing values such as individuals and interactions, responding to change, and customer collaboration. It highlights the need for high-quality engineering practices, rigorous testing, and continuous feedback to build maintainable and extensible products. The author, Gino Marckx, encourages professionals to excel in software engineering and craftsmanship beyond just following Agile principles.
More Related Content
![QA Best Practices in Digital Marketing [whitepaper]](https://cdn.slidesharecdn.com/ss_thumbnails/qabestpracticeswhitepaper-140307194140-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
Forget about Agile
- 1. 1 FORGET ABOUT AGILE GINOMARCKX DIRECTOR, AGILE COMPETENCY CENTER OCTOBER 21, 2015
- 2. 2 Director, Agile Competency Center 20002005 2010 Software Engineer Agile GINO MARCKX
- 3. 3 INDUSTRY SOLUTIONS MEDIA &ENTERTAINMENT FINANCIAL SERVICES LIFE SCIENCES ENERGY RETAIL & DISTRIBUTION TRAVEL & HOSPITALITY SOFTWARE & HI-TECH HEALTHCARE PRODUCT DEVELOPMENT MINDSET
- 4. 4 INDUSTRY SOLUTIONS MEDIA &ENTERTAINMENT FINANCIAL SERVICES LIFE SCIENCES ENERGY RETAIL & DISTRIBUTION TRAVEL & HOSPITALITY SOFTWARE & HI-TECH HEALTHCARE BUSINESS PRACTICES DIGITAL ENGAGEMENT CORE PRODUCT ENGINEERING INTELLIGENT ENTERPRISE ADVANCED TECHNOLOGY PRODUCT DEVELOPMENT MINDSET CORE PRODUCT ENGINEERING
- 5. 5 BELARUS RUSSIA HUNGARY UKRAINE USA, CANADA, MEXICO POLAND 20 50 502800 780 110 125 60 800 320 20 2400 670 30 900 210 60 420 224 TECHNICAL ARCHITECTS AGILE-TRAINED RESOURCES DEVOPS-TRAINED RESOURCES 12,600+ PROFESSIONALS 7,700 PROFESSIONALS TRAINED IN AGILE 3,000 PROFESSIONALS TRAINED IN DEVOPS 4,000 PROFESSIONALS SPECIALIZED IN JAVA 500 PROFESSIONALS SPECIALIZED IN MOBILE NOT JUST A HEADCOUNT
- 6. 6 POLL I consider myselfone of • Software engineer • Architect • Tester • Business analyst • Customer • Project manager • Support engineer • Other...
- 7. 7 WHY FORGET ABOUTAGILE?
- 8. 8 We are uncoveringbetter ways of developing software by doing it and helping others do it. Through this work we have come to value: That is, while there is value in the items on the right, we value the items on the left more. Kent Beck – Mike Beedle – Arie van Bennekum – Alistair Cockburn – Ward Cunningham – Martin Fowler – James Grenning – Jim Highsmith Andrew Hunt – Ron Jeffries – Jon Kern – Brian Marick – Robert C. Martin – Steve Mellor – Ken Schwaber – Jeff Sutherland – Dave Thomas © 2001, the above authors – this declaration may be freely copied in any form, but only in its entirety through this notice. MANIFESTO FOR AGILE SOFTWARE DEVELOPMENT INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS RESPONDING TO CHANGE OVER FOLLOWING A PLAN CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION WORKING SOFTWARE OVER COMPREHENSIVE DOCUMENTATION
- 9. 9 MANIFESTO FOR AGILESOFTWARE DEVELOPMENT INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS RESPONDING TO CHANGE OVER FOLLOWING A PLAN CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION WORKING SOFTWARE OVER COMPREHENSIVE DOCUMENTATION WORKING AS A TEAM 1
- 10. 10 MANIFESTO FOR AGILESOFTWARE DEVELOPMENT INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS RESPONDING TO CHANGE OVER FOLLOWING A PLAN CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION WORKING SOFTWARE OVER COMPREHENSIVE DOCUMENTATION WORKING AS A TEAM BUILDING THE RIGHT THING 1 2
- 11. 11 MANIFESTO FOR AGILESOFTWARE DEVELOPMENT INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS RESPONDING TO CHANGE OVER FOLLOWING A PLAN CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION WORKING SOFTWARE OVER COMPREHENSIVE DOCUMENTATION WORKING AS A TEAM BUILDING THE RIGHT THING 1 2 BUILDING IT RIGHT 3
- 12. 12 MANIFESTO FOR AGILESOFTWARE DEVELOPMENT INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS RESPONDING TO CHANGE OVER FOLLOWING A PLAN CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION WORKING SOFTWARE OVER COMPREHENSIVE DOCUMENTATION WORKING AS A TEAM BUILDING THE RIGHT THING 1 2 CRAFTSMANSHIP OVER CRAP BUILDING IT RIGHT 3 — Robert C. Martin
- 13. 13 POLL I care mostabout one of • Working as a team • Building the right thing • Building it right
- 14. 14 BUILDING IT RIGHT Westrive to achieve the highest standards of excellence: continuously learn, develop, innovate and improve; and take pride in our engineering and accomplishments STRIVE FOR EXCELLENCE VALUE THE INDIVIDUAL ACT WITH INTEGRITY ACT AS A TEAM FOCUS ON THE CUSTOMER
- 15. 15 SO LET’S BUILDIT RIGHT!
- 16. 16 BUILDING IT RIGHT DELIVERWITH HIGH QUALITY 1 ENSURE THE PRODUCT IS MAINTAINABLE AND EXTENSIBLE 2
- 17. 17 2 1 3 LEARNING FROM THEMASTERS Quality is not negotiable Design is a series of unvalidated assumptions The biggest defect is to tolerate defects
- 18. 18 2 1 3 LEARNING FROM THEMASTERS Quality is not negotiable Design is a series of unvalidated assumptions The biggest defect is to tolerate defects — Martin Fowler
- 19. 19 QUALITY IS NOTNEGOTIABLE
- 20. 20 QUALITY IS NOTNEGOTIABLE Test
- 21. 21 QUALITY IS NOTNEGOTIABLE Test $ $
- 22. 22 Test Test Test Test QUALITY ISNOT NEGOTIABLE
- 23. 23 QUALITY IS NOTNEGOTIABLE Build Test Execution
- 24. 24 QUALITY IS NOTNEGOTIABLE Automated Build Build Test Execution Automated Test Execution
- 25. 25 Test Test Test Test QUALITY ISNOT NEGOTIABLE
- 26. 26 • Rigourous testing •Automated build • Automated test execution QUALITY IS NOT NEGOTIABLE ENGINEERING PRACTICES
- 27. 27 POLL In our project,we use any of • Automated build • Automated deploy • Continuous build/deploy • Automated tests • Automated tests on every build
- 28. 28 2 1 3 LEARNING FROM THEMASTERS Quality is not negotiable Design is a series of unvalidated assumptions The biggest defect is to tolerate defects — Alistair Cockburn
- 29. 29 DESIGN IS ASERIES OF UNVALIDATED ASSUMPTIONS ©Alistair Cockburn - http://alistair.cockburn.us/What+engineering+has+in+common+with+manufacturing+and+why+it+matters
- 30. 30 DESIGN IS ASERIES OF UNVALIDATED ASSUMPTIONS
- 31. 31 DESIGN IS ASERIES OF UNVALIDATED ASSUMPTIONS Test Spike Spike Spike
- 32. 32 DESIGN IS ASERIES OF UNVALIDATED ASSUMPTIONS Test Customer Feedback Customer Feedback Customer Feedback
- 33. 33 • Rigourous testing •Automated build • Automated test execution • Use spikes to validate technical assumptions • Use incremental delivery to get early user/customer feedback DESIGN IS A SERIES OF UNVALIDATED ASSUMPTIONS ENGINEERING PRACTICES
- 34. 34 POLL In our project,we use any of • Architectural spikes • Spikes to increase confidence in estimate • Incremental delivery, building a valuable product increment regularly • Product demonstrations to get feedback from our users/customers • A/B or variation to get feedback from the end-user
- 35. 35 2 1 3 LEARNING FROM THEMASTERS Quality is not negotiable Design is a series of unvalidated assumptions The biggest defect is to tolerate defects — Mary Poppendieck
- 36. 36 THE BIGGEST DEFECTIS TO TOLERATE DEFECTS ポカヨケ
- 37. 37 THE BIGGEST DEFECTIS TO TOLERATE DEFECTS ポカヨケ (po’ka-yo’ke)
- 38. 38 THE BIGGEST DEFECTIS TO TOLERATE DEFECTS Test Test & Customer Feedback Test & Customer Feedback Test & Customer Feedback Spike Spike Spike
- 39. 39 THE BIGGEST DEFECTIS TO TOLERATE DEFECTS
- 40. 40 THE BIGGEST DEFECTIS TO TOLERATE DEFECTS Red, Green, Refactor Red, Green, Refactor
- 41. 41 THE BIGGEST DEFECTIS TO TOLERATE DEFECTS Validate Understanding Test & Customer Feedback
- 42. 42 • Rigourous testing •Automated build • Automated test execution • Use spikes to validate technical assumptions • Use incremental delivery to get early user/customer feedback • Use test first development to prevent technical defects from being introduced • Use examples/BDD to prevent functional defects from being introduced THE BIGGEST DEFECT IS TO TOLERATE DEFECTS ENGINEERING PRACTICES
- 43. 43 POLL In our productwe use any of • Test first development • Regular planning sessions to align on the understanding of the functionality • Examples to clarify the requirements • Behaviour driven development
- 44. 44 • Rigourous testing •Automated build • Automated test execution • Use spikes to validate technical assumptions • Use incremental delivery to get early user/customer feedback • Use test first development to prevent technical defects from being introduced • Use examples/BDD to prevent functional defects from being introduced SO FAR... ENGINEERING PRACTICES
- 45. 45 THIS LOOKS FAMILIAR... ©cbby crdotx - https://www.flickr.com/photos/crdot/7321549252
- 46. 46 SO BY BUILDINGIT RIGHT...
- 47. 47 2 1 3 LEARNING FROM THEMASTERS Quality is not negotiable Design is a series of unvalidated assumptions The biggest defect is to tolerate defects
- 48. 48 Red, Green, Refactor TO ARRIVEAT THIS PROCESS Validate Understanding Test & Customer Feedback Spike
- 49. 49 TO ARRIVE ATTHIS PROCESS
- 50. 50 We are uncoveringbetter ways of developing software by doing it and helping others do it. Through this work we have come to value: That is, while there is value in the items on the right, we value the items on the left more. Kent Beck – Mike Beedle – Arie van Bennekum – Alistair Cockburn – Ward Cunningham – Martin Fowler – James Grenning – Jim Highsmith Andrew Hunt – Ron Jeffries – Jon Kern – Brian Marick – Robert C. Martin – Steve Mellor – Ken Schwaber – Jeff Sutherland – Dave Thomas © 2001, the above authors – this declaration may be freely copied in any form, but only in its entirety through this notice. MANIFESTO FOR AGILE SOFTWARE DEVELOPMENT INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS RESPONDING TO CHANGE OVER FOLLOWING A PLAN CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION WORKING SOFTWARE OVER COMPREHENSIVE DOCUMENTATION
- 51. 51 MANIFESTO FOR AGILESOFTWARE DEVELOPMENT CRAFTSMANSHIP OVER CRAP BUILDING IT RIGHT 3 better ways of developing software
- 52. 52 IF YOU ARESERIOUS ABOUT SOFTWARE ENGINEERING
- 53. 53 BEING SERIOUS ABOUTSOFTWARE ENGINEERING... Being serious about Software Craftsmanship
- 54. 54 SO FORGET ABOUTAGILE AND EXCELL AT SOFTWARE ENGINEERING
- 55. 55 THANK YOU! GINO MARCKX DIRECTOR,AGILE COMPETENCY CENTER OCTOBER 21, 2015