Downloaded 22 times
Uploaded byKishen Simbhoedatpanday
Build Quality In
The document discusses ways to build quality into software development through practices like requirements maturity, three amigos meetings, test-driven development, and pair programming. It notes that defects are expensive and that many bugs come from miscommunication or misunderstanding of requirements. The document advocates for continual feedback, quality without compromise, and delivering value over tasks. It promotes collaboration between developers, testers, and product owners from the start of a project to develop a shared understanding and prevent defects.
More Related Content
Build Quality In
- 1. Building Quality In Kishen Simbhoedatpanday T:KishenPanday E: kishen@eskape.nl
- 2.
- 3. Examples FinancialBank: EUR300.000 Web travel agency: EUR 200.000 80% Software Dev dollars on defects
- 5. Solving trivial bugs 1. Developer writes code and tests 2. Tester finds defect and logs 3. Developer tries to reproduce 4. Developer finds bug and investigates 5. Team discussion about how it should work 6. Developer re-codes, re-unit-tests, re-builds, re-delivers 7. Tester verifies and closes ticket
- 6. We let bugshappen Requirements Software Bugs Development Quality Control
- 7. Requirements Maturity Three Amigo meeting Acceptance Driven Development We need change! In Flight UI Review Pair Programming Quality Without compromise Constant Feedback Deliver Value
- 8. Where do defectscome from?
- 9. Where do defectscome from? User Experience Quality Requirements Control Software development Deliver the right code / functionality from the start
- 10. Stop the presses! Don’tmake assumptions
- 11.
- 12. Value people andinteraction over documents
- 13. Requirement maturity Testable and estimable? User Story short enough? UI elements defined? Business rules defined? Customer acceptance Tests defined?
- 14. Three Amigos meetings Createone vision Developer Tester Product Owner One Vision
- 15. Three Amigos meetings Discoverunknowns 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?
- 16. Deliver value instead of Huh? Burning Tasks We’re getting wet… Plan Build Test Review Deploy
- 17.
- 18. Refactor Build test Test Driven Development Build Quality comes first feature
- 19. Functional Test Driven Development Refactor Build test Refactor Build test Refactor Build test Build Build Build feature feature feature
- 20. Why Functional Testing? Stablecode Desired Functionality
- 21. What is thefunctionality?
- 22.
- 23.
- 24. In Flight UIReview Don’t wait until the end of the sprint to get feedback
- 25. Study in Pairprogramming Goal: Build product in 45min 15 programmers 5 working alone 10 in 5 (swapping) pairs
- 26. Study in Pairprogramming Time
- 27. Study in Pairprogramming Test Cases passed
- 28. Study in Pairprogramming ENJOY
- 29. Study in Pairprogramming Lines of code
- 30. Pair programming Bad attitude Good attitude
- 31. Quality comes fromwithin Commitment Continuous Improvement Quality Responsibility Confidence
- 32. Working together Exploratory 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
- 33. What are wedoing here? It’s NOT Testing It’s NOT Coding ....
- 34.
- 35. Nope Bugs in production arenormal Try to minimize them ASAP