Development Team Scenarios

Overview
QlikView is an extremely flexible and easily adapted BI tool. As such, development
teams can organize around several models for support, administration, development,
training and management. These scenarios help guide discussions about possible
configurations for QlikView roles in a development environment.
It is recommended that the client consult its own IT standards for development, as
they may drive this decision, or at least narrow the allowed choices.
QlikTech does not expressly promote one of these scenarios over the others, but
asks that clients determine for themselves which of these configurations might work
best, given the nature of the QlikView development and the skills sets that exist.
Use these scenarios as templates to start your own diagram that is tailored to your
needs.
The subsequent pages in this document describe the scenarios.

2010 QlikTech International AB. All rights reserved. QlikTech, QlikView, Qlik, Q, Simplifying Analysis for Everyone, Power of Simplicity, New Rules, The Uncontrollable Smile and other QlikTech products and services as well as their respective logos are
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
Author: BPN, QlikTech NA

Development Teams Scenario #1

(Fully Centralized)

Scenario Description: This scenario depicts a full centralized development team. Departments dont need to
supply developers, support personnel or administrators to use QlikView applications. They request new applications
and then consume them along with central QlikView services.

Distributed Teams
Central Team

Strengths:
skill set sharing

Infrastructure
Support

QlikView
Administrators

data mgmt and re-use

QlikView
App Support

data access control

increased consistency

Support server
hardware and security

Manage, monitor and tune

QlikView Server and Publisher
Manage Jobs/Tasks/Permissions

best practices are easier to govern

Support QlikView Apps

and End Users

QlikView
Developers

lower TCO over time.

Project
Managers

Challenges:

QlikView
Designers
Develop scripting, database
connections, data models

Manage QlikView
projects

Build QlikView application

interfaces no scripting

End Users

lack of subject matter expertise in

departmental subjects
possible bottlenecks for services
and development
need chargeback or cost tracking to
allocate costs to departments

Users of
QlikView Apps
2010 QlikTech International AB. All rights reserved. QlikTech, QlikView, Qlik, Q, Simplifying Analysis for Everyone, Power of Simplicity, New Rules, The Uncontrollable Smile and other QlikTech products and services as well as their respective logos are
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
Author: BPN, QlikTech NA

Development Teams Scenario #2

(Mostly Centralized)

Scenario Description: This scenario depicts a mostly centralized development team. Enterprise development is retained as
a central function, allowing for the scripting and data modeling to be handled by expert QlikView developers and data
professionals. Departments are responsible for all training, project mgmt, application design, testing and support.

Distributed Teams
Strengths:

Central Team

skill set sharing

Infrastructure
Support

QlikView
Administrators

data mgmt and re-use

data access control

Manage, monitor and tune

Support server
QlikView Server and Publisher
hardware and security
Manage Jobs/Tasks/Permissions

Project Mgmt and Design still

located in departments where
subject matter experts reside

QlikView
App Support

QlikView
Developers

Challenges:
lack of design consistency
Develop scripting, database
connections, data models

Support QlikView Apps

and End Users
Project
Managers

QlikView
Designers

resource bottlenecks for central

team resources

End Users
Manage QlikView
projects

Build QlikView application

interfaces no scripting

processes governance for

departmental Professional
Developers

central support may lack subject

matter expertise

Users of QlikView applications

2010 QlikTech International AB. All rights reserved. QlikTech, QlikView, Qlik, Q, Simplifying Analysis for Everyone, Power of Simplicity, New Rules, The Uncontrollable Smile and other QlikTech products and services as well as their respective logos are
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
Author: BPN, QlikTech NA

Development Teams Scenario #3

(Mostly Centralized)

Scenario Description: This scenario depicts another mostly centralized development team. Support has been
moved to departments, but Project Mgmt is retained in the central team to better allow for QlikView expertise
and control of designs. Departments are responsible for all training, application design, and support.

Distributed Teams
Strengths:

Central Team

skill set sharing

QlikView
Administrators

data mgmt and re-use

Infrastructure
Support

Manage, monitor and tune

QlikView Server and Publisher
Manage Jobs/Tasks/Permissions

data access control

Support server
hardware and security

QlikView
Developers

Support still located in

departments where subject
matter experts reside

Project
Managers

Challenges:
QlikView
Designers

Develop scripting, database

connections, data models

Build QlikView application

interfaces no scripting

Manage QlikView
projects

End Users

QlikView
App Support

Support QlikView Apps

and End Users

design consistency
processes governance for
departmental Professional
Developers
resource bottlenecks for
central team resources

Users of QlikView applications

2010 QlikTech International AB. All rights reserved. QlikTech, QlikView, Qlik, Q, Simplifying Analysis for Everyone, Power of Simplicity, New Rules, The Uncontrollable Smile and other QlikTech products and services as well as their respective logos are
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
Author: BPN, QlikTech NA

Development Teams Scenario #4

(Mostly Decentralized)

Scenario Description: This scenario depicts a mostly decentralized development team, but with retention of
centralized infrastructure and administration for QlikView. Departments are responsible for all training, project mgmt,
application design, scripting, development, testing and support.

Distributed Teams
Strengths:

Central Team

minimal central team training

server/publisher consistency
Infrastructure
Support

QlikView
Administrators

flexible, fast development

most costs born by departments

QlikView
Developers

Manage, monitor and tune

Support server
QlikView Server and Publisher
hardware and security
Manage Jobs/Tasks/Permissions

Develop scripting, database

connections, data models

Project
Managers

Manage QlikView
projects

QlikView
App Support

QlikView
Designers

Challenges:
lack of development consistency
lack of re-use and standardization
lack of skill set sharing across
departments

End Users
Build QlikView application
interfaces no scripting

Support QlikView Apps

and End Users

Users of QlikView applications

2010 QlikTech International AB. All rights reserved. QlikTech, QlikView, Qlik, Q, Simplifying Analysis for Everyone, Power of Simplicity, New Rules, The Uncontrollable Smile and other QlikTech products and services as well as their respective logos are
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
Author: BPN, QlikTech NA

Development Teams Scenario #5

(Fully Decentralized)

Scenario Description: This scenario depicts a fully decentralized development team. Infrastructure is still maintained
centrally, but all other aspects of QlikView development, testing, support, training a usage are distributed to departments.

Distributed Teams
Strengths:

Central Team

all development costs born by

departments
Infrastructure
Support

flexible, fast development

minimal central team training

Support server
hardware and security

QlikView
Developers

Project
Managers

QlikView
Administrators

Develop scripting, database

connections, data models

Manage QlikView
projects

Challenges:
lack of consistency

QlikView
Designers

Manage, monitor and tune

QlikView Server and Publisher
Manage Jobs/Tasks/Permissions

QlikView
App Support

End Users
Build QlikView application
interfaces no scripting

Support QlikView Apps

and End Users

lack of re-use and standardization

lack of governance
lack of skill set sharing across
departments
higher TCO over time

Users of QlikView applications

2010 QlikTech International AB. All rights reserved. QlikTech, QlikView, Qlik, Q, Simplifying Analysis for Everyone, Power of Simplicity, New Rules, The Uncontrollable Smile and other QlikTech products and services as well as their respective logos are
trademarks or registered trademarks of QlikTech International AB. All other company names, products and services used herein are trademarks or registered trademarks of their respective owners. The information published herein is subject to change without notice.
This publication is for informational purposes only, without representation or warranty of any kind, and QlikTech shall not be liable for errors or omissions with respect to this publication. The only warranties for QlikTech products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting any additional warranty.
Author: BPN, QlikTech NA