40 Project Success Factors

Most projects have a million things that can go wrong.

Because a project is by definition temporary, it is inevitable that the budget and schedule factor prominently in project success.

But it is a surprisingly common scenario that project managers think the project is going great because the variables they are concerned with are on track (usually the deadlines and budgets) while being oblivious to an unhappy client or project sponsor that is focusing on other variables (usually stakeholder satisfaction).

The project management plan should define project success. It does this by identifying what the project success factors are.

Here is an example from a project management plan:

Knowing and defining your critical success factors can be the secret to ensuring the project finishes as a success. Of course there are always obvious ones that require no explanation (like staying under budget and schedule), but I see very few projects where there are no other success factors than the primary ones.  There are almost always success factors that fly under the radar, like stakeholder issues, occurrence of certain potential risks, and acceptance of certain interim deliverables.

For this reason we have prepared a checklist of potential project success factors.  Next time you are preparing your project management plan and come to the section on project success factors, run down this checklist to make sure you have it all covered.

1. Under budget
2. Ahead of schedule
3. Minimal change orders
4. Project achieves award
5. Stakeholders satisfied
6. Stakeholder’s financial performance met
7. Stakeholder timelines met
8. Stakeholder communications sufficient
9. Stakeholder communications on time
10. Stakeholder approvals given
11. Scope does not change
12. Deliverables are accepted
13. Deliverables are delivered on time
14. Quality of deliverables is acceptable
15. Quality standards are met
16. Product meets minimum performance or specification level
17. Quality control does not uncover quality problems
18. End user adopts the product
19. End user feedback meets a certain threshold
20. Schedule changes accepted by project sponsor
21. Schedule changes accepted by stakeholder(s)
22. Budget changes accepted by project sponsor
23. Budget changes accepted by stakeholder(s)
24. Project avoided unnecessary disruption to the business
25. Project avoided unwanted changes to the corporate culture
26. Project team works well together
27. Project team leaves the project better than they started it
28. Project team is motivated
29. Project team members are satisfied
30. Project team achieves financial reward, bonus, etc.
31. Project team member achieves award
32. Vendors are under budget
33. Vendors deliver on time
34. Vendors achieve quality target
35. Vendors maintain relationship with stakeholder(s)
36. Vendors achieve repeat business
37. Certain major risks do not materialize
38. Certain major risks are successfully mitigated
39. Certain major risks are successfully transferred to a third party (warranties, etc.)
40. Certain major risks occur but are well managed

Now you have no excuse not to have a successful project!