Quantum Mechanics, Buddhism and Projects
by Rolf Goetz
Every once in a while I run into fellow requirements engineers who seem to ignore the fact that the holy project objectives trinity of Time, Budget, and Scope is all about interrelated, inseparable ideas. Why are they ignorant? After I heard about recent insights from quantum mechanics, an explaining theory formed in my head. I will add a little cognitive science and Buddhism to support my argument.
Conclusion: people might have a mental model too simple for covering the actual interrelation present.
| Attachment | Size |
|---|---|
| Quantum_Mechanics_Buddhism_and_Projects_for RQNG.pdf | 48.82 KB |
quality?
I am not sure that 'quality' constitutes a fourth constraint. Is not scope sufficiently definitive of requirements to include quality? If I need a function to do 'a' then there is no more information I need to produce 'a'. 'A' has no 'qualities' that would allow variation in delivery from requirements. A poor quality 'a' is simply not 'a'.
I also wonder if 'time' is properly a constraint, rather than a requirement. If the delivery requirement is changed (i.e. date brought forward), then the project as whole needs to be reassessed in response. A reaction to say that we'll need to either change scope (reduce) or cost (increase) is not necessarily appropriate in absence of the full requirements and project picture seen in terms of the value the project will produce.