Saturday, March 29, 2008

Large System Integration Testing Projects - What to watch out for...

Testing was looked down (even in some corners it is still prevalent). But let me take a lead and proudly say, that after seeing the IT world from all sides - Dev,Testing,Maintenance - Product and Services as well...I feel Testing is a REAL intellectual challenge and process. It gains its enormity from the point that No other process except testing can give a solace(or sleepless nights) when it comes to credibility of a release. It also is infact one of the most THORNY activity in any software Life cycle.

Various factors make it critical - Type of bid (Fixed, T&M, Size of project,Domain etc etc)

Anyhow i thought of putting my thoughts togather on What are the key characteristics and challenges when there is a testing planned for a LARGE System Integration projects

Tighten your seat belts ...Here you go..

•Large systems integration projects usually are mission critical and have high quality goals not only in terms of providing functionality but also towards high availability, performance, resilience and robustness of the system.

•These projects span over multiple years and business dynamics tend to change during this period.

•More often than not, these are developed in multiple releases having parallel development and testing phases of overlapping releases to maintain the schedule of the project.This increases the complexity of managing large projects.

•These have very typical characteristics of having many possibilities of getting under estimated due to the uncertainties and large number of independent variables that leads to schedule slippage and effort over run.

•Generally significant number of stakeholders and big team size of large programme leads to issues related to communication and coordination.

•Typically in such projects, project team can never be sure that the functionality that is being designed is the one will be deployed finally into the production. There is high possibility of the scope creep that is initiated by the customer, from technical point of view initiated by the vendor and from risk point of view that is decided by the need of the project.

•Usually large projects executed by multiple vendors from multiple locations in different countries having diverse culture and exploit multiple technologies.

Can you collaborate more.,...

~ Manav Ahuja

No comments: