Problems
• Poor requirements – if the requirements are not clear, unfinished, too common, and not testable, then there will be problems.
• Unrealistic schedule – if too much work is given in too little time, problems are inevitable.
• Inadequate testing – no one will know whether or not the program is any good until the customer complain or systems collide.
• Futurities – requests to pile on new features after development is underway; extremely common.
• Miscommunication – if developers do not know what’s needed or customer’s have wrong expectations, problems are assured.
Solutions
• Solid requirements – clear, complete, detailed, cohesive, attainable, testable requirements that are agreed to by all players.
• Realistic schedules – allow adequate time for planning, design, testing, bug fixing, re-testing, changes, and documentation; personnel should be able to complete the project without burning out.
• Adequate testing – start testing early on, re-test after fixes or changes, plan for adequate time for testing and bug-fixing.
• Stick to initial requirements as much as possible – be prepared to defend against excessive changes and additions once development has begun, and be prepared to explain consequences. If changes are necessary, they should be adequately reflected in related schedule changes.
• Communication – require walkthroughs and inspections when appropriate.
Progress Comparation with the Gantt Chart
