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

"Pick Any Two"

I don't think this quote means 'ignore the other one'. In my experience, it means "If I don't have enough resources or time, and the scope is to big, pick which one has to change". In other words, to meet a deadline with the time I have, I'll have to cut scope. If I can't cut scope or miss the deadline, I'll need more resources. If I can't have more resources or cut the scope, I have to have more time. You are right, they are all interrelated and the PM has to look at all three in balance.

However, my problem with this is that 'quality' is not in the equation here. In all of these cases, if you don't pay attention to quality too, that's what is lost. I can make the deadline with the resources I have and put in a complete product (after negotiating these), but if I haven't included quality as a specific requirement, the project plan won't actually have enough resources and/or time. The analysis and testing will be the areas cut so you end up with an inferior product even though you met the deadlines & scope.

So, actually, you have to consciously balance all 4 things. The one you ignore is what will defeat your project.

Ginny

    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