Quality On Time - A Closer Look at Team Skill Mix

Quality On Time

(Continued from previous question...)

Quality On Time - A Closer Look at Team Skill Mix

• Typical mix: 2:8:1 (2 SMEs; 8 Testers; 1 Developer/Guru)
  --Such "Stratified Teams" are most efficient - required level of abstraction is raised for the typical test writer and coding challenges are placed on developer/guru
  
• SMEs should be trained in the discipline of testing
  --Hierarchies and types of testing, Testability of requirements, what verifications constitute necessary and sufficient testing, etc.
  
• SMEs and Testers together constitute the "Test Scripters"
  --Combination of Record and Function Generator (F7) Calls to start
  
• Developers/Gurus constitute "Test Harness Support"
  --Work with scripters to write functions to streamline scripting
  --Supports/expands the framework infrastructure
  

(Continued on next question...)

Other Interview Questions

• Quality On Time - verifiable levels of test coverage
• Quality On Time - A Closer Look at Test Frameworks
• Quality On Time - Strategic Considerations
• Quality On Time - Evaluation Criteria
• Quality On Time - Typical Framework Components
• Quality On Time - Team Skill Mix
• Quality On Time - A Closer Look at Team Skill Mix
• Quality On Time - Skill Mix: Impact on Framework
• Quality On Time - Number of Supported Applications and Releases
• Quality On Time - Anatomy of a Test Case
• Quality On Time - Maturity of Applications
• Quality On Time - A Closer Look at State Navigation
• Quality On Time - Unattended Requirements
• Quality On Time - Distributed Requirements
• Quality On Time - Miscellaneous