van Veenendaal Erik
Drs. Erik van Veenendaal, CISA is a leading international consultant and trainer, and a recognized expert in the area of software testing and requirement engineering. Erik is the (co-)author of numerous papers and a number of books on software quality and testing. He is a regular speaker, e.g., running a tutorial on test design techniques, at both national and international testing conferences and a leading international trainer in the field of software testing.
Since its foundation in 2002, Erik has been strongly involved in the International Software Testing Qualifications Board (ISTQB). From 2005 to 2009, he was the vice president of the ISTQB organization; he currently is the president for the Curaçao Testing Qualifications Board (CTQB).Erik one of the core developers of the TMap test methodology and the TMMi test improvement model, and currently the CEO of the TMMi Foundation. For his major contribution to the field of testing, Erik received the European Testing Excellence Award (2007) and the ISTQB International Testing Excellence Award (2015).
TMMi – THE WORLD STANDARD FOR TEST PROCESS IMPROVEMENT
The Test Maturity Model integration (TMMi) has a rapidly growing uptake and is now the de-facto world-wide standard for test process improvement. An overview is provided of the TMMi model and the way TMMi supports business-driven test process improvement. Besides, the latest developments around the TMMi will be discussed, e.g., TMMi & Agile and the establishment of TMMi Local Chapters. Finally, the Test Improvement Manifesto that defines guidelines on how to make test improvement successfully is presented.
Note, Poland has recently founded a TMMi Local Chapter.
Requirements Engineering for Testers
Testers use requirements as the basis of test cases, review them for testability, and often participate in general requirements reviews or inspections. Unfortunately, many testers have little knowledge or skills in requirements engineering. What level of quality and detail is realistic to expect in requirements documents? What does testability really mean? How can testers help improve requirements? These questions and more will be answered while helping the attendee to develop skills in requirements engineering. Requirements issues and solutions are illustrated with examples, and hands-on classroom exercises in finding defects and evaluating requirements are conducted. Walk through the requirements process from a tester’s viewpoint to learn what you can should contribute to requirements quality.
Requirements Engineering for Testers
Testers use requirements (user stories) as the basis of test cases, review them for testability, and often participate in general requirements reviews or inspections. Unfortunately, many testers have little knowledge or skills in requirements engineering:
- What level of quality and detail is realistic to expect in requirements documents?
- What does testability really mean?
Test Strategies, Analytical Testing and More
Software will never be defect-free. At the same time, the importance of software to the society and its complexity are growing at a high rate. Just applying traditional testing practices in many cases in not enough anymore. This keynote will discuss the various test strategies that can be applied, and how they can assist the test professional. Special focus will be given to analytical testing:
- What is analytical testing and how can it be applied in today’s challenging projects?
- How does risk-based testing relate to analytical testing?
These and many more questions will be dealt with during this keynote.
Lessons Learned – Beyond the Obvious
During this evolving presentation, Erik discusses existing testing methods and techniques. Which ones really work, and which ones provide the most valuable contribution towards project success? It does not have to be perfect, often “good enough testing” is sufficient. Five important and indispensable recommendations are presented that every (Agile) project should implement in order to be successful. This presentation is based on many practical experiences in various domains.
Risk-Based Testing - also for Agile Projects
This workshop deals with a a real-life method (PRISMA) for applying structured risk-based testing in projects. It shows how risk identification and analysis can be carried out in close co-operation with stakeholders. It also addresses ways on how the outcome of the risk analysis can/should be used to define a differentiated risk-based test approach. The method has been developed in practice and has been tuned through many test projects in various domains. Practical experiences are discussed, together with problems encountered and results achieved. The focus will also be on how to apply risk-based testing in an Agile environment. The specific derivate from PRISMA for Agile, called Risk-Poker is presented as a practical, easily applicable method for risk-based testing in Agile projects.