Qlik App
Project Management Document
People Cost & Productivity
Document Author – Adrian Worrall
1st December, 2018
Page 1 of 6
Table of Contents
1 Document Revisions............................................................................................................... 3
2 Project Management Methodology......................................................................................... 4
3 Project Stages........................................................................................................................ 5
3.1 User Requirements........................................................................................................................5
3.2 Due Diligence.................................................................................................................................5
3.3 Build...............................................................................................................................................5
3.4 User Acceptance Testing................................................................................................................5
3.5 Deploy............................................................................................................................................5
3.6 Maintain.........................................................................................................................................5
Page 2 of 6
Document Revisions
Version
Date Document Changes
Number
1 Dec 2018 1.0 Initial Draft
Page 3 of 6
Project Management Methodology
Qlik apps are developed using an Agile project management framework.
This collaborative approach involves delivery of requirements, based on an iterative approach. See
section 3 for individual stage details.
Page 4 of 6
Project Stages
User Requirements
This section defines;
1. Who the audience is [Who]
2. What are they trying to understand [What]
3. Is something already reported & what systems are used to record the data [Where]
4. How frequently do they want to use the data [When]
Due Diligence
At this stage you look to define [How];
What are the current repositories of data (systems, spreadsheets, internet, etc.)
Can we connect directly to those systems (connection strings and access rights)
If so what are the table and field names that contain the required data
Are there any other systems / tables / external data that may aid additional insights
What is the condition of the data (notify data owner if cleanse required / desirable)
Document the entity relationship model
Build
1. Construct the basic load script
2. Design the basic visuals & tables
3. Validate the outputs
4. Consider developer added value – additional insight visuals etc.
5. Add security, once initial testing of functionality completed
User Acceptance Testing
Does the constructed prototype app meet the user requirements?
Document the build
o Annotate script
o Document any set analysis used
o Tip: these can be done quickly and easily using screen recording software
Deploy
Add app to live environment, schedule and add any additional security requirements.
Publish via peer review / change control process document, based on sign off of;
o User acceptance testing
o Entity relationship model
o Script annotation & set analysis documentation
Page 5 of 6
Maintain
Ensure data stewardship rules are clearly defined and understood. As a general rule the data owner
should be the domain of the end user (unless a central function is available).
It is their responsibility to identify and correct any data anomalies.
Page 6 of 6
