ABSTRACT
Inappropriate and ill-defined software requirements Inappropriate technical designs Inappropriate engineering tools Inappropriate user documentation Poor test planning Poor technical support
One of the key findings from this research was the lack of
stakeholder communication and the need to pass on busi-
ness and technical knowledge within the project commu-
nity and wider management hierarchy. The importance of
continuous feedback to each of the participating stake-
holders cannot be stressed enough. In particular, details
of any mistakes made should be shared with the project
community. On the basis of the author’s analysis of the
post implementation audits, there appears a broad consen-
sus that mistakes are acceptable but failure is not. Failure
was considered an absolute error that could not be recov-
ered from. It was therefore concluded that success was in
fact largely dependent on creating contingency plans and
alternate approaches for projects that have a high perceived
risk coefficient.
