Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
This is a debate in a lot of sites. And I am working (betwen others) trying to clarify this inside the PMI´s standards documents. You have to be carefull about what project success really is. Most of the times, meassure related to project success are wrong because it belongs to product instead of project. PMBOK is clear: "success is measured by product and project quality, timeliness, budget compliance, and degree of customer satisfaction". Customer satisfaction is addressed if you take into account to project quality.
...
2 replies by Anupam and Patrick Dicey
Oct 20, 2016 9:19 AM
Anupam
...
Thanks Sergio. Point noted.
Nov 22, 2016 11:04 AM
Patrick Dicey
...
Yup... Technical, Schedule, Cost, and Quality (includes customer satisfaction).
With that said, all of these items aren't always within PM span of control but should still be highlighted as issues where there are gaps at the end of the project from an organizational performance standpoint.
This is a debate in a lot of sites. And I am working (betwen others) trying to clarify this inside the PMI´s standards documents. You have to be carefull about what project success really is. Most of the times, meassure related to project success are wrong because it belongs to product instead of project. PMBOK is clear: "success is measured by product and project quality, timeliness, budget compliance, and degree of customer satisfaction". Customer satisfaction is addressed if you take into account to project quality.
I would define the success as the extent to which the project outcomes meet the objectives defined at the beginning of the project within the defined constraints.
It may be making a big profit for an organization and for another organization success may mean making a customer happy even if they made some monetary loss in the project. But, these have to be defined at the beginning. I think, the measurement of success should not be limited to time, cost and scope objectives.
...
3 replies by Anupam , Brenda Phillips, and Patrick Dicey
Nov 21, 2016 6:48 AM
Anupam
...
Thanks Visswanathan
Nov 22, 2016 11:06 AM
Patrick Dicey
...
Building on your example of varying cost performance objectives; these should be defined at the beginning of the project.
I may be working a warranty project that by definition will LOSE the company money. As long as the budget and these parameters are defined in the initiation/planning phases, and are met, that project could still be considered a success from a cost performance standpoint.
Oct 22, 2017 7:36 AM
Brenda Phillips
...
Agreed. Success should clearly be defined at the beginning. Specificity is important. Defining how success will be measured will avoid ambiguity.
I would define the success as the extent to which the project outcomes meet the objectives defined at the beginning of the project within the defined constraints.
It may be making a big profit for an organization and for another organization success may mean making a customer happy even if they made some monetary loss in the project. But, these have to be defined at the beginning. I think, the measurement of success should not be limited to time, cost and scope objectives.
Community Champion
