Skip to main content

Practical advices by Karl Wiegers

I am reading the beautiful book "More About Software Requirements: Thorny Issues and Practical Advice" by Karl E. Wiegers.

 I'd like to share with you two of the most important points of his "10 cosmic truth", 
that to me are #6 and #9.


 #6 The requirements might be vague, but the product will be specific.


 I would say this is the usual point of "Natura abhorret a vacuo", that is here... each gap n requirements will be filled by some bad feature.


 #9 The customer is not always right, but the customer always has a point.

 Never underrate your key users

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

3. Simple, Complicated, Complex... Chaos !

A few words about the different kind of systems, just so you know in which kind of trouble you are when you start gathering requirements :-) SIMPLE What it is: you can see clearly all the connections between cause and effect . How to handle it: it is usually easy. COMPLICATED What it is: there are cause - effect connections, but it's not easy to see them. There is never a unique solution. How to handle it: ask questions to the experts (if there is any). COMPLEX What it is: it is made of many pieces, and they are highly interconnected. The output is usually part of the system itself and influences it, so it's difficult even to ask yourself the right questions. How to handle it: test some small parts and see what it happens (someone calls it "dance with the system.") CHAOS What it is:  high uncertainty, no apparent cause and effect and ... when some rule seem to apply, it will probably change very rapidly. How to handle it: run away !
Post a Comment
More »

Suppliers, suppliers, suppliers

Some managers don't find the time to evaluate new suppliers, not even 10 minutes on the phone. Then they complain for weeks  that they are stuck in a project that does not take off in 2 years. Because of the supplier....
Post a Comment
More »