Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

   

Linda Webb

Got breaking Oracle news?    Burleson Consulting Oracle News

Click here for more Oracle News Headlines

 


Ralph Kimball gives secrets on gathering data requirements

Ralph Kimball, a highly-respected data warehouse guru has published great advice for ascertaining end-user requirements: 

http://www.intelligententerprise.com/showArticle.jhtml?articleID=160403897&pgno=1 

  •   Learn a bit about the business beforehand by reviewing the Web site or annual report to understand company-specific vocabulary and hot-button issues.

  •  Meet with interviewees on their own turf. Go to their offices or conference rooms, rather than IT meeting spaces.

  •  Prior to the interview, send out an announcement describing the high-level discussion topics and confirming the interview time and place. Don't attach a detailed questionnaire to this meeting notice. You can't achieve a conversational flow if you're reviewing questionnaire results-presuming anyone bothers to complete the survey.

  •  Interview questions prepared in advance are fallback devices, used only if uncomfortable lulls occur in conversations or to ensure key points are covered before ending sessions.

  •  Most good conversations tend to wander, so remember your session goals and steer conversations back on track if you stray too far from core issues. Stay at a relatively high level in the interview's early stages. Don't follow an early comment to a very low level of detail, only to run out of time and discover that you haven't discussed three other major areas of responsibility with important requirements for the DW/BI effort.  

Kimball also has a great quick tips section:

Dos and Don'ts for Gathering Requirements

  • Do talk with a vertical span of businesspeople, including executives, directors/managers and analysts.
  • Don't rely on a single user to represent the business, even if it's less intimidating and easier to schedule.
  • Do allow plenty of time to coordinate calendars for scheduling, especially with traveling business management.
  • Don't get angry if someone has to reschedule at the last second.
  • Do get help from skilled assistants to manage scheduling.
  • Don't offload interview coordination to someone unfamiliar with the project or organization.
  • Do arrive for the interview on time.
  • Don't bring food to the interview, leave your cell phone on or spill a large latte over the interviewee's conference table and sample reports.
  • Do plan on a two-person requirements team in each interview, if possible.
  • Don't overwhelm a lone interviewee with six people sitting across from him, Inquisition-style.
  • Do designate one person as the lead interviewer with primary responsibility for steering the session.
  • Don't turn the interview into a free-for-all, bouncing randomly from one interviewer to the next.
  • Do flesh out your scribbled interview notes immediately, or you'll lose much of the interesting detail by the next day.
  • Don't schedule more than four interviews per day.
  • Do document what you learned during the requirements gathering and feedback results to close the loop with participants.
  • Don't lose sight of the scope of your DW/BI requirements process.
     

 

 
��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational