About ten per­cent of all resources will be nec­es­sary to com­plete this phase, another ten to fif­teen per­cent to com­plete all the work flow­ing from the con­cept design.

In life there are a lot of things you won’t be able to con­trol, tak­ing action to be pre­pared for prob­lems com­ing your way is some­thing you CAN con­trol, cer­tainly dur­ing soft­ware projects.

You don’t judge a char­ac­ter by his words but by his actions.

For me work­ing with­out a scope is clos­ing your eyes to real­ity and offer­ing a weak prayer hop­ing every­thing will go as you would like it to be.

I have no expe­ri­ence with projects who faired well with­out a scope, I have painful ones where a scope was absent with dis­as­trous results.

The heavy load of respon­si­bil­ity. Even when com­mon sense dic­tates that EVERYBODY makes mis­takes it’s never fun if it applies to you.

There’s a word for peo­ple who will bring flip-flops to the Alps want­ing to ski. the same word applies to peo­ple start­ing a project with­out any sense what to do or any knowl­edge about project phases.

Metaphor­i­cally speak­ing, some peo­ple have design pho­bia, don’t make them throw up. Don’t make designs peo­ple don’t want or can’t use dur­ing their work. Do what works.

How can you be frus­trated about some­thing you have the abil­ity to act upon to alter its course?