Qlik project methodology handbook v 1.0 docx

16,249 views
15,859 views

Published on

Published in: Business, Technology
68 Comments
71 Likes
Statistics
Notes
No Downloads
Views
Total views
16,249
On SlideShare
0
From Embeds
0
Number of Embeds
172
Actions
Shares
0
Downloads
0
Comments
68
Likes
71
Embeds 0
No embeds

No notes for slide

Qlik project methodology handbook v 1.0 docx

  1. 1. QlikView | QlikView Project Methodology Handbook QlikView Project Methodology Handbook First Version for Roll out within QT “QPM a business-driven and iterative approach to delivery of QlikView for the Enterprise”
  2. 2. www.qlikview.com Preface Business Discovery is a whole new way of doing things for BI designed to meet today’s heightened expectations. We live in a fast changing world so we need to have a QlikView Project Methodology (QPM) that fits with our QlikView Capabilities and empowers our customer’s in getting the full value from their QlikView investments After you acknowledge this you're ready to embrace change and use QPM to your advantage. In this document you will learn about the “QlikView Project Methodology”. Together with your knowledge and experience you must be able to speak, listen and understand the Project Methodology language and feel comfortable in fulfilling your role in any QlikView project. 2 © 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. qlikview.com
  3. 3. www.qlikview.com Revision History Revision Date Description of changes Author Prel 0.1 2011-08-24 First draft of QDM Handbook Ben Sterry Prel 0.2 2011-09-07 Updated with input from Jeroen Nieuwenhuijs and Gustaf Pilo. Ben Sterry Prel 0.3 2011-09-27 Combining QPM Handbook with QDM Feedback and input from Art Feeney, Ben Sterry, Hernan Azpiri, Laura Gutierrez and Gustaf Pilo. Jeroen Nieuwenhuijs Prel 0.4 2011-10-11 Added Enterprise Platform Deliverables Jeroen Nieuwenhuijs Prel 0.5 2011-10-26 Refined all chapters Feedback and input from Art Feeney, Ben Sterry, Hernan Azpiri, Laura Gutierrez and Gustaf Pilo. Jeroen Nieuwenhuijs Rev 1.0 2011-10-31 First official version Jeroen Nieuwenhuijs 3 © 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. qlikview.com
  4. 4. www.qlikview.com Table of Contents Summary................................................................................................................7 1. Introduction........................................................................................................8 1.1 Background..................................................................................................................8 1.2 Principles......................................................................................................................8 1.3 What is a QlikView project?.........................................................................................9 1.4 What is Project Management?.................................................................................10 1.5 What is QlikView Project Management Methodology?............................................10 1.6 When to use?............................................................................................................11 1.7 Five phases.................................................................................................................11 1.8 Tollgates.....................................................................................................................12 1.9 Tollgates and Milestones...........................................................................................12 2. Tollgate 0 - Start Pre-study.............................................................................14 3. Phase 1: Pre-Study Phase TG0 – TG1............................................................16 3.1 Start Project Management .......................................................................................19 3.1.1 Prepare Project organization..................................................................................19 3.1.2 Define Initial Objective and Scope..........................................................................20 3.1.3 Determine Training Requirements.........................................................................21 3.1.4 Initial schedule and Budgeting...............................................................................22 3.1.5 Tollgate 1.0 Approval - SG Meeting........................................................................23 3.2 Introduction QlikView Enterprise Platform...............................................................23 3.2.2 Define Architecture Scope......................................................................................24 3.2.3 Analyse current Baseline Business Architecture....................................................25 3.2.4 Identify Initial Business Requirements...................................................................25 3.2.5 Identify Initial Data Requirements.........................................................................26 3.2.6 Create Architecture Vision......................................................................................27 3.2.7 Identify Key Considerations for Data Management...............................................27 3.2.8 Specify Infrastructure Requirements .....................................................................28 3.2.9 Security Requirements...........................................................................................28 3.2.10 Publisher Requirements.......................................................................................29 3.2.11 Identify Outline QlikView Solution Scenario’s......................................................29 4. Phase 2: Planning Phase TG 1- TG 2..............................................................31 4.1 Project Management Planning..................................................................................32 4 © 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. qlikview.com
  5. 5. www.qlikview.com 4.1.1 Update prioritize Business Requirements..............................................................32 4.1.2 Estimate Requirements..........................................................................................32 4.1.3 Validate Project objective and Scope ....................................................................33 4.1.4 Create Work Breakdown Structure........................................................................33 4.1.5 Create App Work Packages.....................................................................................33 4.1.6 Determine Project Approach.................................................................................34 4.1.7 Schedule Execution and Implementation phases..................................................34 4.1.8 Review and finalize Project Organization...............................................................35 4.1.9 Assign resources to the roles and responsibilities.................................................35 4.1.10 Allocate Resources................................................................................................35 4.1.11 Review and allocate Project Budget.....................................................................36 4.1.12 Analyse Risk..........................................................................................................36 4.1.13 Review and finalize Business Case........................................................................37 4.1.14 Create Project Plan...............................................................................................37 4.1.15 Set-Up SG Meeting...............................................................................................37 4.1.16 Tollgate 2.0 Approval - SG Meeting......................................................................39 4.2 Plan QlikView Enterprise Platform............................................................................40 4.2.2 Confirm and Elaborate Architecture Principles......................................................40 4.2.3 Develop Target Infrastructure Description.............................................................40 4.2.4 Define QlikView Roadmap......................................................................................40 4.2.5 Develop Target Data Architecture Description......................................................41 4.2.6 Define Data Staging Requirements.........................................................................41 4.2.7 Define Data Roadmap ............................................................................................42 4.2.8 Define Application Architectures............................................................................42 4.2.9 Develop Enterprise Architecture Plans ..................................................................43 4.2.10 Business Transformation Risks ............................................................................44 4.2.11 Establish the Architecture Project........................................................................44 4.3 Plan Application Cycle’s.............................................................................................44 4.3.1 Identify QlikView Users...........................................................................................44 4.3.2 Define Main Users Goals........................................................................................44 4.3.3 Define Usage Patterns............................................................................................44 4.3.4 Invent QlikView Solution to Meet Users Goals and Usage Patterns.....................45 4.3.5 Define Main Navigation Paths...............................................................................45 4.3.6 Create Prototype....................................................................................................45 4.3.7 Polish UI Elements..................................................................................................45 5. Phase 3: Execution Phase TG 2- TG 3...........................................................47 5.1 Managing the Execution Phase.................................................................................48 5.1.1 Brief the team.........................................................................................................48 5 © 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. qlikview.com
  6. 6. www.qlikview.com 5.1.2 Set Up and Maintain Administration......................................................................48 5.1.3 Initiate Control Procedures....................................................................................49 5.1.4 Set-Up Progress Control.........................................................................................49 5.1.5 Issue Management.................................................................................................50 5.1.6 Risk Log...................................................................................................................51 5.1.7 Exception Management..........................................................................................51 5.1.8 Tollgate 3.0 Approval - SG Meeting........................................................................51 5.2 Realize QlikView Enterprise Platform........................................................................51 5.2.1 Set Up QlikView Environments...............................................................................51 5.2.2 Initial Data Load......................................................................................................52 5.2.3 Incremental Loads..................................................................................................52 5.2.4 Ongoing Project Infrastructure Support.................................................................52 5.3 Agile App Development.............................................................................................53 5.3.1 Build........................................................................................................................53 5.3.2 Test.........................................................................................................................53 5.3.3 User Review and Accept.........................................................................................54 5.3.4 Refine......................................................................................................................55 6. Phase 4: Implementation Phase TG 3 - TG 4.................................................56 6.1 QlikView Enterprise Platform Governance................................................................57 6.1.1 Set Up QlikView Competence Center (QVCC)........................................................57 6.1.2 Meta Data Management........................................................................................57 6.1.3 Initiate Maintenance Process.................................................................................57 6.2 Move QlikView Applications to Production...............................................................58 6.2.1 Migration................................................................................................................58 6.2.2 User Education........................................................................................................58 6.2.3 Set up User Support...............................................................................................58 6.2.4 QlikView Support On Boarding ..............................................................................58 6.2.5 Tollgate 4.0 Approval - SG Meeting........................................................................59 7. Phase 5: Conclusion Phase TG 4 – TG5..........................................................60 7.1 Evaluation..................................................................................................................61 7.2 Project closure documentation.................................................................................62 7.3 Financial project closure............................................................................................62 7.4 Tollgate 5.0 Approval - SG Meeting...........................................................................62 8. Roles & Responsibilities...................................................................................63 8.1 Overview....................................................................................................................63 6 © 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. qlikview.com
  7. 7. www.qlikview.com Summary QlikTech has created QlikView Project Methodology (QPM). QPM is perfectly suited to the development of QlikView applications in an Enterprise Environment. QPM is developed by QlikTech consultants as best practice and can also be used by QlikTech customers and Partners. It is designed to control the implementation and deployment phases in a larger enterprise project. QPM elements can be used to manage smaller QlikView projects. The goals for QPM are to: • Support QlikView Consultants in implementing a QlikView Enterprise Platform; • Foster best practice for QlikView Application Development; • Manage Enterprise implementations and roll out’s; • Maximise our customer’s ROI in QlikView. The aim of the document is to: • Define consistent, repeatable steps for the implementation of QlikView; • Speak the same “project language” within QlikTech with Customers and Partners. The intention of the document is that it will serve as a “cook book” for each participant of a QlikView project. With this Handbook, the reader becomes acquainted with the process of the project life cycle, the key deliverables & activities for each phase and the project playground. This results in achieving optimum quality, service management, and time to market by a single way of working. This Handbook describes three key areas for implementing QlikView: • Project Management Process, • Creating the QlikView Enterprise Foundation, • Agile Development of QlikView App’s. Together they form the QlikView Project Methodology. Readers target group of this handbook are: • Project Managers, • Technical Account Managers, • Project team members, • Enterprise Architects, • Solution Architects. • Professional Service Manager and • all other professionals involved with QlikView projects. Should you require more detailed information, please contact your QlikView Project manager. 7 © 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. qlikview.com
  8. 8. www.qlikview.com 1. Introduction 1.1 Background Business Intelligence (BI) emerged twenty years ago as a tool for decision-making. Originally used exclusively by analysts, power users, and board-level executives, it has slowly evolved into a more democratic medium as organizations have come to realize that decision-makers at all levels and in all departments need access to timely, relevant information. Today, there is an increasingly strong move towards the “consumerisation” of BI as people are demanding the same speed and ease-of-use from their workplace software as ubiquitous applications have delivered in their personal life. When decisions are well known (“routine decisions”) a traditional architecture can support them. The requirements for basic financial reporting, for example, don’t change often. But many times, our customers need to make decisions that are novel, such as what markets to expand into, what products to introduce, or how to respond to a new competitor. These types of decisions will often require new information, and will often be very iterative in nature. The way the decision is made changes as the decision maker gains more information. And once made, such decisions can change the landscape entirely. We will follow this model, allowing domain and decision-specific QlikView App’s to be joined together to form the QlikView Enterprise Platform. And as requirements change, QlikView App’s will be added, removed, or updated quickly because they don’t require an assessment of their impact on a universal “single version of the truth” data model. 1.2 Principles Traditional BI implementation methodologies have focused on solving data storage, integration, processing, and presentation issues. With the goal of decision support left unachieved, a new implementation model for QlikView has been developed. QlikView project teams have the challenge to move beyond legacy BI implementation methodologies and QPM that supports a rapid, iterative development style. The ability to rapidly source information, connect it to other information in both a tightly and loosely integrated fashion, and quickly connect QlikView App’s together will be critical in meeting rapidly changing requirements. By using this Methodology we will be able to make a difference in the customer implementation experience and making the best use of the QlikView capabilities. This methodology is replacing the traditional implementations and instead focusing on making QlikView implementations as rewarding as possible. This model changes the focus from data driven to decision driven. It focuses on the requirements of the decisions being made, rather than on corralling all available data. 8 © 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. qlikview.com
  9. 9. www.qlikview.com The success of QlikView is largely due to the fact that it accepts constant change as the norm. Every principle of the methodology is centred on delivering value-producing functionality quickly, and in a way that anticipates significant change in direction. The key characteristics of QPM are that it relies heavily on agile development and business opportunity management (as opposed to the document-driven approach of the waterfall approach). For each QlikView initiative within the project and for each of its levels of elaboration, the same sequence of steps (cycle) is involved during the Execution Phase. There are 3 key principles that underpin the methodology: • Enterprise Ready: o The QlikView technology perspective that defines the hardware, operating systems, networking solutions and data architecture used by the customer. • Business Discovery: o Team based approach to development where requirements are changing based on new Business Discoveries. QPM makes these possible using Discovery loops where a team is able to deliver a QV App (iteration) a short time frame. The objective is to front-load the with the most profitable or highest value deliverables and release them as soon as possible so that they can start making money for our customers • Project Control: o To keep activities and deliverables under control throughout the project life cycle. 1.3 What is a QlikView project? Although “project” is an often heard word, especially in the world of information technology, it is crucial to understand the meaning of this word. Understanding this word enables you to understand why and how things are being set-up and arranged within the QlikView project environment. Many definitions of the word “project” can be found on the internet and project management documentation. Following you will find a definition which is valid for the QlikView project environment. “A QlikView project is a temporary Endeavour Undertaken to create a unique Solution for enabling our customers in making Business Decisions” Typical characteristics of a QlikView project are: • A finite and defined lifespan; • A dedicated budget; • Defined and measurable business products; 9 © 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. qlikview.com
  10. 10. www.qlikview.com • A corresponding set of activities to achieve the business products; • A temporary organization structure with our customers and partners, with defined responsibilities, to manage the project. Due to the characteristic of having a temporary organization structure, people participating in the project will, quit often, play a double role. As a project participant you should be aware of these double roles, because each individual must be able to perform on his or her operational task as well on the project task. Each project falls within a specific business context. A QlikView project may be stand-alone, it may be one in a sequence of related projects, or it may form part of a program or corporate strategy. 1.4 What is Project Management? Project management is the use of knowledge, skills, tools, and techniques to manage activities in order to meet or exceed stakeholder needs and expectations from a project. Meeting or exceeding stakeholder needs and expectations invariably involves balancing competing demands among: • Scope, time, cost, and quality. • Stakeholders with differing needs and expectations. • Identified requirements (needs) and unidentified requirements (expectations). 1.5 What is QlikView Project Management Methodology? QPM is a description of all project management activities, documents and QlikView Deliverables in all the phases of a QlikView project. In other words it is the handling of all the project work in a structured way when running a project from start to end, involving a set of phases, activities, deliverables and templates to be used at different times for different purposes. The purpose of a common project management methodology is to have a common terminology, common steering structure, common templates and common organization in all aspects regarding QlikView projects. Another important purpose of the project management methodology is to ensure a business-focused and efficient project management, resulting in 10 © 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. qlikview.com
  11. 11. www.qlikview.com high-quality project performance and shortened project lead-time. 1.6 When to use? QPM must be followed when: • Customer purchase licenses at a cost that exceeds 200.000 Dollars and where QlikTech owns the Services delivery. Global Services Management must approve any exceptions from this rule. • And/or Project plan exceed six month calendar lead-time between TG0 – TG5 QPM can be followed when: • For all other projects. The intention of QPM is that it will serve as a ”cook book” for the project participants. Depending of the size of your project you can still decide which part of QPM could add value in managing your project. 1.7 Five phases QPM is divided into five distinctive phases • Pre Study; • Planning Phase; • Execution; • Implementation; • Conclusion. 11 © 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. qlikview.com
  12. 12. www.qlikview.com Each phase begins with a Tollgate needs to be passed (Go/NoGo decision). Each phase includes a different set of activities and will result in a document as a firm deliverable, based on a predefined template. During a project’s life cycle many major and minor decisions are taken, the two main ones are Tollgates (for which the Steering Group is responsible) and Milestones (for which the project manager is responsible). Tollgates and milestones are both part of a project methodology and serves as a check mark for the project. 1.8 Tollgates Tollgates must be used regardless the size of the project. The benefits of tollgates are: • An agreed and controllable sequence for the project; • Connect different approval criteria to different TG’s; • Clear opportunities to verify the status of the project; • Verify the benefits to the business; • Result, time, cost and risk level status; • The possibility for the Steering Group to delegate authority to the project step-by-step; • A short-term focus point; • A uniform decision process in all projects, independent of expected result. 1.9 Tollgates and Milestones Tollgates are critical decision points in a project, at which formal decisions are made concerning the projects aim and execution. The number and function of tollgates is standardized TG0 – TG5. • A decision point concerning aims and execution of a project. • A decision to make an investment or to take a hidden cost. One could consider a Milestone as a set of deliverables the team must achieve, and a Tollgate as the decision point after the Milestone is achieved when the sponsors and stakeholders take a deliberate decision to move forward, to pause or to stop the project. 12 © 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. qlikview.com
  13. 13. www.qlikview.com 13 © 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. qlikview.com
  14. 14. www.qlikview.com 2. Tollgate 0 - Start Pre-study At tollgate 0, there must be a decision whether or not to start a project as a pre-study and to be done by whom (an appointed Project Manager). This phase is to be seen as a transparent hand-over phase from the Sales and Pre-sales organization, where the focus will shift from what to deliver towards how to deliver, when. For our customers this means they will have to do a handover of the people involved in the Buying Process to the People who are responsible for the project work. In some cases, the pre-study could include more than one alternative suggestion for solving a solution. If so, a decision should be made for which alternative to choose, and why this alternative is chosen. Basis for decision: • Result from the Customer Centric Selling Sales process. In particular from the Prove Value phase. Milestone including: • SIB • High Level project requirements and a first High Level Implementation plan • ROI/TCO • Opportunity Success Metrics Mandatory participant for this decision: Project Sponsor Meeting organizer: Project Sponsor or if already in place with the Customer the Chairman of the SG in conjunction with presumptive project manager. 14 © 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. qlikview.com
  15. 15. www.qlikview.com Decisions • Initiate pre-study phase (Go/NoGo) – starting or not starting the project. • Appoint a Project Manager for the pre-study phase . 15 © 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. qlikview.com
  16. 16. www.qlikview.com 3. Phase 1: Pre-Study Phase TG0 – TG1 At the start of any QlikView project, there will be a variety of ideas and opinions about the purpose and scope of the project, what the final result of the project will be, and how the project will be carried out. The Pre-Study Phase is concerned with taking these ideas and intentions and developing them into a formal, planned, resourced and funded project. A common practice is to perform some high-level requirements envisioning early in the project to help come to a common understanding as to the scope of what you're trying to accomplish. The goals at this point are to identify the business goals for the effort, develop a common vision, and swiftly identify the initial requirements for QlikView at a high-level. You do not need to write mounds of documentation at this point, instead you will identify the details later during development cycles. Very often this initial requirements modeling effort is on the order of days, not weeks or months as we see on traditional projects. The pre-study phase is the preparatory phase in QPM, before the project is formally started. During the pre- study phase, the business opportunity for the expected outcome of the potential project is assessed. All the relevant commercial, technical and organizational aspects are considered and addressed. In order to define the project it is first necessary to clearly and explicitly define what the project is intended to achieve and what its scope of interest will be. By defining this first, a benchmark is created for assessing the quality of what is actually produced at the end of the project. The purpose of the pre-study phase is to ensure that a business idea is technically and commercially feasible, that it will fulfill the expressed and unexpressed requirements and needs of the customer, and will be aligned with the organization’s business direction. Another important purpose is to analyze if there are any possible alternatives in how to run the project. The possible alternatives should each be depicted in a SWOT matrix and a recommendation to be made for one of the alternatives. The Pre-Study Phase must also define what resources and associated time commitment are required to carry out the project. The work breakdown structure provides a first basis from which this estimation can be carried out. The resource and time commitment can be used to calculate an end date for the project and an estimate of its cost. This information is key input into the establishment of a business case for the intended project. The way the project is managed and executed is the key to its success. Early involvement of Senior Executives is crucial. Make sure that the Customer has assigned a responsible person as the Project Sponsor. The involvement of the right people for data capture and decision making is also crucial. It is necessary to identify and recruit these people at the start of the project and to define the project organization structure. It is also necessary to establish the procedures that will be used by the people in the Project Organization Structure to carry out and control the project work. 16 © 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. qlikview.com
  17. 17. www.qlikview.com Finally, in order to establish a resourced and funded project, it is necessary to establish a clear and convincing business case for the project. This business case should be reviewed, and accepted by customer’s management. The business case will identify the projected benefits of meeting the objectives of the project, and balance these against the costs and risks associated with realizing these benefits. The business case can also be used as a benchmark to compare against actual results, costs and benefits in order to assess the ultimate success of the project. This phase is described here as a sequence of steps. In reality, once the objective and scope have been defined, many of these steps occur in parallel, and the step products are developed iteratively, since there are many dependencies between the steps. It is necessary to plan the Pre-Study Phase, albeit in an informal manner. 17 © 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. qlikview.com
  18. 18. www.qlikview.com • Input (Result from the Prove Value phase: o SIB o High- Level Implementation plan o ROI/TCO o Opportunity Success Metrics • Key - Activities: o Start Up Project o Define Business Objectives & Requirements o Define Enterprise Platform Requirements • The purpose o Ensure that the project is technically and commercially feasible, o Ensure the project can fulfill the expressed and unexpressed requirements and needs of the customer o Analyze any possible alternatives in how to run the project  Using a SWOT matrix. • Output o Pre-study report. o Business Case. o This is required to pass TG1 and move to the planning phase. 18 © 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. qlikview.com
  19. 19. www.qlikview.com 3.1 Start Project Management 3.1.1 Prepare Project organization The purpose is to select and prepare the people, whose involvement will be necessary for the QlikView project to succeed. In a way that • ensures that all major interest groups are appropriately represented, • clearly identifies roles and responsibilities, • ensures that the best individuals to fulfill roles and responsibilities are selected, Key Activities are: • Recruit SG o Assemble a senior management team (Customer and QlikTech) which will direct and be accountable for the project and gain management commitment. Ensure that those senior Managers with a significant interest in the successful outcome of the project are properly represented. o Generally identify the lowest level person for each SG role. Work up the organization chart until a person is found who can make the decisions "stick". • Recruit Key Stakeholders o Identify other people who are critical to the success of the project. They are management level personnel who will be affected by the project, but are not the primary decision makers. • Recruit Development Team o There are two types of team members, customer and QlikTech. People assigned to team member roles will usually fulfill the "produce" responsibility for tasks. Team members may change from phase to phase as different skill sets are required. Identify appropriate personnel required for the phase, define the team structure and, if necessary appoint Team Leaders • Recruit Key Resources o Identify any additional technical or business specialists required to support the project. These roles contribute to the creation of products by providing information about the business and reviewing QlikView Application(s). They generally fulfill the "consult" and "approve" responsibilities. They will include both customer and Qliktech personnel. • Suppliers (Services, Competence or Products) o List suppliers related to the assignment or the project outcome, such as partners, subcontractors and consultants, by name and function. • Create Project Organization Chart o Using the Pre-Study Document, allocate the identified personnel to one or more roles. Ensure all key individuals are assigned an appropriate role, but don't overwhelm the 19 © 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. qlikview.com
  20. 20. www.qlikview.com project with too many people. Produce a Project Organization Chart defining reporting and communication lines between all parties involved in the project. • Review Project Organization o Conduct a review of the Project Organization to ensure that the proposed organization reflects all participants needed to achieve the QlikView project objective. 3.1.1.1 Templates 1. Pre-study Report_ QPM Template Rev 1.0 3.1.2 Define Initial Objective and Scope The purpose is to clearly define the project boundaries, in a way that • identifies the types of boundary (scope dimensions) relevant to the project, • takes account of the background to the project, • explores the variety of objectives and scope that the project could cover, • Clearly and explicitly defines what the project will cover, clearly and explicitly defines what the project will not cover. With this a commonly understood target and benchmark is available to project members and other interested parties by which they can steer the direction of the project and assess the quality of the final QlikView Solution. It is important to start creating a clear definition of the purpose and scope of the project to ensure that both Customer and QlikTech personnel are clear about the field of reference. Any project carried out by an organization should be addressing one or more of the Business Objectives of the organization. If it does not, why is the project being carried out? Therefore to establish the objectives and scope of the project, it is first necessary to identify the overall reason for the project by relating it to one or more objectives of the organization on an Enterprise level. This will put the project into context for the organization as a whole. It is vital that the project objective be clearly stated and agreed before proceeding with the rest of phases. If this is not possible, then do not continue. The project objective can then be further defined in terms of scope. There are two aspects to project scope, the scope of the pre-study, and the scope of the solution. At the start of the project it is unlikely that the problems and requirements will be fully understood. However, in order to avoid wasting time by analyzing irrelevant areas, the scope of investigation will help focus on those areas thought most likely to be impacted by the project. Therefore the scope of investigation may well expand as a better understanding of the problems is achieved. Scope can be expressed in terms of dimensions. These include business organization, business functions, data, geography, systems, operating environments, etc. Identify the dimensions appropriate to the project and determine those components in scope and those out of scope. 20 © 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. qlikview.com
  21. 21. www.qlikview.com Scope will be further defined in terms of problems and requirements during preparing the QlikView Enterprise Platform. In effect the move from objective to requirements is a continuum illustrating the progressive expansion of the project definition. Key Activities are: • Define Project Objective o Conduct workshops and/or interviews with customers to identify the project objective. This must be clearly stated and agreed. The project objective must also relate back to a business objective, to ensure that the project is aligned with the business direction of the organization. • Establish Scope Dimensions o Determine which dimensions of scope to apply to defining the project. Diagrammatically represent each dimension of scope, explicitly stating as narrative bullet points what is in scope and what is out of scope. Identify the constraints, specific limitations or exclusions within which the project must operate. Record any assumptions made in defining the scope of the investigation. 3.1.2.1 Templates 1. Pre-study Report_ QPM Template Rev 1.0 2. Business Scope_QPM Template.doc 3.1.3 Determine Training Requirements The first objective is to effectively train the development staff. QlikView application development training is typically a fraction of the time of other software training cycles. A typical mid level developer usually can be effectively trained in a matter of weeks. In some cases new QlikView customers pair an experienced QlikView consultant with the internal staff for a short period of time; this fosters best practices and shortens the learning curve. The purpose of this important activity is to identify the QlikView training modules that are required to enable individuals to fulfill their roles and responsibilities on the project. Assess the capabilities and skills of all those identified as part of the Project Organization. Based upon this assessment establish a training plan to acquaint the project team members with the methodologies, technologies, and business areas under study. Your local Trainer and/or Training Manager is responsible for this activity. 3.1.3.1 Templates 21 © 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. qlikview.com
  22. 22. www.qlikview.com 1. Enterprise Training Strategies.doc 3.1.4 Initial schedule and Budgeting In the Pre-Study Phase the aim is to define the initial project schedule and budget. It the planning phase this needs to be finalized and confirmed. Once the objective and scope are decided, it is necessary to determine what activities are required to be carried out to meet the objective. The dependencies between these activities can then be determined, which in turn allows resources and timescales to be estimated. This needs to be done for the whole project (project plan), and then in more detail for the next stage of the project. This step is concerned with the overall project. The project schedule is not intended to direct resources to specific activities on certain dates. Key Activities are: • Estimate Duration o Project schedule estimates will be determined as duration or elapsed time. Determine the duration for each step. It is recommended that you estimate in units of a day. Step level estimates are unlikely to be less than one day. When estimating duration, include expected non-productive and non-effective time. Alternatively, produce an initial top- down estimate for the each phase and apportion to the component steps. • Establish Resource Requirements o When estimating duration, define an initial requirement for resources. For the project schedule, it is sufficient to estimate the number of each type of resource required, rather than specific people, e.g., 2 Solution Architects. Concentrate on identifying the resource types who will either be part of the project team or who will have a significant impact on the project. • Develop an initial schedule of project activities. o Determine the proposed project start date and use the scheduler to calculate the stage and step start and end dates. Validate these dates against the project constraints. Adjust scope, dependency and resources until a satisfactory balance is achieved. Revise any assumptions that have been modified. • Prepare Project Budget o Estimate the internal and external staff costs by step. Staff costs are a function of step duration, resource equivalent and chargeable rate. Estimate non-staff costs by step:  Project Training ,for the project team to develop the application,  Installation Training, for customers, operations, etc. to use the application,  Miscellaneous, includes supplies, copying and printing, accommodation,, subsistence, travel, or other costs which cannot be classified above,  Aggregate the costs by phase. • Review Time and Budget 22 © 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. qlikview.com
  23. 23. www.qlikview.com o Conduct a product review of the Project Schedule and Budget to ensure that the scope meets the business needs and that all technical standards are met. 3.1.4.1 Templates 1. Pre-study Report_ QPM Template Rev 1.0 2. Budget_QPM Template 3. Implementation Framework Calculator_QPM Template 4. Project estimation worksheet_QPM Template 3.1.5 Tollgate 1.0 Approval - SG Meeting The Pre-Study Report is the first ‘contract’ between the Project Manager and SG concerning the next phase of the project. Although this meeting is not intended as a detailed "line item" review, it is important that the SG fully understand and accept this tollgate. If the SG authorizes the project to continue they must be prepared to provide unconditional support to the Project Team. 3.2 Introduction QlikView Enterprise Platform This chapter describes the initial phase of the QlikView Enterprise Platform Development. This will be done in parallel with the Project Management activities. It includes information about defining initial Business Requirements, creating the Architecture Vision. Some people will tell you that you don’t need to do any initial architecture modeling at all. However, experiences proved that doing some initial architectural modeling offers several benefits: • Improved productivity. o You can think through some of the critical technical issues facing your project and potentially avoid going down fruitless technical paths. • Reduced technical risk. o Your team gains the advantage of having a guiding vision without the disadvantage of having to overbuild the overall QlikView Solution – just because you’ve modeled it doesn’t mean you have to build it. • Reduced development time. o Initial architecture modeling enables you to make better cost and time estimates for your project, two pieces of information which management will want. • Improved communication. o Having a high-level architecture model helps you to communicate what you think you’re going to build and how you think that you’ll build it, two more critical pieces of information desired by management. • Scaling QlikView development. o Your initial architecture model will be a key work product in any "QlikView at scale" efforts because it provides the technical direction required by sub-teams to define and guide their efforts within the overall project. 23 © 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. qlikview.com
  24. 24. www.qlikview.com The architect needs to determine things such as the expected total number of users and their location, the number of subjects that might ultimately be addressed (e.g., sales, finance, purchasing, HR, etc.), the potential sources of information, anticipated data volumes, data refresh expectations, etc. These macro “requirements” help Enterprise organizations create the first structure, or shell, of the overall solution for the QlikView Enterprise Platform without knowing the exact number of apps and how apps will be laid out. These initial analyses and inputs result in Architecture design decisions such as the types of databases needed (warehouses, marts, operational data stores, etc.), data acquisition and integration methods required (batch processes, real-time updates, change data capture, information busses, etc.), and the potential methods of delivery (dashboards, reports, scorecards, etc.). Once the Enterprise Platform has been determined, QlikView functionality will support the given architecture selected. It’s through the definition of these key components, the principles created and planning in Phase that delivery can begin. The deliverables for the QlikView Enterprise Platform are being used to define the specific components of the QlikView apps, refine them, and ultimately deliver value to the business in the form of metrics, KPIs and analytical solutions that must fit within the architectural blueprint. In other words, in order for the project team to begin a project, the architecture on which their QlikView apps will be built must exist. It’s during the iterative delivery process that the business and the project team get to put their mark on the solution. Key - Activities are: • Analyze current Baseline Business Architecture; • To define the key business requirements to be addressed in this architecture effort, and the constraints that must be dealt with; • To validate the business principles, business goals, and strategic business drivers of the organization and the enterprise architecture Key Performance Indicators (KPIs). • To define the scope of, and to identify and prioritize the components of, the QlikView Enterprise Platform effort 3.2.1.1 Checklist 1. Enterprise Readiness FAQ[1].pdf 2. Enterprise Readiness Material.doc 3.2.2 Define Architecture Scope Key-Activities are: • Define what is inside and what is outside the scope of the QlikView Architecture efforts; • The breadth of coverage of the enterprise; • The level of detail required; • The partitioning characteristics of the architecture; 24 © 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. qlikview.com
  25. 25. www.qlikview.com • The specific architecture domains to be covered (business, data, application, technology); • The extent of the time period aimed at, plus the number and extent of any intermediate time period; • QlikView Applications created in previous iterations within the enterprise 3.2.3 Analyse current Baseline Business Architecture Knowledge of the Business & BI Architecture is a prerequisite for QlikView architecture work and is therefore the first architecture activity that needs to be undertaken, if not catered for already in other organizational processes (enterprise planning, strategic business planning, business process re-engineering, etc.). In practical terms, the Business & BI Architecture is also often necessary as a means of demonstrating the business value of subsequent architecture work to key stakeholders, and the return on investment to those stakeholders from supporting and participating in the subsequent work. The scope of the work will depend to a large extent on the enterprise environment. In some cases, key elements of the Business Architecture may be done in other activities; for example, the enterprise mission, vision, strategy, and goals may be documented as part of some wider business strategy or enterprise planning activity that has its own lifecycle within the enterprise. In such cases, there may be a need to verify and update the currently documented business strategy and plans, and/or to bridge between high-level business drivers, business strategy, and goals on the one hand, and the specific business requirements that are relevant to this architecture development effort. The business strategy typically defines what to achieve - the goals and drivers, and the metrics for success - but not how to get there. That is role of the Business Architecture. In other cases, little or no Business Architecture work may have been done to date. In such cases, there will be a need for the architecture team to research, verify, and gain buy-in to the key business objectives and processes that the architecture is to support. A key objective is to re-use existing material as much as possible. In architecturally more mature environments, there will be existing Architecture Definitions, which (hopefully) will have been maintained since the last architecture development cycle. Where architecture descriptions exist, these can be used as a starting point, and verified and updated if necessary. Gather and analyze only that information that allows informed decisions to be made relevant to the scope of this QlikView Architecture effort. 3.2.3.1 Templates 1. Enterprise Readiness FAQ[1].pdf 2. Enterprise Readiness Material.doc 3.2.4 Identify Initial Business Requirements Identify the initial requirements. The benefit of this is that you can answer fundamental business questions. QlikView development teams embrace change, accepting the idea that requirements will evolve throughout a project. They understand that because requirements evolve over time that any early investment in detailed documentation will only be wasted. Instead we will do in this phase just enough initial requirements envisioning to identify the scope and develop a high-level schedule and estimate; that’s all 25 © 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. qlikview.com
  26. 26. www.qlikview.com you really need early in a project, so that’s all you should do. During the execution phase the development team will model storm in a just-in-time manner to explore each requirement in the necessary detail. Like it or not, people are always going to ask you what the vision is for you're going to build (what's the scope), how long do you think it's going to take (the schedule), and how much is it going to cost (the expected budget). You often don't need to answer these questions in detail but you will need to convince the people who are funding and supporting your project that you understand the fundamental business issues that your project team is going to address. Benefits of initial requirements: • Improved productivity. o You can identify and think through some of the critical business issues facing your project. • Reduced business risk. o Your team gains the advantage of having a guiding business vision without the disadvantages associated with a Waterfall Approach. In this phase it’s about to drive to scope concurrence with your stakeholders, thereby reducing business risk, and the way that you do this is through initial requirements envisioning. Not only do you identify the scope of the effort, you also help to make the relevant stakeholders aware that there is a range of needs being met by QlikView, not just theirs, and that they are going to have to compromise sometimes. • Scaling QlikView development. o Your initial requirements model will be a key work product in any "QlikView at scale" efforts because it provides the business direction required by your overall architecture team for their initial architectural envisioning efforts (typically done in parallel with initial requirements modeling) and by sub-teams to define and guide their efforts within the overall project. 3.2.4.1 Templates 1. QlikView Requirements_Template.xls 2. Interview Business ManagerAnalyst_QPM Best Practice.doc 3. Interview Business_QPM Best Practice.doc 3.2.5 Identify Initial Data Requirements The definition of the Business Requirements determines the data needed to address business user’s requirements. Key Activities for defining Data Requirements are: • Define key business KPI’s & Drivers and their dimensionality. • Analyses of relevant Operational Source Systems. • Develop a source-to-target data mapping. 26 © 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. qlikview.com
  27. 27. www.qlikview.com 3.2.5.1 Templates 1. Interview Data_QPM Best Practice.doc 2. QlikView DataFlow Template.xls 3. QlikView Requirements_Template.xls 4. KPI Source_ QPM Template.xlsm 3.2.6 Create Architecture Vision The Architecture Vision provides the Enterprise Architects with a key tool to sell the benefits of the proposed QlikView capability to stakeholders and decision-makers within the enterprise. Architecture Vision describes how the new capability will meet the business goals and strategic objectives and address the stakeholder concerns when implemented. Clarifying and agreeing the purpose of the architecture effort is one of the key parts of this activity, and the purpose needs to be clearly reflected in the vision that is created. QlikView Architecture activities are undertaken with a specific purpose in mind - a specific set of business drivers that represent the return on investment for the stakeholders in the architecture development. Clarifying that purpose, and demonstrating how it will be achieved by the proposed architecture development, is the whole point of the Architecture Vision. Normally, key elements of the Architecture Vision - such as the enterprise mission, vision, strategy, and goals - have been documented as part of some wider business strategy or enterprise planning activity that has its own lifecycle within the enterprise. In such cases, the activity is concerned with verifying and understanding the documented business strategy and goals, and possibly bridging between the enterprise strategy and goals on the one hand, and the strategy and goals implicit within the current architecture reality. 3.2.7 Identify Key Considerations for Data Management When an enterprise has chosen to undertake large-scale QlikView roll-out, it is important to understand and address data management issues. A structured and comprehensive approach to data management enables the effective use of data to capitalize on its competitive advantages. Considerations include: • A clear definition of which application components in the customer’s landscape will serve as the system of record or reference for enterprise master data; • Will there be an enterprise-wide standard that all application components, need to adopt? • Clearly understand how data entities are utilized by business functions, processes, and services; • Clearly understand how and where enterprise data entities are created, stored, transported, and reported; • What is the level and complexity of data transformations required to support the information exchange needs between applications? 27 © 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. qlikview.com
  28. 28. www.qlikview.com • What will be the requirement for QlikView in supporting data integration with the enterprise's customers and suppliers (e.g., use of ETL tools during the data migration, data profiling tools to evaluate data quality, etc.)? 3.2.7.1 Templates 1. Data Source_QPM Checklist.doc 2. Data Staging_QPM Checklist.doc 3. DataModel Design _QPM Checklist.doc 3.2.8 Specify Infrastructure Requirements The objective of this milestone is set-up the hardware Sizing requirements for deploying QlikView to your users, together with its companion papers (QlikView Hardware Sizing, Administering a QlikView Hardware Sizing Exercise and QlikView Hardware Sizing IV: QlikView Hardware Sizing Worksheet) it provides the knowledge of what impacts QlikView performance and details the steps necessary to perform a hardware sizing exercise to help answer questions such as: • “Exactly how much of this specific dataset can I analyze on a server with these given characteristics?” • “How many concurrent users will this specific the server serving this specific QlikView application support?” • “If I want to support X number of users analyzing X amount of data from this specific dataset what type of server will I need?” The goal of QlikView hardware sizing is to answer these questions and more. In short it is to guarantee the performance of a given QlikView installation by ensuring that adequate hardware resources are available to QlikView as required by the amount of data to be analyzed, the characteristics of the data to be analyzed, the type of analysis preformed and number of the users to be supported. 3.2.8.1 Templates 1. QlikView Requirements_Template.xls 2. QlikView Sizing_checklist_.xls 3.2.9 Security Requirements QlikView applications often contain sensitive business information that should be accessible only to appropriate people within a company. Company performance, employee payroll, sales data, and forecast information are examples of company information that are commonly represented within QlikView applications. It is essential that security measures prevent unauthorized access to this information while allowing access for those who need it. QlikView provides robust means of securing data utilizing industry standard technologies such as encryption, access control mechanisms, and authentication methods. This activity describes how QlikView is deployed to the enterprise maintaining the confidentiality, integrity, and accessibility of our customer’s information. 28 © 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. qlikview.com
  29. 29. www.qlikview.com The purpose of this activity is to understand the requirements for various security features in QlikView, including: • Encryption • Authentication • Authorization 3.2.9.1 Templates 1. QlikView Requirements_Template.xls 3.2.10 Publisher Requirements QlikView Publisher is an add-on module to QlikView Server that provides control over the distribution of QlikView Documents to users. It includes an automated means of loading, distributing, and securing QlikView applications. It also allows administrators to reduce an application’s data set to a subset of data appropriate for subsets of users. The purpose of this activity is to describe the requirements for QlikView Publisher. 3.2.10.1 Templates 1. QlikView Requirements_Template.xls 3.2.11 Identify Outline QlikView Solution Scenario’s Prepare an outline solution to illustrate the feasibility of achieving the defined business requirements for the QlikView project. Outline the likely nature of the solution, and provide sufficient information for the preparation of a business case. • Describe different solutions in how to deliver the project outcome, if any. Use a SWOT model for each solution. • Preferred solution o Describe which of the alternatives to use and why this is the recommended approach.` • Internal and external dependencies o Specify the interfaces between this project and other projects, subprojects or assignments run within QlikView, that will have an impact on the outcome, e.g. new SW releases or larger change initiatives. 3.2.11.1 Templates 1. Pre-study Report_ QPM Template Rev 1.0 29 © 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. qlikview.com
  30. 30. www.qlikview.com 30 © 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. qlikview.com
  31. 31. www.qlikview.com 4. Phase 2: Planning Phase TG 1- TG 2 This is the phase in which the project is formalized, planned and preparations for successful project Execution and Implementation are made. • Input o The pre-study report, including any referenced documents • Activities (some major): o Formulize project goals and objectives and describe delimitations and scope, based on requirements o Organize the project and describe how the participants are to cooperate o Plan and budget the project o Risk Assessment o Describe how the project is to be followed up and concluded, and by whom • The purpose o To decide on a project strategy o To define the project goal o To prepare the project plans in order to provide a solid foundation for successful project Execution, Implementation and Completion • Output o Project plan 31 © 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. qlikview.com
  32. 32. www.qlikview.com o This is required to pass TG2 and move to the execution phase. 4.1 Project Management Planning 4.1.1 Update prioritize Business Requirements In the Pre-Study Phase the requirements where in initial format on the Enterprise level. In this phase the requirements must be (without going into much detail) further specified for specific parts of the organization (e.g. Marketing, Finance, Sales, HR, Operations,) be checked on feasibility and must be prioritized in line with the project goals. Business requirements define the future capabilities of QlikView to satisfy a legitimate business needs. QlikView Implementation success is based on a good understanding of the business users and their requirements. The QlikView Project Team must understand the key factors driving the business to effectively determine business requirements and translate them into design considerations. The first step of each cycle is to identify the business objective of the portion of the QlikView Application being elaborated. There are three types of interviews for collecting requirements. • Business Executive • Business Manager and/or analyst • Information System Data Specialist • Preparations before starting collecting requirements  Read company’s annual report  Copy of internal business plan  Website  Marketing Material  Begin talking with Business Users  Once you hear consistent themes from users it’s time to sit with Data Expert and you can match Business needs in with availability of data  Review Interview Results  Prepare and Publish Requirements Deliverables 4.1.1.1 Templates 1. QlikView Requirements_Template.xls 4.1.2 Estimate Requirements Developers are responsible for estimating the effort required to implement the requirements which they will work on. Although you may fear that developers don’t have the requisite estimating skills, and this is often true at first, the fact is that it doesn’t take long for people to get pretty good at estimating when they know that they’re going to have to live up to those estimates. 32 © 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. qlikview.com
  33. 33. www.qlikview.com Smaller requirements are easier to estimate. Shall statements, such as “QlikView shall convert feet to meters”, are an example of very small requirements. A good rule of thumb is that a requirement must be implementable within a single iteration. Short iterations reduce the feedback cycle making it easier to stay on track. Successful teams will deploy a working copy of their system at the end of each iteration into a demo environment where their potential stakeholders have access to it. This provides another opportunity for feedback, often generating new or improved requirements, and shows stakeholders that the team is making progress and thus their money is being invested wisely. 4.1.2.1 Templates 1. Project estimation worksheet.xlsx 4.1.3 Validate Project objective and Scope Review the latest statement of the Project Objective and Scope and ensure that it still accurately reflects the current status and plans for the project. • Review Project Objective and Scope o Conduct a review of the Objective statement and Scope definition to ensure the scope meets the business needs and all standards are met. 4.1.3.1 Templates 1. Project Plan Template Rev 1.0.dotx 4.1.4 Create Work Breakdown Structure Based on the results of the previous phase you can draw the work breakdown structure. This is necessary to clarify the project and its expected results. The most useful tool for accomplishing the task of estimating is the Work Breakdown Structure (WBS). The idea behind the WBS is simple: A complicated task is subdivided into several smaller tasks. This process can be continued until the task can no longer be subdivided, at which time you will probably find it easier to estimate how long each small task will take and how much it will cost to perform. 4.1.4.1 Templates 1. WBS_QPM Checklist.doc 4.1.5 Create App Work Packages A Work Package is a set of prioritized and estimated requirements for one or more required Applications collated by the Project Manager to pass responsibility for the execution phase formally to a member of the Development team. Define for each App which requirements are in scope. 33 © 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. qlikview.com
  34. 34. www.qlikview.com 4.1.5.1 Templates 1. Project Plan Template Rev 1.0.dotx 4.1.6 Determine Project Approach The purpose of the project approach is to provide an overall structure to the next phases of the project. Once the objective and scope are decided, it is necessary to determine the approach and what activities are required to be carried out to meet the objective. The dependencies between these activities can then be determined, which in turn allows resources and timescales to be estimated. This needs to be done in more detail for the next phase and on a high-level for the implementation phase. The ideal situation is to use the process as described in the execution phase, which is to base the tasks for this phase. This should then be customized to the particular needs of the project. Use the "Work Breakdown Structure” and add steps and tasks. One of the outputs of the next activity is a defined App demo date. That means you have to decide on a cycle length. So what is a good cycle length? Short cycles are good. They allow the enterprise to be “agile”, i.e. change direction often. Short cycles = short feedback cycle = more frequent deliveries = more frequent customer feedback = less time spent running in the wrong direction = learn and improve faster. Long cycles are good too. The team gets more time to build up momentum, they get more room to recover from problems and still make the cycle goal, you get less overhead in terms of cycle planning meetings and demos. Generally speaking users like short cycles and developers like long cycles. So cycle length is a compromise. In the past we experimented a lot with this and came up with our favorite length: 3 weeks. Most of our teams do 3 week cycle. Short enough to give us adequate corporate agility, long enough for the team to achieve flow and recover from problems that pop up in the cycle. One thing we have concluded is: do experiment with cycles lengths initially. Don’t waste too much time analyzing, just select a decent length and give it a shot for a cycle or two, then change length. 4.1.6.1 Templates 1. Project Plan Template Rev 1.0.dotx 4.1.7 Schedule Execution and Implementation phases The objective is to develop an overall time schedule for the rest of project, in a way that: 34 © 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. qlikview.com

×