A succesful approach is context driven
Polteq is frequently invited by organizations to help improve testing. Traditional triggers are solving issues like poor quality of testing, a too long time-to-market or the perception that testing is too expensive. Nowadays, application of new technologies combined with a drastic change in the way systems are being developed, tested and maintained, are the the reason to turn to Polteq for advice on test improvement. Please read below how Polteq can help you with improving your testing.
Classical test process improvement no longer fits in many cases. That’s why Polteq has developed Context Driven Test Improvement: a flexible and pragmatic approach that helps you achieve continuous test improvement in line with your context and your goals.
Context Driven Test Improvement differentiates between collecting and assembling improvement suggestions (architecture) and selecting and performing improvement actions (implementation).
Architecture: collect improvement suggestions
Together with you and your team, the objectives for test improvement are defined: What triggered the improvement initiative? What is the scope? What can and must be achieved, when and by what means? And of course, the context is crucial. Take into account the technologies that are used:
Is virtualization, web, cloud, and/or mobile applied? And have a close look at the way systems are being developed, tested and maintained: Is Agile, SCRUM, or KANBAN in use? Has DevOps, Continuous Integration and/or Delivery been implemented? What about Context Driven Testing? Or is a more traditional test approach followed?
In line with the objectives and the context, the approach is assembled from our tool box:
Polteq has developed test improvement approaches for Agile, test automation, mobile and organizations with a limited budget: TI4Automation, TI4Agile, TI4Mobile and TI4LowBudget.
Renowned (test) improvement models like TPI® (Next) and TMMi® with a pre-defined approach for assessment and implementation.
Based on the expertise of Polteq as well as your people and organization.
The assessment is performed by Polteq together with you and your people. The scope is, when necessary, broader than testing. Listening and asking questions is crucial. This results in detailed insight in the strengths of your people, their approach and the technologies they apply – the fundament for the future – and a list of improvement suggestions, including priority, impact and term.
Implementation: selecting and performing improvement actions
Applying key principles of SCRUM, LEAN and KANBAN creates a positive momentum for successful implementation. Examples are improvement in iterations, setting priorities and estimating the required effort together with the team.
The team is directly involved in translating the improvement suggestions in concrete improvement actions. This way, implementation is aligned with the context and the organization and can be performed efficiently and effectively. Successful implementation is a short-cycled process with clear steps and realistic, achievable objectives. Priority, impact and term for improvement suggestions are, when required, updated.
Implementation includes a learning curve. Gathered knowledge and experience are essential input for the next cycle of improvement actions.
Test Improvement services
An Agile environment requires a different approach than an organization with an independent testing department. Mobile testing requires different improvement tools than the improvement of test automation. Sometimes it might be even better to use the “model-less” approach; an approach without any specific tools.
The improvement architect chooses the approach that fits the context best, which is an important condition of a successful test improvement process.
Please visit the following pages for more detailed information on a specific test improvement approach or model: