QA Essentials: 4 Processes to Implement Right Now
Onsite QA has its benefits.
QUICK COMMUNICATION Is easier, for example.
Also, the team knows the
PRODUCT & CULTURE before they begin testing.
But implementing these
QA PROCESSES
will get your team in the loop:
SOFTWARE REQUIREMENT SPECIFICATION
• Purpose? ✓ Helps define project plan
• Purpose? ✓ Helps define project plan ✓ Foundation for test cases/user scenarios
• Purpose? ✓ Helps define project plan ✓ Foundation for test cases/user scenarios • Separated into modules for QA/Dev
COMMUNICATION STRATEGY
• Stakeholder kick-off: ✓ Define full scope of project
• Stakeholder kick-off: ✓ Define full scope of project ✓ Ensure no deviation from requirements
DAILY STANDUP MEETINGS
• Dual purpose: ✓ Update stakeholders
• Dual purpose: ✓ Update stakeholders ✓ Update engineers
• Dual purpose: ✓ Update stakeholders ✓ Update engineers • Plan ahead: ✓ What’s working
• Dual purpose: ✓ Update stakeholders ✓ Update engineers • Plan ahead: ✓ What’s working ✓ What isn’t
SCRUM MEETINGS
• Led by Scrum Master
• Led by Scrum Master • Purpose: ✓ Monitor engineer contributions
• Led by Scrum Master • Purpose: ✓ Monitor engineer contributions ✓ Identify team issues
LEARN MORE ABOUT
EFFECTIVE QA PROCESSES READ THE COMPLETE BLOG POST: THE 1st QA PROCESSES TO IMPLEMENT WITH YOUR SOFTWARE TESTING COMPANY QUESTIONS ABOUT QA PROCESSES? VISIT US AT QASOURCE.COM