Product Success

Several studies indirectly claim that the success of the information system
created by the project determines the success of the project, drawing on
the IS literature (e.g., Ballantine et al., 1996; Delone & McLean, 1992,
2003; Seddon, 1997; Seddon, Staples, Patnayakuni, & Botwell, 1999).
If the major project deliverable is not also accepted and used by the
intended client/end-user and/or does not sufficiently benefit them, then
completing the main project deliverable "to scope" (specification) may not
be a legitimate or adequate measure of project success. This success
criterion may include measurements of information quality, system quality,
service quality, intention to use, actual usage, user happiness, and net
benefits in the case of information system deliverables (DeLone & McLean,
2003).
However, the same idea may be used to describe structures and other
types of civil infrastructure, such as those created through construction and
engineering projects (Baccarini, 1999). Clients and users have distinct
interests and demands from project stakeholders than the triple constraint
group. Their main focus is on functional readiness and other advantages
brought about by changes in the nature and circumstances of their
employment.
An information system may be delivered "on schedule, under budget, and
to specification" by a project, yet the system may not be used or accepted
by users. This can happen, for instance, when a system specification lacks
sufficient user input to its definition or when user requirements change as a
result of changing business conditions.