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