Embed Size (px)
Citation preview
Successful Enterprise Applications Projects
Golan Avraham - Tescom USAJune 22nd 2006
Hold System Integrator Accountable Through Independent Quality Assurance
A Quality Project
What is quality?
What is the cost of quality?
What is the cost of no quality?
Today, We Will Discuss…
What goes wrong with implementations and upgrades?
A solution: Align System Integrator (SI) delivery with project’s quality assurance
“Quality Gates” to Project Success Assessing Deliverables Constant Monitoring Possible Payment Structures Customer Success
Enterprise Software Projects Are Notorious
50% of all software implementation projects failed to meet requirements (Gartner)
50% of all software implementation projects exceeded their budget (Standish Group)
90% of all software implementation projects finish late(Aberdeen)
What Typically Goes Wrong?
Scope Creep
Business requirements continuously reopened
Requirements not traced through development process
Cutting testing efforts: development milestones take precedence
Unexpected performance and data issues
Defects in critical business scenarios before go-live
$$ spent on SIs without promised results
The Solution: Define Project’s Quality Gates
Determine project’s phases
Define risk based Critical Success Factors (CSFs) per phase
Define specific metrics and measurements for each CSF
Use defined metrics and measurements as go/no-go criteria to pass through each gate
The Solution: Align SI Deliverables with Quality Gates
Tie SI main deliverables to Quality Gates
Obtain agreement prior to project start
Implement on-going monitoring and control procedure
Structure payout based on passing Quality Gates
Use an Independent Validation and Verification (IV&V) 3rd party for objectivity
The Need for Independent Quality Assurance
“Whether or not a software system meets its requirements should be determined by independent agents - neither the developers, who were paid to produce the system, nor the technology vendors, who sell off-the-shelf products, have the objectivity required for impartial review.”
Harvard University - March 2004
IV&V Quality Gates
Requirements
Design
Implementation
Integration
Go-Live
Post Go-Live
Requirements Traceability
RICE Components Audit
Critical Scenarios Testing
Quality
Gate
Customer Success
Customer: Leading manufacturer of telecommunication solutions
Challenge: Customer suspected that ERP project requirements were not fully addressed by project integrator
Tescom’s Activity: Build
requirements to design traceability matrix tables
Results: Tescom found that more then 20% of project requirements were not addressed by Integrator
Requirements
Design
Implementation
Integration
Go-Live
Customer Success – Cont’d
Customer: Leading supplier of semiconductor industry products
Challenge: Customer wanted to verify that ERP critical business scenarios were successfully tested prior to go-live
Tescom’s Activity: Designed and
performed independent tests for critical business scenarios and integrated RICE elements
Results: Tescom found more then 200 serious defects in the critical scenarios, some of them found but overlooked by the integrator’s internal testing team
Requirements
Design
Implementation
Integration
Go-Live
Getting Started With This New Approach
I have a project coming up…what are the next steps?
What if I’m already in a project, and it’s over budget or behind?
How can I apply these ideas for an upgrade?
A Quality Project
What is quality?
Zero critical defects on go-live
What is the cost of quality?
15% of project cost
What is the cost of no quality?
50% development rework
