What kind of industries do some of your biggest clients come from?
By strategy since its inception ten years ago and based on evolving strengths, Maveric has focused on banks and other financial institutions. However, over time, we see the need, as well as leverage of our frameworks and intellectual property in other industries as well, namely government, and public utilities, health care and pharma, logistics, telecom and retail.
The need for independent testing is nearly all pervasive today, with some industries investing in the same as a reaction to big time failures of software, while others are doing so more proactively, as well as to comply with the regulatory standards of respective countries, and business environments they operate in. Monetary authorities and central banks are driving this in case of banks and financial institutions.
How long does the independent software testing process take?
A full life cycle effort could take two to three years for, say, testing in a transformation programme for a top five global bank. On the other hand, a Business-As-Usual effort could take a few weeks to some months.
Maveric employs a mix of various types of testing (functional, non functional), techniques (for test design, test execution), engagement models (time and material, outcome based) and shoring strategies (offshore, near shore, near site, on site) to successfully implement testing with our clients. Depending on the client requirements, we could also bring in solution and delivery accelerators. For example, we could be typically employing Testac, our proprietary test design framework, which could rapidly cut down on cycle times for design by five to ten times, over and above our base value proposition.
How do you evaluate the software testing needs of individual companies?
Maveric combines an approach to formally evaluating the clients testing practices, its test organisation and the ecosystem it works in, by deploying industry accepted assessment models. It also involves baseline of testing spends, as well as benchmarking vis-à-vis industry practices.
Typically, what comes out of the exercise is a list of initiatives and programmes that one could start, stop and/or continue.
Our recommendations, which are evolved through a facilitated process of Visioning, and co-creating a design for the Test Organization with the client, factors in the Application landscape, Project and Program practices, likely Engagement Model/s (end-to-end, with/without resource augmentation, and/or test delivery), Scope (number of applications and types of tests), and variables (level of customisation, stability of solution, business criticality and so on) amongst others.
How big is the team that follows through with the testing?
In our experience with clients, team sizes could be ranging from a core team of three to five testers to as many as 100 or more for peak work.
Sign up for Computerworld eNewsletters.