Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Implementing Qlik Sense

You're reading from   Implementing Qlik Sense Design, Develop, and Validate BI solutions for consultants

Arrow left icon
Product type Paperback
Published in Oct 2017
Publisher Packt
ISBN-13 9781786460448
Length 438 pages
Edition 1st Edition
Arrow right icon
Authors (2):
Arrow left icon
 Solanki Solanki
Author Profile Icon Solanki
Solanki
 Hegde Hegde
Author Profile Icon Hegde
Hegde
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Title Page
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
1. Consultant - An Introduction 2. Preparing for the Project FREE CHAPTER 3. Prerequisites to Start a Project 4. Requirement Gathering 5. Architecture Design 6. Development 7. Validation, UAT and Go-Live 8. Post Go-Live 9. Avoiding Common Pitfalls 10. Knowledge Sets 11. A Real Life Case-Study

Common mistakes in requirement gathering


It is said that humans makes mistakes, and requirement gathering is an activity performed by humans, so it is also prone to mistakes. Being a consultant, one should make sure that he/she tries to avoid common mistakes which happens during the requirement gathering for BI projects.

As we have learned since starting this chapter, requirement gathering is an important phase in the execution of a project, so any mistake made during requirement gathering may result in some risk to the project, which may cause the project to fail.

The following is a list of mistakes which are commonly made in the requirement gathering phase.

Lack of business understanding

Most of the times, the consultant starts requirement gathering without understanding the dynamics of that business. They may not be doing this intentionally, but they may skip this due to time factor or other pressure from the client or from the project manager, and at times due to overconfidence.

One common...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images