(Can occur at any point in the project’s life cycle)
THERE ARE ALWAYS SITUATIONS IN WHICH PROJECTS MUST BE STOPPED. BELOW ARE SEVERAL REASONS FOR STOPPING:
- Final achievement of the objectives.
- Project cannot impact on the bottom line (either make or save the firm $).
- Poor initial planning and market prognosis.
- A better alternative is found.
- A change in the company’s interest and strategy/project conflicts with corporate objectives/clash of corporate egos.
- Inability to find a qualified partner/ specialists.
- Allocated time is exceeded.
- Budgeted costs/work hours are exceeded.
- Key people leave the organizations.
- Personal whims of management.
- Problems too complex for the resources available.
- Technical risks too high.
- Project becomes incompatible with corporate strategy.
- Original project purpose changed or outlived.
- Change in customer requirements.
- Loss of project champions.
- Loss of funding – money ran out/experiencing drastic budget cuts/project is seriously under funded.
- Superior product delivered by competitor.
- Loss of design control.
- Loss of public support.
- Estimates to complete are no longer valid.
- Failure of project to achieve actual customer’s service/cost reduction at acceptable cost or if parties cannot reach agreement.
- Loss of resources (money/time/key personnel).
- When research results prove unfavorable.
- When unable to duplicate research results (after one or several attempts).
- When prototype testing fails too many times or late stage trials/prototype consistently fails to operate.
- Perceived benefits do not materialize.
- Final product/services does not work or does not work as the customer requires.
- Too few benefits remain for project to be attractive to customers.
- Systems are not compatible/don’t (haven’t and will not) integrate.
- he threat is withdrawn.
- Irreconcilable breakdown in contract negotiations.
- Users adamantly refuse to approve/use or abide by the project’s output.
- Final product/service is too complicated to use.
- Main customer is too slow to accept the changes required by the project.