Did You Say What I Think You Said?
Tom's latest eBook has been released on Amazon: "The 7 Myths of IT Integrations". Tom is also a Program Director for a large Midwest corporation and has been an adjunct faculty member at Walsh College. He has managed global web initiatives, data center moves and large multi-million dollar programs.
There is one phase of any IT project that is more important than any other--more important than designing, building or even deployment. Any mistake made in this crucial area simply multiplies in dollars and effort as the project progresses. Getting the proper requirements for a project at the beginning produces a higher quality project at the end.
There is an art to gathering those requirements, however. Requirements mining involves customers, and customers don’t always know exactly what they want, or how to articulate it. Compound that with the fact that we in IT are not listening so much as we are connecting the dots to support a solution we are already thinking about for our customer. There is a simple formula to follow to insure that you are getting quality requirements for your project.
Four Types
Requirements are not always easy to spot. They all don’t wear name tags and come ready to fit neatly into a spot we are trying to fill. As we begin our requirements gathering process, you should know that there will be a lot of facts coming at you. Some are relevant, some are hints. Therefore we need a way to categorize our requirements according to some common traits. There are four types of requirements that you will typically encounter.
Functional Requirements are concrete, value-added attributes that the new product or service …
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Get your facts first, and then you can distort them as much as you please." - Mark Twain |
