- list all deliverables, goals, and objectives of the project
- determine the importance rate of each one
- determine the degree of completion (success) of each one
- calculate the success rate of the project Saving Changes...
At the very begining, before the project is started, project objectives have to be defined because them will be the measurement of project success. Project objectives have to be defined from solution objectives mainly from product/service/result to be created. With that on hand you have all you need to determine project success.
1 reply by John Farlik
Jan 07, 2019 10:54 AM
As always, your thoughts are excellent. I would add that project success criteria can be either quantitative in nature (i.e. we will save $X of money, deliver X widgets) or qualitative in nature (i.e. we will serve our organization by enhancing customer experience...). I've found that the best measures of success include both elements. The benefits realization and organizational adoption goals are (often but not always) qualitative, while the cost/schedule goals are most likely quantitative. This "mixed methods" approach to success brings "richness of purpose" to the project.
Well, the success is measured against the objectives and goals established. It is important to define the parameters and techniques to use. An example could be something like: We are expected to get 1000 likes on every material promoted in the social networks. At the end of the project, you can easily check on every advertisement the number of likes received or by using a digital marketing tool. Saving Changes...
Agree with the overall feedback thus far. If the objectives and success factors are not clearly defined up front, there is no gauge or baseline from which to measure against, regardless of project or industry, be it construction, marketing, IT, etc.