Deliver Fast, Break Nothing Via Effective Building Developer and Tester Collaboration - Hoang Lien Son
8 likes•3,653 views
The document discusses problems with developer and tester collaboration such as trade-offs between speed, scope and quality. It proposes solutions like testers providing checklists to guide developers and collaborating more closely throughout the development process. Some obstacles to effective collaboration are changing mindsets, building trust between roles, and lack of shared understanding around quality responsibility. With improved collaboration over time through checklists and other means, teams can deliver high quality software faster.
Deliver Fast, Break Nothing Via Effective Building Developer and Tester Collaboration - Hoang Lien Son
- 1. 1 VIA BUILDING EFFECTIVE DEVELOPER & TESTER COLLABORATION HOÀNG LIÊN SƠN TESTING VN Co., ltd DELIVER FAST, BREAK NOTHING
- 2. Today’s Topics • Problems – Trade-off – Misunderstand about Quality Responsibility • Solutions – Developer and Tester Collaboration • Obstacles – Changing Mindset – Building Trust 2
- 3. 3 DELIVER FAST, BREAK NOTHING Trade-off
- 5. Testing Development / Bugfix Trade-off - Agile 5 Release Time
- 6. Development Bugfix Trade-off - Agile 6 Testing Release Time
- 7. Avoiding the trade-off 7 Why the team can’t recognize problems sooner? Build it incorrectly test it fix it
- 8. 8 DELIVER FAST, BREAK NOTHING Misunderstanding about Quality Responsibility
- 9. 9
- 11. How to solve these problems? 11
- 12. 12 DELIVER FAST, BREAK NOTHING Developer and Tester Collaboration
- 13. Testers Provide Checklist 13 Situation What we do - Developers are unclear what needs to do to have better quality - Testers doesn’t have the trust of developers yet - Testers provide a checklist for DEV - Testers and managers need to send a clear message that: Complete the checklist is a critical task of DEV.
- 14. Testers advise DEV on Creating Checklist 14 Situation What we do - Developers familiar with checklist - Developers and testers understand DEV’s habits and common mistakes - Dev creates checklist - Testers guides/supervises to produce checklist - Manager and team leads support to provide sufficient time for developers to be able to learn
- 15. Improve Checklist 15 Situation What we do - Developers know what is a standard checklist, and how to apply it on implementation - Developers has a sense of quality responsibility - Start adding more edge cases we found during requirement analysis. The sooner developers know it the better quality we got - Testers show developers how we explore the requirement - Knowing the fact that now developers can cover most of basic cases.
- 16. Sharing Technical Risks in Checklist 16 Situation What we do - Developers and Testers trust to each other - Developers and Testers start discussing the requirements and technical - Testers know internal logic, and technical of implementation - Testers and developers sit together, Testers give risks base on the implementation solution that DEV shared - Checklist now become a document which needs to update frequently - The checklist is updated when DEV change the solution or Testers revise new issue/theory
- 17. End of Story 17 - Testers understand deeply about product, that will keep them on tinkering and imrpove their skill greatly - Dev can built a product which have high quality right from the start - We can ship product faster and more quality
- 18. Week in the Life of a Tester 18 40% 35% 25% For Customers For Teams For Tetsters
- 19. 19 DELIVER FAST, BREAK NOTHING Obstacles
- 20. Obstacle 1 – Mindset & Expectations 20 Management Customers DevelopersTesters
- 21. Obstacle 2 – Communication 21
- 22. Obstacle 3 – Building trust 22
- 23. Atlassian Result Timeline 23 100% 30% 15% 7% 4% 0% 20% 40% 60% 80% 100% 2009 2011 2013 2014 2015 Story Rejection Rate Source: Atlassian It takes significant time and effort to achieve this result
- 24. Takeaways 24 Software quality comes from implementation, not testing Developers and Tester united we stand, divided we fall It takes time and effort to achieve this result
- 25. © 2016 HCMC Software Testing Club Q&A
- 26. References 26 – https://atlassian.com – http://opensecurityarchitecture.org – http://syncotek.en.alibaba.com – http://tes.com – http://news.vanderbilt.edu – http://advice.milkround.com – http://customergroup.com – http://syncotek.en.alibaba.com – http://blog.smartbear.com/ – http://mystarjob.com/