begins. Same for the next phase that it was to begin with whole SDLC including requirements, development, test, and defect fixes etc. Once all phases complete, a big-bang integration was to happen followed by an end-to-end Integration test by testing team followed by an end-to-end UAT. 8. Risks: If delayed for a certain period, this medium size project could be in critical path of a much larger multi-million dollar program resulting in loss of revenue and massive loss of reputation.
The Problem Statements:
1. Everything started on a positive note. However, right in the middle of phase 1 development, the development supplier discovered that there were hardware infrastructure dependencies on another supplier and that these dependencies will impact the schedule of first phase. Eventually, the first phase slipped by almost 2 months. Not only that, it had a roll-on impact on the whole schedule. 2. Impact on testing: Test execution for phase 1 delayed. The delay had a knock on effect on phase 2 test preparation. Phase 2 test execution got delayed due to additional scope and much longer preparation time. This directly impacted testing estimates, test team member count and schedule. Phase 2 resulted into a disaster due to discovery of more than 150 defects. This was obvious as the vendor was still trying to deliver on time making their development team prone to more mistakes and their testing team was not able to cope with the time pressure. Unfortunately it also impacted client testing team as they were discovering more and more defects in acceptance testing and previously fixed defects were failing in subsequent releases. Phase 3 scope increased due to multiple defect fix cycles and additional defects found in the fixed releases.
The Solution: If we had not thought of a practical approach to resolve all issues before deployment of Phase 3 release, I wouldn't have been writing this experience report today.
Context Rules: I was keen on resolving the issue. Hence, the first thing I did was to make a vendor visit offshore. The objective was not to screw them over open issues, but to see 1) Why there are so many issues and 2) If we can help resolving some of them.
Teatimewithtesters.com
July 2013|28