Please login or join to subscribe to this thread
If anything can go wrong, it will.
Nothing is as easy as it looks.
Everything takes longer than you think.
If you perceive that there are four possible ways in which a procedure can go wrong, and circumvent these, then a fifth way will promptly develop.
Whenever you set out to do something, something else must be done first.
Every solution breeds new problems.
Nature always sides with the hidden flaw.
Murphy's Law in Project Management
Murphy's Law mentions "What can go wrong will go wrong".
If the project has started without a proper project plan, it is going to be failed.
If the project sponsor is half hearted with the project, the chance of project success is low.
If the project manager lacks the competencies, the whole project team suffers.
We have to ensure right from the beginning, the project is a right project and we should execute it in the right way. Thus, ensuring the product or service makes business sense and with the strong management support are critical. Next is to have a competent project manager with the right project management methods to deliver the project.
Entire Comment taken from Murphy's Law in Project Management - ResearchGate. Available from: https://www.researchgate.net/post/Murphys_...ject_Management [accessed Jul 28, 2016].
Professionally, I see lot of challenges when talking about opportunities and growth. Sometimes it's the management decision, and sometimes org changes & realignments.
Murphy's Law is practically proved - "If anything can go wrong, it will". :)
I think that is why there seems to be such a large push of going toward Agile. In traditional project management a lot of change is seemed as bad. In Agile, you expect change. In which case you wouldn't be waiting for Murphy's Law. One thing I've also learned over time is 'never say never'. As soon as you say "That will never happen." It will...
Some of my lessons learned:
* trust but verify
* have everything reviewed by at least one second pair of eyes
* budget for rework
* pessimistic estimates are usually not generous enough
Murphy's law can get all project down but sometime with considering project time one has to take decision which might open door for Murphy's law. And with team efforts it can be avoided also. So I think it is about just taking good solution for time being. And putting all efforts to make it worth.
I couldn't agree more. There two atittudes that have always helped me when "Murphy shows his presence": always keep updated forecasts on project path and, mainly, having an engaged team. If you work on agile projects or in a very active market, there is a great chance you'll have demands not foreseen, in these moments the team engagement with the goal will help a lot.
Doesnt Murhpy's Law State" Anything that can go wrong, will go wrong? Yes, we know that is the answer. My personal experience with this is heavy risk management (not heavy handed.) Meaning that I am constantly working with my teams to have a very active Risk Management Process (identify, qualify, plan). I think in our agile teams we are heavy on Service Strategy & Design trying to create & stick with a vision as Agile doesn't mean change is automatic. My thought process is cant plan for everything but you can build solid Risk risk register or risk-adjusted backlog that will help control Murphy.
Please login or join to reply