Many software failure matters hinge on uncovering the root causes of failure. Some of the many techniques we use to assess the causes of a software project failure include:
Software Project Failure
Today, no business can compete without reliable information-technology systems.
The failure of a software project or system can cost millions of dollars in lost productivity and disrupt normal business operations, placing a company at a significant competitive disadvantage. Yet study after study tells us that a significant percentage of software projects end in failure.
The Root Causes of Software Project Failure
Software projects ending in dispute typically have three major customer complaints:
Vendor and Customer Responsibilities
Software development contracts often bind the vendor to standards of care relating to the manner in which they implement software as well as the delivered software’s fitness of purpose. Similarly, the customer often has critical duties assigned by contract and industry standards. Software project failures can be traced to failures of either party in understanding and adhering to these duties.
How We Can Help
Determining the Causes of a Software Project Failure
DisputeSoft professionals are highly experienced and credentialed in the application of applicable industry standards, and have provided clients with critical investigation, analysis and opinions related to project management and software engineering failure issues. Whether the system failure dispute arises from alleged fraud, misrepresentation, negligence, or breach of contract or warranty, we provide the expertise necessary to support or refute technical facts at issue in the case, and to arrive at the ultimate causes of a project’s demise. We have worked as software failure experts on more than 100 cases on behalf of both software vendors and their customers to provide detailed analyses of failed software projects and systems.
We have worked on more than 100 cases on behalf of both software vendors and their customers to provide detailed analyses of failed software projects and systems.
- tracing software functionality through to requirements traceability matrices (RTMs) or other technical specifications
- assessing code quality using tools such as SonarQube
- reviewing produced documents related to software engineering and project management
- manually reviewing code to examine severe or especially important defects
- assisting in the preservation of systems germane to a dispute
- standing up systems using virtual machines
- examining highly confidential systems or source code for a limited time while on-site
- interviewing fact witnesses
- assessing project delay and technical debt according to industry-standard project management formulas
- measuring percent complete according to industry-standard software engineering formulas
Counsel may also request our assistance with drafting requests for production, preparing affidavits and declarations to support motions, or preparing for deposition.
Experts on Software Project Failure
Jeff Parmet is a widely respected IT dispute resolution specialist who has served as a…
J. Todd Trivett
Todd Trivett is a recognized industry expert in Information Technology, providing consu…
Josh Siegel has substantial experience analyzing copyright, patent, and trade secret cl…
Nick Ferrara has been an integral part of more than 90 cases, spanning numerous commerc…
Tom Ashley applies his expertise in a wide range of software-related matters, including…
Allen Klein consults with software development, systems integration, IT and business pr…
Lubomyr Chabursky is a Director in DisputeSoft's IT Project Failure practice. Lubomyr h…
Anne Ackerman has extensive experience in investigating software failure matters, inclu…
Since joining DisputeSoft in 2016, T.J. Wolf has consulted for clients on a variety of…
Aparna V. Kaliappan
At DisputeSoft, Aparna assists in drafting expert, rebuttal, and investigative reports…
At DisputeSoft, Evan is a Senior Consultant responsible for analyzing source code in IP…