Project plans should accurately comprehend project priorities, and these priorities should be central to any re-planning activities necessary after the project is kicked off. The most important priorities are those associated with determining project success; i.e., key product technical/quality requirements, delivery schedules, and budgets. Delineating the priorities between these key project objectives enables the appropriate trade-off decisions to be arrived at when the project plan is in need of being re-balanced due to realized issues. This scenario is most prevalent in the more complex and risky projects, and especially those where you are attempting to “do more with less.” Project managers are wise to push for priorities at the out-set of a project to avoid conflicts, potential misunderstandings and delays later on during project execution.
The objective of this series of posts is to provide insights into the breadth of Holistic Project Risk Management, especially as it relates to satisfying an organization’s objective to “Do More with Less” – which, if done well will improve the organization’s business success. The plan is to provide 2 posts per week over the course of 10 weeks. Thus, there will be time in between topics to comment and/or reach out to the author for clarification or further requests. Past posts will be assembled and stored on the Build2Scale.net website for future reference.
My text book “Project Risk Management: A Practical Implementation Approach” can be purchased via the following link: