9. • Focus on developers regularly performing testing after coding is
complete to verify that the code behaves as expected.
• Formal "QA verification" step included in the development
workflow after coding complete.
• Instigate Developer on Test (DoT) role: a developer who tests
another developers work.
• Require DoTing of an issue before its QA verification step can
be completed.
27. STAGE 1 - QA SUMMARY
• Test high risk/priority stories
• Review and provide feedback on developer testing
• Pair with developers on test objectives and test sessions
• Formal training for awareness, diligence and test session notes
• Short testing team exercises designed by QA
• Organize regular blitzes
• Create test data for use by developers
• Develop and maintain the product testing playbook
• Establish quality scorecard
29. • Focus on anticipating and correcting failures and gaps before
coding.
• Creation of upfront testing notes detailing areas and ideas
worth testing
35. • Focus on replacing post-coding testing with testing performed
concurrently with coding.
• Instigate Bug Hunter role: each day a team member is
responsible for finding new issues with the features from the
team.
• Create and maintain a Test Backlog: A live list of test ideas for a
particular feature (that grows and shrinks as we learn more).
39. STAGE 3 - QA SUMMARY
• Pair with bug hunter
• Write bug hunter guidelines
• Sub-team health checks
• Drive improvement adoption & idea sharing across teams
• Train new team members
• Manage the Product Test Backlog
