Home > eBusiness > QA & Testing
|
QA
|
Avail our sound QA and testing methodologies, ensure timely delivery of your products and services and have continuous improvement of your processes and systems.
Quality assurance is a much talked about but relatively less implemented term.
It is often difficult for organizations to get serious about quality assurance. Solving problems is high-visibility; preventing problems is low-visibility. Software quality problems are not as readily apparent as they are in the case of an industry with more physical products.
Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations and is maintainable. However, quality is obviously a subjective term. It will depend on who the 'customer' is and their overall influence in the scheme of things.
Tavant's initiative towards quality
Five years back, our relatively small QA team at Tavant started out with an initiative called Zero-D - a daunting task of implementing some of the best practices listed out by the industry . Their vision was "To exceed customer's expectations for product quality and performance, ensure on-time delivery of products and services to meet customer's requirements and provide continuous improvement of our processes and systems".
The QA team at Tavant initially comprised of 6 members. They identified two major parameters which would contribute to enterprise-focused testing excellence - People as well as Process and Technology. They developed an ad-hoc process from scratch which would be the best-in-class, reusable and repeatable, thereby preventing redundancy and reinventing the wheel. With baby steps they progressed from project focused testing approach - where testing teams were formed on a project by project basis, and then moved on to identify the key practices to ensure consistency and adapt the PDCA (Plan Do Check Act) methodology. The core testing team adds leading practices, tools, automation and metrics to the process. From an organizational perspective, the focus is on quality and centralized testing using leading practices. From a 6 member team, the QA team has grown to approximately 120 members. Each of the team members is highly skilled, internally and externally trained on technical and business domains.
How are our QA practices unique?
- Early detection of defects - What makes us unique is our ability to implement the QA process early in the development cycle, rather than wait for the release and then test it. This involves close coordination between the developers, QA and the business analysts - thereby eliminating any preliminary glitches in the product.
- Stabilization phase - We have developed a stabilization phase wherein the QA team works to find defects early in the cycle to stabilize the application being developed. This eliminates any glitches during the actual testing phase.
- Domain knowledge/Consulting services - Apart from this our sound domain knowledge in QA management helps us in providing consulting services by involving our Business Analysts.
- In-depth, specific training - We also provide regular training to our QA team at Tavant. We provide design trainings, database and QA-related specific training as well as unit testing training is provided to our team.
- Reusability of test cases - Our testing practices are unique because of the reusability of our test cases - we have developed generic test cases which can be reused or modified according to the requirement.
Our involvement goes beyond testing. It extends to sharing knowledge, best practices. We at Tavant believe in applying what we have learnt, which is significant because all the best practices have actually been broken down into implement able components. Considering the scale of our projects, with many modules and complex code, this seems like a huge task. But we have simplified and modulated the testing process, thereby creating a superset of test cases - generic and specific, which can be implemented as per the requirement.
We focus on process excellence and continuous improvement of existing processes. Our effort has been to use Six Sigma to achieve the level of excellence as presented by a CMM Level IV organization. Our modular approach to testing has reduced onsite QA cycle time, since a lot of redundant stages are eliminated.
We believe in ongoing improvements and training to sharpen the QA process and skill sets. Our team undergoes continuous training programs and testing techniques and methodologies.
Our QA team has completely changed the way quality has been perceived in Tavant. From a small size team to a team of around 120, we have evolved testing techniques which are unique and modular in nature. By breaking down the best practices laid down by the industry and implementing them at a modular level, we have incorporated true quality into our software development process.
|
Testing
|
At Tavant we are committed to establishing superior testing practices which ensure quality software. Few years back, we started an initiative known as Zero D - which is aimed at implementing some of the best practices listed out by the industry. From a small-size team, we have come a long way.
Our QA methodologies are holistic and fundamentally sound. We believe in early detection of defects which not only prevents stumbling blocks during the actual testing phase, but also stabilizes the application right from the start. Apart from this, our reusable test cases can be easily implemented in various environments, making testing an intensive, integrated process.
Best of all, we believe it's essential to sharpen and enhance one's skill sets to be able to deliver the best. Hence we conduct in-depth training for all our QA personnel to ensure they are abreast of all the latest trends.
Tavant has in-depth experience and understanding of the Mortgage and Warranty space - which makes us ideal partners for you because we can provide consulting services to give our testing practices an added advantage.
Read on to know more on how we can help you deliver mission-critical, quality software within stringent timelines. |
|
| |
|
|
