© 2006 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice What is the “Big Issue”? What causes issues to slip through the testing net? - Colin Robb, HP Software (formerly Mercury)
Despite Our Best Efforts …
80% of business applications are not tested properly before being released into production Some Statistics from Gartner … 50% of deployed apps need to be rolled back to development 40% of unplanned downtime is caused by application failures, costing an average of $100k per hour for mission-critical apps
Factors Causing “Challenged Projects” 1. Lack of User Input Incomplete Requirements & Specifications Changing Requirements & Specifications Lack of Executive Support Technology Incompetence Lack of Resources Unrealistic Expectations Unclear Objectives Unrealistic Time Frames New Technology Standish Group CHAOS Report
Complexity of applications and integrations New technologies Performance test environments not available Technology Issues Matrix development difficult to Manage Resources have dual demand No alignment between silo teams Parallel Development Different priorities for different teams Lifecycle Issues Time and cost pressures lead to corner cutting People don’t know what to do and when – time is wasted No proper collaboration Efficiency Requirements are incomplete, ambiguous or non-existent Business are not involved throughout Many App Dev staff are not business aware Different views of the truth Business/IT Communications No Standards No Metrics Different terminology between teams and projects Performance testing is an afterthought Lack of Standard Processes Flat Budgets Mandatory Compliance Initiatives to be dealt with Constant environment of change Resource attrition External Issues Some More Reasons … Typical Areas of Pain
Discussion – What is the “Big Issue”? What is the factor, above all that causes issues to slip through the testing net and surface in production? I will record the ideas as we debate them, then we will vote at the end