Test improvement with consideration for the environment
Polteq gets requests from many organizations to help improve their testing. Traditionally, the reason is to resolve bottlenecks: the quality of testing is insufficient, the time to market is too long or people find testing too expensive. Increasingly, the application of new technologies, often combined with a drastic change in the method of development, testing, and management is reason to call on Polteq.
Classical Test Process Improvement is therefore no longer appropriate in many cases. This is why Polteq has developed Context Driven Test Improvement. This flexible and pragmatic approach ensures an improvement cycle that seamlessly matches your situation – fit for context – and your objectives – fit for purpose.
Together with the client, the purpose of test improvement is determined: What is the trigger? What is the scope? What can and will be achieved? In what time frame and by what means?
In addition, context is crucial. Consider the technology being applied: Do virtualization, cloud, web technology and mobile apply? Does it integrate with social media? But just as important is the way development, testing and management are done: Are Agile, SCRUM, or KANBAN methodologies being applied? Have DevOps, Continuous Integration and/or Delivery been implemented? Is Context Driven Testing being applied? Or will a more traditional approach be employed?
In line with the objective and context, an optimally appropriate approach is assembled from our toolbox together with the client. The approach is:
- Tailormade: specifically for Agile, test automation, mobile, and organizations with limited budgets, Polteq has developed several targeted Test Improvement (TI) approaches: TI4Agile, TI4Automation, TI4Mobile and TI4Usability
- Bound: globally recognized Test Process Improvement models with established approaches to research and implementation such as TPI® Next and TMMi®
- Unbound: the expertise and experience of the employees of both Polteq and the client
Polteq conducts the research together with you, and we look beyond testing where necessary. Listening and probing are crucial in this regard. The result is an understanding of the strengths of your people and methods of working – the foundation for the future – and an inventory of opportunities for improvement. In addition to the importance and impact, the timeframe over which improvements can be made is indicated.
Looking for improvement opportunities
Once the problem and context are clear, the testing professional identifies possible causes through consultation, interviews, observations and document review. He then makes known which improvements lead to a solution. This can be quick: the turnaround time from start to advice ranges from one day to several weeks.
Implementing improvements
Implementation begins with improvements that pay off quickly. This is followed by improvements that require a longer lead time or more effort. The test professional supervises the improvement project and coaches the people involved.
Continuous improvement
Improvements divided into small steps are easier to insert into ongoing work. Thus, the testing professional creates a flow in the organization, with ongoing improvements. In doing so, he checks whether the organization’s original goals are being met.
Eye for the environment
An Agile context requires a different approach than an organization with an independent testing department. Testing mobile requires different tools for test improvement than improving test automation. Sometimes it is even better to start a test improvement project without specific tools (model-less).
The test professional chooses an approach that is well suited to the context, which is an important prerequisite for successful test improvement.
