I find it risible that many software groups refer to themselves as “engineers” and to what they do as “engineering”, when they have no idea what “engineering” actually entails. And in particular, when they make no effort to assess and control software risks (development risks and product risks, both).

See also:

Jones, C. (1994). Assessment and Control of Software Risks. Yourdon Press.

Koen, B. V. (2003). Discussion of the Method: Conducting the Engineer’s Approach to Problem Solving. Oxford University Press.

Demarco, T. & Lister, T. R. (2003). Waltzing With Bears: Managing Risk on Software Projects. Dorset House Pub.