home

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.

AttachmentSize
Quantum_Mechanics_Buddhism_and_Projects_for RQNG.pdf48.82 KB

Article Sponsored By

Any two

Ginny,

thank you for your insightful comment.

I think your right, Greg's sentence was not meant to mean "ignore the third."
However, I met quite a lot of people who do - which was the trigger for the article.
And yes, I agree that quality is missing in the equation. I like Jim Highsmith's generalization of the Kaizen Triangle at the Agile09 conference (value - quality - constraints by Jim, delivery - quality - cost by Masaaki Imai (?)). Time and Budget constrain projects actually.

The point is: one should never focus only on parts of the balance. For the requirements people this actually means that Budget, Time, Scope, Value AND Quality are requirements to consider all the time. I believe we first and foremost have to make use of methods that allow us to specify value
and quality. Tom Gilb's Planguage comes to mind here, the only human-readable specification language I know of that really 'delivers' ;).

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group