DPTASM 03: Productized Test Automation Service
What is it all about?
Why to productize a service especially in the context of test automation? Following are the factors or considerations.
1. Consistent Deliverables at Low Cost: Because of systematization, Test Automation, as a Productized Service, can immensely benefit the Product or Project Teams that use the Test Automation Service. And, it can also immensely benefit the Automation Engineering or Development Team that delivers the Test Automation Service. The Automation Engineering or Development Team can create the Test Automation Common Infrastructure (TACI) quickly, with absolutely low volume of time and resources, and with lesser number of people, in a consistent fashion.
2. Standardized Expectations: Product or Project Teams get to use the Test Automation service quickly and they exactly know what to expect. There is a close match between the Test Automation service expected and delivered.
3. Infrastructure Standardization: The more the Test Automation service is productized, the more will be the proportion of standard, shared, reusable common components; and, lesser will be the Product or Project Team specific customized nonstandard components in the Test Automation Common Infrastructure (TACI).
4. Standardized Services: With the Production Infrastructure standardized, it becomes easier and more obvious to deliver instances of service that are more standardized. However, while we follow a pattern of standardization, we are in a position to cater to special project and product specific Test Automation requirements (Service Customization) while we continue to use the standardized and centralized Service Production Mechanism (SPM) in the context of Software Test Automation.
5. Economies of Scale: “Economies of Scale” is easily achieved and that reduces the cost further. Let's take a look at what this model is not about, next. Next Page >>
Why to productize a service especially in the context of test automation? Following are the factors or considerations.
1. Consistent Deliverables at Low Cost: Because of systematization, Test Automation, as a Productized Service, can immensely benefit the Product or Project Teams that use the Test Automation Service. And, it can also immensely benefit the Automation Engineering or Development Team that delivers the Test Automation Service. The Automation Engineering or Development Team can create the Test Automation Common Infrastructure (TACI) quickly, with absolutely low volume of time and resources, and with lesser number of people, in a consistent fashion.
2. Standardized Expectations: Product or Project Teams get to use the Test Automation service quickly and they exactly know what to expect. There is a close match between the Test Automation service expected and delivered.
3. Infrastructure Standardization: The more the Test Automation service is productized, the more will be the proportion of standard, shared, reusable common components; and, lesser will be the Product or Project Team specific customized nonstandard components in the Test Automation Common Infrastructure (TACI).
4. Standardized Services: With the Production Infrastructure standardized, it becomes easier and more obvious to deliver instances of service that are more standardized. However, while we follow a pattern of standardization, we are in a position to cater to special project and product specific Test Automation requirements (Service Customization) while we continue to use the standardized and centralized Service Production Mechanism (SPM) in the context of Software Test Automation.
5. Economies of Scale: “Economies of Scale” is easily achieved and that reduces the cost further. Let's take a look at what this model is not about, next. Next Page >>
Comments
Post a Comment