“You can see a lot by just looking.”
(Yogi Berra)
Organization and Management of Software Testing Teams
For the good organization of software testing process, quality assurance activities should be managed by specialists with perfect comprehension and knowledge of testing techniques.
It is necessary to use the response from analyses of dimension information to make different management decisions and to improve the quality.

Software testers and testing groups are mainly organized into such 2 models:
Horizontal Model
Such model is used in rather big companies. In this case a testing group just conducts one type of software testing for a lot of various software products. For instance, various products can have the equal system testing team.
Vertical Model
It would organize around a software product, where dedicated software testers conduct several testing assignments. For instance, one or more testing teams may conduct all the various kinds of software product testing, beginning from unit testing and ending with acceptance testing.
Staffing level may vary over time. It depends on the requirement for software testers by various projects. Thus, in the vertical model project specialists could be re-assigned to conduct various missions.
One generally accepted practice is to use developers to conduct different software testing assignments when testing stage peaks. Unfortunately, such practice may be the reason of a lot of different troubles related to cadres’ management. Carelessness in this point may lead to project delays as well. The inconsistency between people’s skills and their assignments may also cause much more software bugs passing through the testing stage to cause supplementary in-field defects.
This fact is one of the causes for people to accept the horizontal model where staffing level variations may commonly be better managed due to the various plans and requirements by various projects.
In practical situations, a combination of both models is usually used in big software companies, with low-level software testing conducted by dedicated testers, system testing shared across similar products, and common project support performed by a centralized support unit for the total company.
The common project support comprises process, technology and tool support necessary for formal development and software testing. This centralized support unit is similar to the so-called experience factory that also gathers skills, knowledge and lessons learned from development for more efficient use in future.
Quote of the Day
Our Clients:
Knowledge Center
-
QA Testing Materials
- The Basis Of Interaction Testing
- Software Testing Sub-Stages
- Finite-State Machines for Web Testing
- Software Testing With Different Types Of Checklists
- What Is Checklist-Based Testing?
- Main Software Testing Activities
- Users and Third-Party Testers In Software Projects
- Organization and Management of Software Testing Teams
- Software Test Implementation Measurements
- Why Is It Important to Have Testable Requirements?
- Test Suite Management
- Test Suite Preparation
- What Is The Difference Between Coverage-Based Testing And Usage-Based Statistical Testing
- Two Main Forms Of Stopping Software Testing
- The Meaning of Structural Testing In Software Project
- Major Activities And The Generic Testing Process
- Sub-Activities in Test Planning and Preparation
- Software Testing: Concepts, Issues And Techniques
- Human Efforts In Quality Assurance Activities. Part II
- Human Efforts In Quality Assurance Activities. Part I
- Forming a Quality Assurance Strategy
- Setting Software Quality Purposes
- What to Test and What Type of Faults Are Found?
- Verification and Conformance In Software Testing
- Validation and Failures In Software Testing
- Waterfall Process In the Quality Assurance Activities
- Operating with Pre-/Post-Release Software Bugs
- Software Bug Handling And Related Activities
- Software Bugs’ Averting Activities
- Show all
- What Is Quality In Software Engineering?
- Software Bugs In The Context of Quality Assurance
- At What Defect Level Should We Stop Software Testing?
- When Can a Specific Testing Activity be Conducted?
- When Should We Do Backup and Recovery Testing?
- What Is Documentation Testing?
- Performance Testing And Different Test Types
- Test Documents In The Software Development Lifecycle
- Quality Cost Analysis: Main types of Costs Associated with Software Products
- What Is Defect Removal Efficiency In Software Testing?
- The Severity Ratings In Software Project
- Software Projects Analysis And Design
- Definition and Meaning of Exploratory Testing
- Definition and Meaning of Configuration Management. Part II
- Definition and Meaning of Configuration Management. Part I
- Design of Applications and Regression Testing
- Test Plan Documents Used in a Project
- Main Types Of Strategies For Rolling Out To The End Users
- What Does Testing Company Need From User To Start Proper Testing?
- Start Software Testing On Early Stages. How Does This Affect Cost?
- User Acceptance Testing as One of the Main Service Models in Software Testing Company. Part II
- User Acceptance Testing as One of the Main Service Models in Software Testing Company. Part I
- 5 Types of Software Testing Teams
- Software Test Plan Process
- Incident Management in Software Testing
- The Main Goals of Software Test Plan
- Test Planning and Development Documentation
- The Theory of Software Testing. Testing the Specifications
- Test Execution Documentation
- Definition of Beta Testing
- Performance-Based Decisions: Deciding When and What to Test. Part II
- Performance-Based Decisions: Deciding When and What to Test. Part I
- Error Guessing in Software Testing
- V-MODEL Descriptions. Responsibility of QA Managers and Software Testers
- V-MODEL Descriptions. Responsibility of Developers, Project Managers and Business Analyst
- Fundamental Test Process
- The V-Model Framework
- Risk Management In Software Testing
- Oracle. Definition and Meaning
- Psychology In Software Testing
- How Much Does Quality Cost? Part II
- How Much Does Quality Cost? Part I
- Economics of Testing
- Software Bug's Life Cycle
- When Should You Test?
- Completeness of Software Testing. The Criteria for White Box. Part II
- Completeness of Software Testing. The Criteria for White Box. Part I
- Completeness of Software Testing. The Criteria for Black Box
- Completeness of Software Testing. Introduction
- Practice of Automated Functional Testing in Microsoft Visual Studio
- Estimation of Number of Errors in the Program. Mills Model. Part II
- Estimation of Number of Errors in the Program. Mills Model. Part I
- Ad Hoc and Exploratory. What is the Difference Between Theory and Practice?
- Modern Methods of SQL Injection Attacks: Identification
- Testing of Mobile Applications
- Complete Software Testing Outsourcing. Part II
- Complete Software Testing Outsourcing. Part I
- The Rapid Expansion of the Company's Resources as the Goal of Outsourcing
- Independent Quality Audit. Part III
- Independent Quality Audit. Part II
- Independent Quality Audit. Part I
- Testing of Existing Software Products
- Overview of Automated Testing Tools
- Independent Software Testing
- Necessary Tools to Test Linux
- Basics of Automated Functional Testing
- Product Life Cycle and Testing
- Models of Organization of Independent Testing
- Tools for Testing From HP
- Tools for Testing From the IBM Rational
- What Do We Need to Know to Become an Expert in Performance Testing?
- How to Сontrol Test Data
- The Basic Load Testing Tools
- The Importance of Software Testing Automation
- Selenium: Subsidiary Tools
- Attacks on Unprotected Login Forms
- 10 Usability Heuristics
- The Introduction to JMeter
- Autotests: Myths And Reality
- Evaluation of software reliability
- Developers Don’t Like Testers, Because They Don’t Know How to Use Them
- 15 Important Theses About Usability Testing
- Load Testing of the Projects
- Pylot - Tool For Load Testing of Web Applications
- Key Terms of Load Testing
- An Example of System Requirements
- Life Duration of Software Bug
- 4 Attributes of Qualitative and Well-Written Test-Case
- Superstitions in Software Testing
- Fundamentals of Mobile Application Testing
- 3 Tips to Reduce Mobile Application Testing Efforts
- Project Applications that are Easy to Test
- Software Testing Checklist – 5 Steps to Success
- Top 10 Critical Software Bugs of 2010 Year
- 3 Types of Mobile Wireless Applications
- What Is A Mobile App and Why Do I Want One?
- What is Fuzz Testing?
- Mutation Testing – Way to Verify Your QA Team
- Effective Use Case Example
- Well-Performing Application is Goal of Performance Testing
- The Parable of the Pyramids in a New Way
- Pareto Principle in Software Testing
- Who is a Good Tester?
- Has the Software Tester Right to Make Mistakes?
- 5 Tips to Get Started in Software Testing
- 3 Tools to Test UI Mockups Compliance
- 5 Simple Ways to Reproduce Not Reproducible Bug
- 4 Best Add-ons to Identify Selenium Locators
- Running Selenium Server Using Custom Firefox Profile
- 3 Goals of Usability Testing
- 3 Forms of Acceptance Testing and their Application
- Test Strategies for Smartphones and Mobile Devices
- Embedded Software Testing
- Testing Techniques for Mobile Applications
- Tutorial Database Testing using SQL
- 12 Best Cross Browser Testing Tools to Ease Your Browser Compatibility Testing Efforts
- 6 Tips to Get Started with Automated Testing
- Do I Need to Test the Automated Tests?
- Technical Terms Used in Testing World
- ISTQB Advanced Practioner Level Practice Exam 1
- Mobile Usability Testing: Problems and Solutions
- Does any one know a good open source tool for Test Management and Bug Tracking?
- Software Quality Metrics
- How to Make Adhoc Testing More Effective
- Test Plan for a Mobile Applications
- 10 reasons why you are not getting job in software testing
- Top 20 Practical Software Testing Tips
- Wasting Your Time By Not Writing Tests
- Test Checklist For Mobile Applications
- Sample Deliverables
- Software Testing Glossary


















