Introducing the "Six IT Success Models"

On this webpage we present:

Expert Reports

Welcome to the WSRcg Learning Center for IT Excellence

Warren S. Reid, Managing Director of WSR Consulting Group, LLC, has briefly described the “IT Success Models” for you below and has attached a very special one-page graphic image, fit for hanging/framing ;-), of each model for you.

Note that it is not possible to absorb all of the thought-provoking ideas, philosophies & processes in each IT Success Model from a short paragraph and detailed (but abbreviated) graphic provided. That is why they are taught in 1-2 extended class sessions in Law School and at the University level.

However, there is still a lot to be learned from what is included on the site. From time to time, Warren will put up well-crafted slides to help unpack the wealth of material in the models.

Also, Warren will be happy to discuss and/or train you, your firm, and/or your clients & customers on any or all of the six IT Success Models on a one-on-one confidential basis for a fee.

Please contact us at 818-986-8842 or e-mail Warren directly at if you would like to know more about the models or want to book a presentation or consultation..

Back to Top

The "He Said ... She Said" Chart:
Why Systems Fail???

© 1995 - 2010 Warren S. Reid All rights reserved

click here




The “He Said … She Said” chart, originally created in 1995 Warren S. Reid, has been updated and published in several articles and peer-reviewed journals. It is taught in USC’s Graduate School of Software Engineering, and Southwestern Law School’s IT/Computer Contract class. It is a starting for the other Six Success Models.
Statements in each cell represent virtually all of the reasons why system projects fail and the claims each party makes in its lawsuits – worldwide. Most times both (all) parties contribute something to failure – BUT this chart helps sought out who made the big mistakes and decisions that put and kept the project or system on the road to failure.

See how many are true for your project. Contact us to discuss what you might do about it!

Back to Top

I. "Riskipedia 2.0:
Failure Factors That Fly Under the Radar:
Hidden, Yet Debilitating Software Project Cripplers!

© 2008 Warren S. Reid All rights reserved

click here




Today, even though many software projects and organizations follow much better standards than in the past, and do a better job estimating projects, assigning the “right” staff, performing good project management, following good SDLC methodology and mitigating/managing risks – over 2/3 of large scale systems projects still come in late, over budget, under-functioning or scrapped altogether! Why? Because once these fundamental failure factors are dealt with, other challenges and risks that were potentially always there – actually surface.

Warren has explored this phenomenon and introduces a whole new series of oftentimes hidden risks that “pull defeat out of the jaws of victory." In previous presentations exposing these hidden project cripplers, attending IT executives shook their heads and asked, “How could I have missed that?”

Back to Top

II. “Requirements Elicitation:
Why So Difficult – Still?”

© 2008 Warren S. Reid All rights reserved

click here



Requirements! If you get them wrong at the start of the project, you are in big trouble! If you try to change them too much/too often as users learn more about current and future needs (a natural phenomenon), you may get into bigger trouble!! And if you don’t catch wrong, missing, ambiguous, or misunderstood requirements until after the system is released, such mistakes can result in loss of life (of the project, the company, or users of the system), limb (of the software, a corporate division, or human injury) and livelihood (of all concerned) – i.e. really big trouble!!
Warren once again peels the layers back from the onion – but with the different “aha” emphasis and spin and perspective he oftentimes brings to problems, and will recommendation how can we all do a better job in this frequently elusive, typically frustrating, always unforgiving, commonly political, usually misunderstood, and forever people-intensive area!

Back to Top

III. “The RFP Process for Successful Software & Vendor Selection"

© Copyright 2008-2010 By Warren S. Reid. All rights reserved

click here



Simply put, an information technology request for proposal (referred to as RFP) is a formal written document inviting suppliers (e.g., systems vendors, integrators, software developers, IT consultants, etc.), to submit a proposal on a specific commodity (e.g., system, hardware, software, network, etc.) or services ( e.g., software maintenance, staff augmentation, implementation services, custom development, etc.). The RFP PROCESS is a bidding process and one of the best methods for leveraging a company's negotiating ability and purchasing power with suppliers. The RFP process brings structure, analysis and more precision to the procurement decision and, if done correctly, flushes out the risks and benefits upfront. One of its many benefits is input from a wide range of functional, performance and subject matter experts – which helps ensure that the chosen solution will suit the company's requirements. Effective RFPs typically reflect the strategy and short/long-term business objectives, providing detailed insight upon which suppliers will be able to offer a matching perspective.

