Reasons for Project Failure?
- Incomplete requirements
- Didn’t involve users
- Changing requirements
- Unrealistic expectations
- Poor planning
- Insufficient resources/schedule
- Lack of managerial support
- Didn’t need it any longer
What went wrong histroically?
Software quality needs to increase level of quality being deployed into production, technical team has qualified four contributing factors impacting application quality.
- Testable Requirements: Inadequate level of analysis to ensure application quality, stability, efficiency and speed. I.e. lack of quality relevance of information within Functional Spec & interface specs for downstream, lack of use cases, frequent changes in requirements even if application is in UAT phase. Resulting in i) inadequate test coverage, ii) defect slippage (SIT à UAT à Prod) & iii) Increased cost of defect fixes
- Toll Gating Mechanism: Inadequate rigor around Entry & Exit criteria’s in each phase of test such as i) Limited control over entry criteria for SIT & UAT, ii) Parallel test execution for SIT & UAT resulting in poor quality of software application & iii) Scanty quality SDM deliverables
- Communication: Lack of proper/defined communication, resulting in i) delay in start of test design activities, ii) improper test coverage due to last minute changes (which were not communicated) & iii) no time for test planning (which impacts test effort)
- Test Environment: Lack of test environment stability & test data, and ‘fit – to- purpose’ set up. Resulting in i) inadequate usage/controlled test environment (integrated with downstream), ii) incomplete test execution based on coverage defined, iii) late introduction of defects in application life cycle & iv) maximizes the opportunity of issues to be leaked to production.