a). Poor requirements - if requirements are unclear, incomplete, too general, or not TESTABLE, there will be problems.
B). Unrealistic schedule - if too much work is crammed in too LITTLE time, problems are inevitable.
c). Inadequate testing - no one will KNOW whether or not the program is any good until the customer complains or systems crash.
d). Futurities - requests to pile on new features after development is underway; extremely common.
e). Miscommunication - if developers dont know whats needed or customers have erroneous EXPECTATIONS, problems are guaranteed.

a). Poor requirements - if requirements are unclear, incomplete, too general, or not testable, there will be problems.
b). Unrealistic schedule - if too much work is crammed in too little time, problems are inevitable.
c). Inadequate testing - no one will know whether or not the program is any good until the customer complains or systems crash.
d). Futurities - requests to pile on new features after development is underway; extremely common.
e). Miscommunication - if developers dont know whats needed or customers have erroneous expectations, problems are guaranteed.