By focusing on three simple but often overlooked methods, David Petrella’s test team consistently stays on schedule and delivers the testing results his projects expect. Learn how to develop and employ Risk Assessment documents to define the scope of testing and identify areas that cannot be tested with available resources. Publish an Entrance Criteria document that defines what resources (hardware, software, data, etc.) are needed for a successful test project. Then, use the Code Freeze concept to ensure that the software is not constantly changing until the day of delivery. Take away specific examples and helpful templates based on David’s experience using these methods in numerous projects.