Warren S. Reid, noted author, educator, management & IT consultant, and IT expert witness has created an RFP model, that takes you through the foundational steps, the preliminary selection, “best” candidate selection and the meeting of the minds processes, culminating with an IT contract(s) that allocates risks, embraces and enforces proven SCLC methodologies, and incentivizes all parties to continue to perform.

Back to Top


IV. “Developing Savvy MIS/IT Contracts that: Allocate Risks, Keep You On Target, & Help Lead to Project Success!"

© Copyright 1998 – 2008 By Warren S. Reid and Richard L. Bernacchi, Esq. All rights reserved

click here



Here, Dick Bernacchi, one of the founders of the field of Computer Law and Warren tie together there vast experience in the contracting, litigation and expert witness arenas to identify and trace approximately 200 contract clause areas (IT technical, business and legal areas) to various stages of the systems development life cycle. Warren, in turn, then cross-references each of these to the 11 top reasons disputing parties attribute as the root causes of alleged failure. why systems/software projects fail virtually anywhere in the world claims & counterclaims found in virtually every failed systems/software project dispute anywhere in the world.” (see Warren’s “He Said … She Said” model).

This was created to enable vendor, integrator, and/or customer project technology leaders, managers and subject matter experts to understand where they fit in the IT Contracting Process and to allow them to contribute valid, knowledgeable, measurable and in-depth contributions to Counsel.

Back to Top


V. “CPR (Cooperative Project Recovery):
Reviving the Drowning Large IT Project -- Version 2”.

© 2006-2008 Warren S. Reid All rights reserved

click here



Warren takes you through his 13 step CPR methodology in a plan to get a failing or runaway project back up and running- the right way!. Warning: It’s simple – but not easy!

1. Communicate honestly, “not rosier than actual”

2. Conduct a forensic review

3 . HUA!Hear it!  Understand it!  Acknowledge it! & define “success”?

4. Revise your business case & estimates;  Re-contract

5. Make a decision point: Get on! Get off! Get away! Get down!

6 . Focus on the “right stuff”; Reqm’ts Elicitation:  Why So Difficult – Still?

7. Engage the “Right” people (Outsource?)

8. Implement an early & ongoing “adoption” philosophy

9 . Implement a Software Adjudication Team (SWAT)

10 . Adopt & execute an appropriate SDLC

11. Employ proper project mgm’t processes & tools [Manage risks]

12 . Conduct reliable and necessary testing [dynamic & static]

13. Plan and execute “go-live & acceptance” processes

Then, prepare lessons learned, share them, start new projects at # 1.


Please contact us at 818-986-8842 or e-mail Warren directly at if you would like to know more about the models or want to book a presentation.

Back to Top



Model VI: Testing Wheel

Testing is the easily overlooked stepchild of the software development lifecycle. But without thorough, smart, and effective testing throughout the development process, failure of any large scale software project is almost certainly guaranteed.

With testing, quality assurance, quality control, and IV&V, taking as much as 50% of the effort to build, "enable and stable" a complex system or ERP system, it is critical to understand the nature, sequence, reliability, and completeness of testing and the system's readiness for Go-Live.

In the interest of educating customers and integrators alike, here are 33 Tenets of Testing along with a Testing Wheel which is a thoughtful test management tool and guide to help assure successful systems implementation.

© 2006-2015 Warren S. Reid All rights reserved

click here

Back to Top



Home | Founder: Warren S. Reid | Firm Introduction & Philosophy | References & Testimonials | Firm News | Credentials, Cases, Testimony | Approach to Cases & Discovery | Expert Reports | ERP Expert Witnesses | Software Expert Witnesses | Computer Expert Witnesses | Internet Expert Witnesses | IP Expert Witnesses | IT Consulting Expertise | Firm Resume | Consultant & Expert Witness Resumes | Publications | Presentations | Firm Blog | Contact Us

WSR Consulting Group LLC · Los Angeles · (818) 986-8842 · ·
Copyright © 2004, 2005, 2006 WSR Consulting Group, LLC. All rights reserved