Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part IX - Drill Down Questions
December 20, 2007 | Author: PM Hut | Filed under: Project Management Best Practices, Requirements Management
Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part IX - Drill Down Questions (#9 in the series Successfully Interviewing Your Project Customer and Gathering Project Requirements)
By Keith Mathis - PM Expert Live
While asking questions of the customer and the different experts involved, the interviewer must make sure he or she is prepared for the interview - not only with the standard questions, but with drill down questions. Drill down questions are additional questions that can be asked of the customer in a follow-up manner based on their answer.
There are two principles which must be remembered when asking drill down questions. By utilizing these principles, you will be surprised how much additional detail will be gained from the customer, and your understanding of the requirements will be more specific and obtainable.
Each question you create should have three or four follow-up questions for gaining information and clarity.
To have three or four follow-up questions to discuss with your customer shows the amount of planning you have put into trying to gather the requirements. This sets the tone and allows the customer to understand you are running the project based on thorough documentation. Having additional follow-up questions also prevents you from stammering around wondering what to ask next.
Drill down your questions until both the customer and the interviewer has a solid understanding of all requirements.
The question arises from people as to how far and how many questions should one ask. This is always dependent upon your understanding of the project and your relationship with the customer. For example, if I am conducting an interview with a customer for whom I have done three other projects, there is a lot of information I already know. However, if I am working with a customer for the first time, it is very unlikely that I have this kind of relationship or this background knowledge, so I am forced to interview the customer with more details.
It is clear that drill down questions show the customer you are prepared and will give you the
needed information and data.
Dr. Keith Mathis, founder and CEO of The Mathis Group, specializes in Project Management, Management Leadership, and Marketing training for private businesses and government agencies of all kinds. He offers 33 Project Management courses, is a Project Management Professional, is certified by the Project Management Institute and will customize every training session to your individual company’s needs. The Mathis Group also sponsors www.pmexpertlive.com, which is a powerful project management resource with free reports, podcasts, videos, and a monthly newsletter. He also offers customized management training and coaching on any subject with prolific communication and professionalism.
Related Articles
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part VIII - Asking the Questions
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part I - Introduction
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part V - Requirements Interview Process
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part III - Benefits of Conducting a Requirements Interview
- Successfully Interviewing Your Project Customer and Gathering Project Requirements - Part XI - Block Model
No comments yet.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.




