Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Project Values
This is the third and final installment in an exclusive series excerpted from the book "Project Rescue — Avoiding a Project Management Disaster" (McGraw-Hill, 2004).
Project outcome can be measured and explained by determining the value of individual business requirements to the organization or stakeholders. Value can be measured in hard terms such as impact on net revenues or reduced stock level, or softer ones such as gaining competitive advantage or a happier workforce. A value-based approach demands ruthless evaluation and prioritization of project objectives and business requirements with the clear understanding that delivering the higher priority items will have a greater weight when assigning the overall success or value of the project.
A relatively simple approach for measuring and comparing value to support a different priority for the project objectives involves a graph showing elapsed time as a function of work effort and cost for every objective in the project charter. Stakeholders can then prioritize each objective in terms of any of these parameters: value to the enterprise, delivery date, or the cost of the function.
For example, the graph might show three groupings of the objectives based on value delivered. Because the highest value objectives are included in release 1, the business may find it acceptable …
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Seriousness is the only refuge of the shallow." - Oscar Wilde |