Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Page Contents:

  • Description
  • Scope
  • User Journey
  • Scenarios
  • Field Validation
  • Related JIRA ticket links
  • For Discussion & Assumptions
  • Agreed Next Steps


Description

The ability to extract data from TIS and to use extracted data for analysis

Component: TIS-646


Scope

Access Reporting Tool

View Dashboard (TBC)

See here for discussion notes



User Journey


JIRA Tickets

https://hee-tis.atlassian.net/secure/RapidBoard.jspa?rapidView=13&projectKey=TIS&view=planning&selectedIssue=TIS-646&quickFilter=69&selectedVersion=11700


Discussion & Assumptions

#QuestionCommentOwner
1
  • Confirmation that there is nothing currently delivered by Intrepid?

Joanne Watson (Unlicensed) - My understanding is that there are Standard reports and availability of Report Builder within Intrepid. Not 100% sure, but have previously heard of Power BI tool also. Can you please confirm?

YesJoanne Watson (Unlicensed)
2
  • What’s the expectation from a delivery perspective?
See here
3
  • should reports be customisable or standard?
Both; but accessible in different ways by different user sets (outside of TIS)
4There are currently Standard Reports available in Intrepid. Is there an expectation that the proposed reporting solution that will be available to access within TIS would have those standard reports available? If so, who will be responsible for delivering those if not the TIS team?
Joanne Watson (Unlicensed)
5What are the MVP reporting requirements?
Joanne Watson (Unlicensed)
6Which of the Local teams uses reporting?Apprears to be the following: HETV, HEW, HEYH, HENW, & HENE.Joanne Watson (Unlicensed)

Agreed Next Steps

  • Obtain sample list of standard reports (AP)
  • Arrange configuration of standard reports within SSRS (RH)
  • Write up scenarios in detail
  • Specify field validation changes & rules
  • Refine stories to reflect user journey, scenarios and field validation
  • validate with SMLs
  • No labels