Skip to main content

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.

Comments

Post a Comment

Popular posts from this blog

Why is business people so "unorganized" ?

The more I work, the more I see "strange" behaviour both on the side of our customers, both on our side and on my personal side. I will try to understand way better why we are so changing, hectic, often unpredictable in our business hours.  I guess all this could be linked to the Complex, Complicated thing...
Post a Comment
More »

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
Post a Comment
More »

0. What's the matter with requirements ?

In my experience, many problems arising from the little care in requirements gathering are mainly due to these five factors: Pre-judgments: we believe we know how to do the right thing before we even realize what we have to do, We do like to "settle" things "later", End users often do not know exactly what they want, or express themselves in their own way and often different users have conflicting requirements, The requirements now are constantly changing: as soon as we catch some, some other requirement has already changed, Often there are organizational or "political" factors involved (ie. we listen more to the requirements of a manager who will never use the system rather than the requirement of the user who will use it 10 times a day).
Post a Comment
More »