Requirements, C.I.A. Style
Rob Saxon is a Project Management Professional, Certified Information Systems Auditor and a trained Six Sigma Specialist. Rob is currently developing methods to integrate project management into previously unexplored areas of business.
“Quality in a service or product is not what you put into it. It is what the client or customer gets out of it.” - Peter Drucker
We can better gather and manage requirements through the C.I.A., but I’m not talking about spies. Our C.I.A. stands for:
-
Customer or client
-
Intended usage
-
Actual functionality
These principles can also be represented by three questions:
-
Who needs the solution?
-
What is the solution supposed to do?
-
Is the solution doing what it’s supposed to do?
The answer to the first of these questions helps us to understand who our customer or client is. The answer to the second question helps us in gathering requirements, and the answer to the final question helps us in managing requirements.
Customer or Client?
I once had a manager who said, “If you are managing a project for folks internal to your organization, they are not customers. Customers have a choice in the product, and very few of these folks have a direct choice about which product to use.” Indeed, many consumers of internal projects have power of contribution, but often not the power of selection. By definition, then, these consumers are our clients, because we must safeguard their requirements.
Certainly if …
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"When you cannot get a compliment any other way, pay yourself one." - Mark Twain |
