A framework that standardises test processes, and best practices, facilitates tools to ensure the optimal utilisation of testing resources. It also provides metrics and other deliverables to measure the efficiency of the current methodology.
Benefits of TCoE include
Schedule optimisation, the possibility of automating a repetitive task and the use of templates provide a reduced test execution time. Also, the implementation of standard processes reduces the idle time between common tasks and accelerates the resolution process on the most demanding ones. This can be put into practice, for example, by having the team work together to build a repository with all templates and standard processes documented. This way, every team member can work aligned with each other.
Enhance Risk and Quality management. The execution of integrated work rules could increase the quality of the product by reducing the impact of usual project risks. This is granted with an early evaluation and supported by the use of metrics that measure the efficiency of the applied methodology. With the team-created repository, there is a chance to avoid late deliveries or undetected critical bugs if there is a guideline for the team members to rely on so they can focus on the quality of the product instead.
Reduction in costs Considering that the executed processes must be goal-oriented, there is a higher opportunity for the team to develop their skills and specialise themselves according to specific objectives. In the long term, this could lead to a cost reduction due to the optimisation of tasks that are implemented by a skilled team.
Building a Testing Center of Excellence (TCOE)
Getting the stakeholder's buy-in Commitment to quality is everyone's responsibility and has to come from each stakeholder of the organisation. Stakeholders' support for quality is required, and it has to be in actions, not just words. If it is clear that a software release won't be ready for production, key leaders must have the courage to do what is right for the business and speak up.
Maintain independence QA leaders need to be an independent voice for quality within their larger IT organisations and must be able to honestly deliver bad news without being handicapped by a conflict of interest.
Understand risk-reward trade-offs. Empowered QA organisations should have a seat at the table when there are discussions regarding business and technical risk-reward trade-offs. Promising zero defects and quality without compromise is often unrealistic in most fast-paced, competitive environments.
Focus on defect prevention and early detection Early involvement of QA in the SDLC consistently proves to save $$ in the long run. Defects caught in the requirements and design phases can be hundreds of times less expensive than defects caught in production.
Review integration challenges Most testing teams to do a pretty good job of functional testing in specific areas, like web- or retail- application testing. Customer experience defects are often found where the systems integrate. Therefore, it is important to have efforts dedicated to end-to-end integration.
Initiate and automate repeatable tasks. Initiate and automate important, repeatable tasks to optimise test efforts. Automation is not just about regression testing; automation should be used for other tasks such as test data creation, test lab management tasks and reporting.
Standardise and simplify processes, tools and methods. Too many testing groups think their applications and workflows are unique and require customised processes, tools and methodologies. Standardising and simplifying testing processes, tools, and methods has a profound and immediate return on investment.
Manage by facts Standardising allows leaders to manage by facts instead of emotions or opinions, enabling informed decision-making. Having the facts available with a quality dashboard will assist the line of business owners and executive management in decision-making and reinforce the value of the QA team to the organisation.
Promote continuous improvement. It is important to continuously look for ways to improve the testing and QA process through lessons learned or root-caused analysis. Historical trends, such as release-over-release data, are invaluable in developing estimation tools and release predictive readiness models.
Build a committed, high-performing QA team. QA teams are often a blend of employees, contractors and outside partners. Make sure all involved are fully committed, high-performing and have the right attitude for success.
Comments