Project Management

Please login or join to subscribe to this thread

Project Value - Project Value Mindset Vs Theory of Constraints Mindset

linkedin twitter facebook   Agile   Change Management  
avatar
Dr. Deepa Bhide Hyderabad, Telangana, India
PMBOK 7th edition introduces "Value-based delivery" as a key concept. This places a significant importance on the broad application of ideas, routines and principles for creating value in a dynamic, complex and ever-changing project ecosystem. Needless to say, to work towards "value delivery" the project manager and team needs to have the project value mindset. This mindset describes the attitude of a project manager, which maximizes the value of a project, by making value-focused project decisions and by seeking and exploiting opportunities beyond the baseline that will lead to increased project value.

Two questions here
1. The common argument around value delivery is who and how one measures the value of the project.
2. One of the theories of project success has been to define project success as adherence to triple constraints. This, in my opinion, is also a mindset, a "theory of constraints-based" mindset. How do you navigate both these mindsets to ensure the "real" value of the project is derived?  

I would like to know your experiences.
Sort By:
< 1 2 >
avatar
Dr. Deepa Bhide Hyderabad, Telangana, India
Jun 30, 2024 1:32 PM
Replying to Keith Novak
...
Deepa,
I look at the triple constraints as essentially the business equivalent of Newton's laws of motion. There is only so much work that can be performed with a given amount of energy so how that energy is applied are the trade-offs in planning and execution.

The definition of value itself is the most important qualities of the intended outcome. In engineering, those are sometimes called the "illities" like profitability, sustainability, produceability, etc. When applying systems thinking pick perhaps 4 of the most important characteristics of your end state. Then whether it is a product or business outcome, you can compare your solution options based on whether they make each of those characteristics better or worse.

That's fundamentally how genetic algorithms work. Some thing, whether that is a molecule or a business organization can be modeled as a set of characteristics. Changing each gene will make the solution better or worse based on your desired qualities. If the change is better, than keep it and if not discard it. The algorithms then try to find the best fit through a process of optimizing the genomes to produce the solution with the highest total score based on your qualities representing value.
Keith
Keith, I so agree with you and thank you for explaining the concept. I relate this somewhere similar to healthcare domain (since I am a physician!) and also a project manager. In healthcare, while control or cure of the disease can be the ultimate "solution" of the project (patient care continuum as a project), the ultimate value to be determined is quality of life, psychological alignment etc. That's the ultimate value of the project.

Thanks so much
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Consistency is the last refuge of the unimaginative."

- Oscar Wilde

ADVERTISEMENT

Sponsors