Information Technology Reference
In-Depth Information
scripts never ran smoothly and used to stop due to some error in the script. This led
to insufficient defect detection in the application under test. After a period of time
the customer lost confidence in the project. This also led to loss of goodwill from
the customer side.
9.3.4.2
Solution
Finally the project was handed over to another ser vice provider. They had good expe-
rience in handling such projects. They finished the project in a satisfactory manner.
This became possible because the new team employed techniques like efficient
knowledge transition, had a backup plan in place, had a good resource center
(known as center of excellence) for automation where expert automation engineers
were available, and so on.
9.3.4.3
Lesson Learned
In of shoring projects, a proper k nowledge tra nsition process shou ld be in place so t hat
all deficiencies in knowledge and understanding about the project can be addressed.
9.3.5
Business Case 5
9. 3. 5.1
Test Estimation
This project faced the problem of underestimation of project size. The project exe-
cution was based on monthly plan and estimation. Estimation was based on the test
steps in the manual test cases, which was a wrong approach. Again complexity was
derived based on the number of steps in the manual test cases. Controlling factors
were calculated based on experience of the estimator and not by statistically proved
data. After the initial estimation no effort were made to refine it. Test data creation
effort was not accounted in the estimation as well.
9.3.5.2
Issues Faced
Due to schedule underestimation, schedule overruns happened for almost all phases
of the project. Due to effort underestimation, budget overrun also happened for all
phases. This led to loss of customer goodwill.
9.3.5.3
Solution
The project was handed over to another team. This team used test point analysis for
effort and schedule estimation. The team also made sure that size of the application,
