Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
BuildingQuality InKishen SimbhoedatpandayT: KishenPandayE: kishen@eskape.nl
Defects are expensive
Examples FinancialBank: EUR 300.000 Web travel agency: EUR 200.000 80% Software Dev dollars on defects
Solving trivial bugs1.   Developer writes code and tests2.   Tester finds defect and logs3.   Developer tries to reproduce...
We let bugs happen              Requirements                        Software       Bugs                      Development  ...
   Requirements Maturity                     Three Amigo meeting                     Acceptance Driven                 ...
Where do defects comefrom?
Where do defects comefrom?                          User                       Experience       Quality                   ...
Stop the presses!Don’t make assumptions
MiscommunicationMisunderstanding
Value people and interactionover documents
Requirement maturity Testable   and estimable? User   Story short enough? UI   elements defined? Business   rules defi...
Three Amigos meetingsCreate one vision                      Developer          Tester                   Product           ...
Three Amigos meetingsDiscover unknowns What does the requirement mean? What are the special cases? How will we test thi...
Deliver value in stead of      Huh?Burning Tasks                  We’re getting                               wet…Plan   B...
Get Test Infected!
Refactor     Build test                          Test Driven                          Development         Build           ...
FunctionalTest Driven Development Refactor             Build test   Refactor             Build test   Refactor            ...
Why Functional Testing?Stable code    Desired Functionality
What is the functionality?
Testing Pyramid ROI
Agile Testing Quadrants
In Flight UI ReviewDon’t wait until the end of thesprint to get feedback
Study in Pair programming              Goal:              Build product in 45min               15   programmers          ...
Study in Pair programmingTime
Study in Pair programmingTest Cases passed
Study in Pair programmingENJOY
Study in Pair programmingLines of code
Pair programmingBad attitude       Good attitude
Quality comes from within                     Commitment       Continuous      Improvement   Quality       Responsibility ...
Working togetherExploratory Testers              Programmers   Communication                   Communication   Be curio...
What are we doing here? It’s   NOT Testing It’s   NOT Coding....
It’s Software Development
NopeBugs in productionare normalTry to minimize them ASAP
Build Quality In
Upcoming SlideShare
Loading in …5
×

Build Quality In

471 views

Published on

Published in: Education, Technology
  • Be the first to comment

Build Quality In

  1. 1. BuildingQuality InKishen SimbhoedatpandayT: KishenPandayE: kishen@eskape.nl
  2. 2. Defects are expensive
  3. 3. Examples FinancialBank: EUR 300.000 Web travel agency: EUR 200.000 80% Software Dev dollars on defects
  4. 4. Solving trivial bugs1. Developer writes code and tests2. Tester finds defect and logs3. Developer tries to reproduce4. Developer finds bug and investigates5. Team discussion about how it should work6. Developer re-codes, re-unit-tests, re-builds, re-delivers7. Tester verifies and closes ticket
  5. 5. We let bugs happen Requirements Software Bugs Development Quality Control
  6. 6.  Requirements Maturity  Three Amigo meeting  Acceptance Driven DevelopmentWe need change!  In Flight UI Review  Pair Programming  Quality Without compromise  Constant Feedback  Deliver Value
  7. 7. Where do defects comefrom?
  8. 8. Where do defects comefrom? User Experience Quality Requirements Control Software development Deliver the right code / functionality from the start
  9. 9. Stop the presses!Don’t make assumptions
  10. 10. MiscommunicationMisunderstanding
  11. 11. Value people and interactionover documents
  12. 12. Requirement maturity Testable and estimable? User Story short enough? UI elements defined? Business rules defined? Customer acceptance Tests defined?
  13. 13. Three Amigos meetingsCreate one vision Developer Tester Product Owner One Vision
  14. 14. Three Amigos meetingsDiscover unknowns What does the requirement mean? What are the special cases? How will we test this? What about the non-functions? What to do with errors?
  15. 15. Deliver value in stead of Huh?Burning Tasks We’re getting wet…Plan Build Test Review Deploy
  16. 16. Get Test Infected!
  17. 17. Refactor Build test Test Driven Development Build Quality comes first feature
  18. 18. FunctionalTest Driven Development Refactor Build test Refactor Build test Refactor Build test Build Build Build feature feature feature
  19. 19. Why Functional Testing?Stable code Desired Functionality
  20. 20. What is the functionality?
  21. 21. Testing Pyramid ROI
  22. 22. Agile Testing Quadrants
  23. 23. In Flight UI ReviewDon’t wait until the end of thesprint to get feedback
  24. 24. Study in Pair programming Goal: Build product in 45min  15 programmers 5 working alone  10 in 5 (swapping) pairs
  25. 25. Study in Pair programmingTime
  26. 26. Study in Pair programmingTest Cases passed
  27. 27. Study in Pair programmingENJOY
  28. 28. Study in Pair programmingLines of code
  29. 29. Pair programmingBad attitude Good attitude
  30. 30. Quality comes from within Commitment Continuous Improvement Quality Responsibility Confidence
  31. 31. Working togetherExploratory Testers Programmers Communication  Communication Be curious about how stuff is tested by Programmers  Ask Testers for help Partner with Programmers  Show Testers what’s build / tested Coach Test Awareness / Test infection  Help out with Automation
  32. 32. What are we doing here? It’s NOT Testing It’s NOT Coding....
  33. 33. It’s Software Development
  34. 34. NopeBugs in productionare normalTry to minimize them ASAP

×