Project Management

Please login or join to subscribe to this thread

Has a Project failed if the benefits are not realised?

linkedin twitter facebook   Benefits Realization   Portfolio Management   Risk Management  
avatar
Gordon Alexander Senior Principal - Global Programme Director| Indepndent Chelmsford, Essex, United Kingdom
I just read an article "Disaster Recovery for Your Project" by Mark Mullaly which reminded me of an old question and many political debates with sponsors and stakeholders.

example of this: A product that was a must have for one of the sponsors did not come high enough on the priorities to be allocated a slot on the portfolio roadmap. After reviewing the priority levels for the roadmap and discussions at board level the case was resubmitted with 3 x the annual revenue over 3 years and 15% less cost, when questioned around this the statement was "we understated the original revenue forecast so that when we exceeded it, it would be deemed a bigger success". Hmmm! after more discussions the political landscape changed and we force fitted it into the roadmap but with the project budget supplying 60% of the cost and the department supplying the other 40% from within their budget.

To cut the punchline, after 18months the product had made a total profit of €96, well below the original and revised ROI targets. The Portfolio management was blamed for not delivering this earlier and they had missed the window for a successful product. The product was delivered on time and budget as per its place in the portfolio roadmap.

Whats your view: Did the project fail because the benefits were not realised?
Sort By:
< 1 2 3 >
avatar
Gordon Alexander Senior Principal - Global Programme Director| Indepndent Chelmsford, Essex, United Kingdom
May 02, 2019 4:33 PM
Replying to Wade Harshman
...
Gordon, I think I understand a distinction you're making. A project could be considered as a failure if it does not meet the goals set for it (financial, strategic, etc). However, that doesn't necessarily mean there's a failure in project / program / portfolio management. Although a PM or PMO could certainly cause a project to fail, there are factors outside the scope of project management that can keep a project from achieving its goals.

This would be a very important distinction to make in any review. It's easy and tempting to blame the PMO for project problems, but an organization needs to be very honest if they want to identify root causes and improve over time.
Hi Wade and yes, this is the dilemma in some cases, the delivery project can be very successful but the business case (in the example) was flawed. the project statistics on successful completion reflected this. 18 months on that changed when the head of sales stated it was a project failure.
avatar
Gordon Alexander Senior Principal - Global Programme Director| Indepndent Chelmsford, Essex, United Kingdom
May 02, 2019 9:59 PM
Replying to Keith Novak
...
Projects can be considered successes or failures based on the perspective of the observer.

If you are the executive who had an ulterior motive for some project, like develop skills, entry to market, or keep good staff around while we find a better project, it might be considered a success despite the stated business objectives. To come out even €96 ahead is pretty good if there was another strategic value

If you are on the team and the project fails to hit the targets, it can certainly feel like a failure, and the team can also feel like they were set up to fail from the beginning due to unrealistic expectations. This is very demotivating and a way to lose good people.

Unless the team just dropped the ball, this is an important time as a leader to recognize the team for the good work they did when put in an unfortunate situation. If you can get through a bad situation together as a team and still enjoy each other's company, then it was a success on a different level.
Thanks Keith and all relevant points.
The forecast revenue for year 1 was £2m, yr 2 was £5m in 18 months it did €96, there was no ulterior drivers the project.

The project celebrated the release and all was good until the revenue didn't build up. There was a big LL exercise and the real cause identified so in the end all was good and the project team could sleep well again.
avatar
Gordon Alexander Senior Principal - Global Programme Director| Indepndent Chelmsford, Essex, United Kingdom
May 02, 2019 9:09 PM
Replying to PRASAD Mani
...
The Project is considered as failure if it does not produce what Customer Expectations and there is no working software. Customers give the projects as they want to see ROI and provide services to their clients if that is not achieved then the Project is considered to be failure.
Thanks Prasad and I agree with the points you have put in.
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"A mind once stretched by a new idea never regains its original dimensions."

- Anonymous

ADVERTISEMENT

Sponsors