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

Comments

Popular posts from this blog

Crash course - 2

Why ? The more I think about it, the more "why" is the word when it comes to requirements gathering. The question "Why ?" has two different meanings: THE PAST : you ask questions to understand the cause, what has happened in the past. THE FUTURE : we ask questions to understand what the user will need in the future, what he wants to do.

Airlines and Software

This might be a little off topic, but after reading this article from USA Today , I thought the software industry should be inspired by the airline security system. As far as I know, the reason why air flight is the safest way of traveling is much due to these aspects. One, all the parts involved work toward ZERO fatalities . Two, their effort is never "good enough" . Three, they have a very open mind, sharing all the information about problems and crashes (the system was born when planes were "constantly" crashing so the pilots were very interested in sharing their experiences !) Four, unfortunately aircafts can't really pull over to change a flat tyre or stop to check their engine along the road ! Airplane manufacturers are therefore forced to build better, safer airplanes with improved safety and performance. Maintenance technicians are also forced to improve procedures to enhance reliability and safety and I think that regulators contribute wi...