Test management approach  Test management approach (TMap) is a software testing approach. TMap is an approach that combines insights on how to test and what to manage, as well as techniques for the individual test consultant. The first method was created in 1995 and written by Martin Pol, Ruud Teunissen, and Erik van Veenendaal. At the end of 2006 a new version was published called "TMap Next" written by other authors (Tim Koomen, Michiel Vroon, Leo van der Aalst & Bart Broekman). The main reason for this new version was the aim to create a more process focused description of the test process and put more emphasis on the business objectives as a guidance for the testing process. TMap was created by the Dutch division of Sogeti which is part of Capgemini. Although TMap is a Dutch product by origin, accounts of the method have been published in French, German and English. There are risks involved in changes. Introducing new information systems is a major change for a lot of organizations and it is wise to manage these risks. This is called enterprise risk management. TMap Next has four pillars: test management, toolbox, structure and flexibility. The test manager can manage the process on four aspects: time, costs, risks and results. TMap provides techniques for the following:  TMap Next has phases that each test has to go through: and the two extra phases:  TMap allows for adaptation to the environment, including agile and scrum. In this phase a risk analysis of the product is carried out, and a test strategy is developed. The budget and test plans are made. Choices are made about the products to be delivered, the test infrastructure and the test organisation. The master test plan usually has to be signed off by the business (client). In the master test plan the test process controls are specified. Testing can be done at the end of the process where the end-product is tested against the requirements, or it can be done in an earlier phase, during development. During development, what can be tested are the available elements. What can be tested depends on the software testability. Testing during the development phase is the review of documentation, and the testing of small parts of the system as soon as they are ready for testing. It is partly static testing and white-box testing. Examples are: test-driven development, pair programming, code review, continuous integration and application integration. In Agile testing testing is carried out early in the process.