Yes, I understand your point.

Jeff Moden (9/8/2015)

Jeff Moden (9/8/2015)That's a large part of the problem. Poorly defined jobs and obstinacy (and a few other "anti-traits"). Add all that to some ridiculous schedule...

Jeff Moden (9/8/2015)

I'll say that a lot of developers aren't actually qualified to determine what the client's expectations are. That's why there's such a thing as "requirements" and use...

the boundaries are 'properly filled' only if the client say so.

The person in charge of deliver the software to the client can say it's finished but finally only the client...

Yes, that is a good point of view. I agree with that too. If the software has specific boundaries and those were properly filled, we can say it's done 100%

Why not? it's just a way of thinking. If the developer says, yes the software is working but..... With any "but", you can understand the software is not complete, so...

There is nothing new in scientific method, that's just some steps that need to be done to learn something. I mean that's is not a human invention, that's the result...