Summary
KTS follows a simple scoping process for reporting and dashboard work to keep requests practical and avoid rework. This article walks through the stages so you know what to expect.
Who this is for
Customers who are about to raise, or have already raised, a reporting request through KTS IaaS.
The stages
-
Intake — You describe the decision you want to support and the audience.
-
Data check — KTS confirms the data source exists, is reachable, and is accurate enough to support the question.
-
Scope agreement — KTS proposes what version one of the dashboard will include, and what is out of scope for now.
-
Build — KTS builds the first draft in Metabase.
-
Review — You look at the draft with KTS and give feedback.
-
Handover — The dashboard is published to the right Metabase collection and documented.
What keeps a request moving
-
A clear owner on the customer side who can answer questions
-
Agreement on one main question the dashboard should answer
-
Willingness to start with a smaller version rather than waiting for a perfect one
-
Access to the underlying data source being confirmed early
What slows a request down
-
Too many contributors with different views on what the dashboard should do
-
Requests to change the data at the source, which is a separate project
-
Unclear data in the source system, which needs tidying before reporting on
-
Changing scope after build has started
What KTS may need from you
-
A named owner or point of contact
-
Access to or details of the data source
-
Sample outputs or mockups if available
-
Clarification questions answered within a reasonable time
When to contact the service desk
Contact the service desk when you want to start, change, or close a reporting request.