Testing in DarkAges!

As Test Practitioners, one thing that we all may agree upon is that there is no silver bullet to avoid the squeezing testing timelines when it comes to project schedule.  Scope-creep in projects is almost predestined. Let me ask you a question. As a Test Manager, how many times have you come across the situation where the Project Manager walks up to you and asks you a little favor, “can we finish testing with lesser number of resources” or “can the testing be finished a little earlier” or “I know this is kind of late, but can we include this module too”; and in most cases the first thing you say is, “let me check”.

This ‘check’ has to be quick; and it should just not be based on assumptions, rather on measured inputs. ‘Something’ has to be in place somewhere throughout the testing life cycle which allows us to quickly adapt to the changed scope without risking the quality of testing and the delivery. Risk based testing is one such ‘something’ that assists testing teams in prioritizing the test deliverables conforming to the project plans.

What I am saying here is an overview of risk based testing; proposing it as a tool to shield yourself and your teams from the ever-changing requirements, scope-creeps and last minute surprises. Since a lot has already been written about Risk Based Testing, risk definition, risk identification, risk assessment and risk mitigation process, I don't think we need to discuss it here.

All that I am mentioning here is basically a case study based on the system integration testing phases of the programme for implementing a common HR Integration System across all branches of the company using PeopleSoft. The HR system was based on customization of PeopleSoft as per the HR policies prevailing & impacting a particular branch of the company in that country. 

Considering multiple implementations with overlapping phases and more than one project plans, a risk based approach to testing was adopted. Focus was on prioritization & reusability and test artifacts were shaped considering these. 

To further buttress this approach, every module of PeopleSoft was given a priority after discussion with the respective project manager.  Once this base was prepared, timelines for testing as estimated by the Test Manager were mapped with the respective modules. As & when there was a change in project scope, minor changes in the matrices produced a new version of testing schedule, which was publicized to the whole group.

The Risk Based Testing approach proved highly beneficial to the project and testing team could successfully manage the scope changes throughout without bringing down the quality or morale of the team. Well done Team!

Interactive Web: Does it require different Test strategies?

Another discussion among the team members provoked some more thoughts about Web2.0. Rohit made a list of items of web 2.0 that may require additional testing. My point is, we may have to work altogether in a different way to make our testing effective in an environment which is very dynamic and keeps on changing. 

For example, we all visit various news sites and content has to change every few minutes or hours. Now, it demands a very efficient & effective testing. In fact, Intercative Web has brought forth a dynamic web experience to the end users.

Web end-users are impatient and they demand and have access to a web world full of options. Even the smallest failure in providing a superlative functionality, performance, security, consistency, speed and reliability to the end user may lead to undesirable revenue losses, loss of reputation and increased support costs. With the aim of offering the user a consummate web experience, extensive new testing strategies and processes need to be exercised that would accommodate the requirements of Interactive Web.

How does a TCoE help or contribute to the client organization?

Since TCoE is a group of skilled people in respective technologies, domains, Business area and carry a lot of experience collectively; they bring success to client they serve and also bring continuous improvement to their processes.

Also, a TCoE can provide all kind of testing solutions and services to the clients who may be getting services from multiple clients. Now, since only one vendor is providing all services, this also brings in more operational effectiveness and efficiency.

Further, this single group becomes responsible for the overall success of the venture and because they belong to a group, they have better coordination among them; which, eventually results in saving on time and money.

The expertise a TCoE brings along, also helps & motivates them to look for more innovative ideas to serve to all testing requirements of their customers.

There is no doubt that a Testing Center of Excellence is a focused group of skilled individuals who increase the efficiency and profitability of their parent organization and also bring multiple benefits to client organizations.

Testing CoE - 2

The attached image shows a basic overview of a Testing CoE. The Organizational structure might differ in your organization.

Testing CoE - 1

Some freshers asked me what is a Competency Center or a Center of Excellence and what it does. I can understand that for many it is still a vague term and does not make much sense except that it is group of people of similar technical competencies who meet often, prepare presentations etc. etc. Up to an extent, it is true. And in fact, I have seen different variations of CoE in different organizations I have worked with. Well, I cannot really describe all those here.

A Center of Excellence is a group of people of varied technical competencies that work as a team and towards a goal of leveraging their competencies across the organization for different engagements.  In this article, we will be focusing on Testing Center of Excellence (TCoE).