<< 1 >>
Rating: 
Summary: Wery useful method to rely on
Review: As a senior test engineer consultant I was asked to do a investigation on how we had worked in the test team in a project, and provide feedback to the QA organization. I was using this method and found it wery helpful! This book, unlike most other books with this subject, goes straight to the problem and and is not focused on the number of pages...
Rating: 
Summary: A practical way to reach CMM level 3
Review: If your job is to manage the test process in your company or in a project this book will be very helpful. There are many questions in the book, which helps to find out the level of the test process in your company. You find practical hints what to do to improve your test process. These hints are not of that kind: "Use test method xy or buy test tool ABC". The hints are concrete and helpful descriptions what to do. The TPI model is especially developed for improving the test process. It supports the definition of small, controlled and practical improvement steps, based on priorities. The TPI model is independent of other Software Process Improvement models and can be used regardless of the fact whether an organisation tries to improve the total software process or just the test process. If you try to use the CMM Model to improve your test process you will soon discover that it does not offer much help. It contains too little detailed insight and it is difficult to define a gradual improvement path for the test process. The TPI model offers the necessary details and can be very helpful to reach CMM level 3 regarding testing activities.
Rating:
Summary: TPI - a useful tool for test process improvement
Review: In the book Test process Improvement we found a tool to help us finding the answers to the following questions:How should we start working with test process improvement? Where in the organization do we have the "best" test process? How do we measure the current status, and what areas are the most important to improve first? We have made our first internal status evaluation, and are implementing new procedures over the summer. The book is a helpful tool giving useful tips and answers to questions of various kinds.
Rating: 
Summary: TPI falls short of giving real world answers
Review: The book Test Process Improvement is a great disappointment to me as I expected some insights by fellow testing professionals into the complex issues involved in changing the testing habbits in organizations. Allas, it was not to be. The writers choose the easy way and have come up with standard answers. Almost as if one can change an organization by simply following a checklist. Futhermore the book lacks any insights into what it takes to get organizations started along the path to improvement and to gain the commitment of senior management. The one positive thing about TPI is that it contains some interesting examples on the issues with which one may be faces during efforts to improve te test process. This, I'm sad to say, is not enough to provide for insightfull reading.
Rating:
Summary: For mature, stable test organizations
Review: This book provides a coherent process improvement approach for software testing. It provides a model that supports the assessment of strengths and weaknesses of an existing software testing process and an approach for developing and implementing remedial action to rectify the weaknesses. As such this book is not useful to organizations that have not achieved a mature and stable testing process because the model will not apply. If you are seeking a book that will get your processes stable you will find "Systematic Software Testing" by Rick D. Craig and Stefan P. Jaskiel a better place to start. However, if your processes are stable this book is among the best because it stays focused on improving the testing process and does so in the same manner that SEI's CMM does for software development. In fact, the TPI approach in this book is cross-referenced to the CMM, which gives you an approach that can be viewed as a testing maturity model that aligns nicely with the CMM (including the newer CMMI). This is one of the strong points of the book and TPI. Another thing to know about this book is that it's written more like a specification than a narrative. Some readers may find this difficult, but if you are involved in mapping the TPI key process areas to the CMM (or SPICE, Bootstrap or PSM), you'll appreciate the format. Also, the book views TPI as a subset of software process improvement, and software process improvement as a subset of TQM. While the authors focus on the software testing process, they do not isolate it from the bigger picture. This allows you to view then entire quality process as a coherent whole when you're assessing the software testing process and developing improvement strategies. I personally think this book adds considerably to the software testing body of knowledge, and that the approach the authors give is both practical and sensible. If you work in an organization that has a stable testing process or is at CMM level 2 or above this book is essential reading.
Rating:
Summary: For mature, stable test organizations
Review: This book provides a coherent process improvement approach for software testing. It provides a model that supports the assessment of strengths and weaknesses of an existing software testing process and an approach for developing and implementing remedial action to rectify the weaknesses. As such this book is not useful to organizations that have not achieved a mature and stable testing process because the model will not apply. If you are seeking a book that will get your processes stable you will find "Systematic Software Testing" by Rick D. Craig and Stefan P. Jaskiel a better place to start. However, if your processes are stable this book is among the best because it stays focused on improving the testing process and does so in the same manner that SEI's CMM does for software development. In fact, the TPI approach in this book is cross-referenced to the CMM, which gives you an approach that can be viewed as a testing maturity model that aligns nicely with the CMM (including the newer CMMI). This is one of the strong points of the book and TPI. Another thing to know about this book is that it's written more like a specification than a narrative. Some readers may find this difficult, but if you are involved in mapping the TPI key process areas to the CMM (or SPICE, Bootstrap or PSM), you'll appreciate the format. Also, the book views TPI as a subset of software process improvement, and software process improvement as a subset of TQM. While the authors focus on the software testing process, they do not isolate it from the bigger picture. This allows you to view then entire quality process as a coherent whole when you're assessing the software testing process and developing improvement strategies. I personally think this book adds considerably to the software testing body of knowledge, and that the approach the authors give is both practical and sensible. If you work in an organization that has a stable testing process or is at CMM level 2 or above this book is essential reading.
Rating:
Summary: A revolution in the world of testing
Review: With Test Process Improvement (TPI) one is able to add a new dimension to test activities. TPI makes it possible to show the environment what and how the test process works. TPI makes it possible to improve the test process in logical and clear steps. TPI gives the answers for the test process which CMM did for the software process. For me it is a revolution in software testing. With TPI, testing has become even more interesting, dynamic and mature. It is a pleasure to work with it.
<< 1 >>
| 
