Explanation/Reference:
Scenario 7 "Test Estimation"
Testlet 1
You have been contracted to manage the acceptance testing of a new computer-based reservation system for a travel agency. You have provided an approximate budget estimate for the testing project based on previous experience with similar sized projects. However, the management of the parent company of the travel agency will not commit to the budget until detailed cost estimates are provided.
The reservation system is being developed by a third party However, detailed specifications of the software are available, as well as an estimate of the total effort that will be spent in developing the software. The software is to be delivered in four increments, and the functionality to be delivered in each increment has already been agreed on.

Topic 4, Scenario 4, V2 "Test Management Tool"
The project situation after 11 months is:
-
The first increment was released one week late but contained sufficient functionality to be declared fit for purpose'. However, there were 20 outstanding incidents deferred to increment two.
-
The amount of voluntary overtime worked PV the test team has reduced the second Increment slippage to just 3 weeks.
-There is talk of reducing the scope of requirements. The purpose of this is to first deliver the application with support for manual testing and then to provide a delivery * weeks later to resolve any remaining points and provide support for automated testing (i.e. the link to the capture-replay tool).
-Concerns have been expressed by a section of the user community, that in some places the usability is very poor.