Project Governance at our Heart 

Projects can be tailored to be as light touch as the client requires.  

 

Below is the approach / framwork template QlickXL uses as standard.

Project Management Methodology

QlickXL Agile Framework Lifecycle

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.
 

Project Stages 

User Requirements

This section defines;

  1. Who the audience is [Who]
  2. What are they trying to achieve / 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 app/data and do they want any automated reporting outputs [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
    • Annotate script
    • Document any set analysis used
    • 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, based on sign off of;
    • User acceptance testing
    • Entity relationship model (development team internal sign off)
    • Script annotation & set analysis documentation (development team internal sign off)

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.

 

For any enhancements to the original scope, the cycle is simply repeated, where applicable.

QlickXL Limited

© QlickXL Limited. All rights reserved.

We need your consent to load the translations

We use a third-party service to translate the website content that may collect data about your activity. Please review the details in the privacy policy and accept the service to view the translations.