Test Process Improvement
A Practical Step-By-Step Guide to Structured Testing
Published:
1999
Pages:
207
Upcoming Events
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |
Jun 08 |
AI Con USA An Intelligence-Driven Future |
Sep 21 |
STARWEST Software Testing Conference in Anaheim & Online |
User Comments
I also read and used the book on several projects. Very, very helpful. The first TPI project I did, was on a project with IQUIP, where Martin Pol used to work. I've implemented it successfuly afterwards several times.
I have read the book and think that it a very constructive and practical way to improve the SW Test Process. Thoroughly recommended!
I certainly agree that both the book and the TPI model are valuable contributions. In fact, I have used both on several assessments of testing practices, both at the project level and the organization level. I have had to make only two changes to ensure that the participants in the assessments could really understand what was being asked of them and what I was recommending. Some of the language in the TPI checkpoints is somewhat convoluted and arcane and tended to confuse participants in the assessment, especially the non-testers (e.g., project managers, developers, DBAs, configuration managers). So, without compromising substance, I've simplified the wording in the checkpoints to make it more direct and active. Secondly, I found it difficult to manually keep track of and communicate the relevance of the dependencies among checkpoints and key areas. The tool on the TPI web site does not address this problem. So, with a lot of help from an Excel expert, I created a tool that uses formulas to ensure that the dependencies are respected. The results of using this variation on the TPI model have been quite astounding, especially when I've had the opportunity to perform a follow-up assessment -- quantifiable findings led to very specific, feasible, prioritized recommendations, which in turn led to equally quantifiable improvements.