Reset Search
 
Article

healthstat.be - Reports - Business Process - Project Phase

« Go Back

Support article

 
Last Modified Date11/16/2017 6:07 PM
SummaryThe article describes the requirements of healthstat.be reports for monitoring projects by healthdata.be.
Content

1. Introduction

The article explains the requirements of a report about the status of projects managed by healthdata.be (HD.be).This document includes 4 points:

2. Project METRICS

The aim of the Metrics project is to develop a data driven approach for steering all activities of HD.be. Currently, that implies the assessment of metrics grouped in 6 categories:

  1. Business Processes;
  2. External Interfaces Availability;
  3. Data Collection;
  4. Operations;
  5. Information Architecture and Terminology;
  6. Data Warehouse.
Each metrics category concerns a specific sub-project within the Metrics project. This document deals only with the Business Processes (BP) category. It focuses of status of projects by HD.be.

2. Project Management within healthdata.be


  

Healthdata.be manages projects using 8 phases listed below:

  1. Request;
  2. Define;
  3. Propose;
  4. Build
  5. Test;
  6. Deploy;
  7. Run;
  8. Evaluate.
The  project management is implemented within a software tool named JIRA. Each phase of projects implies several tasks, sub-tasks or documents. Each issue related a project should be recorded in JIRA regarding the 7 phases previously described.
The phase 4 to 7 contains 3 sub-categories named:
  • Data Collection : data capture
  • DWH Exploitation : data management;
  • DWH External(reporting): data reporting.

3. Dataset used for the reporting

The data linked to the implementation of Business Processes for managing HD.be projects in JIRA are hosted in a cloud. An Extraction Transformation Loading (ETL) procedure has been designed to get these data named JIRA_DATASET. The structure of the JIRA_DATASET is shown in the Table 1. Each record fetched from JIRA_ DATASET corresponds to a task, a subtask or an EPIC in JIRA.

Table 1 : : Description of the JIRA dataset by displaying : VARIABLE NAME, FUNCTIONAL DESCRIPTION and FUNCTIONAL NAME

VARIABLE NAMEFUNCTIONAL DESCRIPTIONFUNCTIONAL NAME
DT_FETCHINGDate of fetching of JIRA_DATASETEXTRACTION DATE
TX_PROJ Fully name of the project (to validate with the planning sheet)PROJECT NAME
TX_KEY Unique identification of a ticket in JIRAJIRA IDENTIFCATION
TX_ISSUE_TYPE* Define the ticket being a task or document, that impact the possible values of the field TX_STATUSTASK TYPE
TX_SUMMARY Title of the ticket, i.e. the task or documentTASK SUMMARY
TX_STATUS* If TX_ISSUE_TYPE is task or sub-task, then TX_STATUS possible values are TO DO, IN PROGRESS, DONE, CANCELLED  and TX_ISSUE_TYPE takes value Document, it can be TO DO, IN PROGRESS, IN REVIEW, SUBMITTED, APPROVE, ARCHIVE, DONE, CANCELLEDSTATUS
TX_ASSIGN Responsible of the taskTASK ASSIGNEE
DT_DATE_DUE The deadline of the ticketDUE DATE
TX_MAND Define whether a task is mandatoryMANDATORY
TX_PHAS The name of the corresponding phase of the EPIC (01 = Request ; 02 = Approval ; 03=Define, 04=Build ; 05=Test; 06=Deploy; 07=Run; 08=EvaluatePHASE
TX_PRIOR Priority of the task with 3 levels : ‘High’, ‘Medium’, ‘Low’PRIORITY
TX_REPORT Reporter of the task completed for all fields, not really in useà to be deletedREPORTER
TX_TSK_ID Task id from wiki BPTASK IDENTIFICATION
TX_TRACK The track code which contains the possible values from A1 to A4, B1 to B3PROJECT TYPE
TX_WAVEFor The 8 wave of HD projects : WAVE 1 (2014-2015), WAVE 2 (2015-2016), WAVE 3 (2016-2017), WAVE 4 (2017-2018), WAVE 5 (2018-2019), WAVE 6 (2019-2020), WAVE 7 (2020-2021), Wave:Cancelled, Wave : TBD 
WAVE
TX_SERVICEThe service provided by HD extracted of a list containing 4 values : ‘None’, ‘Data Collection’, ‘DWH Exploitation’, ‘DWH External (reporting)’SERVICE
TX_PRIVATEField to specify whether the project is private or publicPRIVACY
TX_SPONSORField to specify the project funderSPONSOR
TX_COMMISSIONERField to specify the project requesterCOMMISSIONNER

A dummy JIRA_DATASET is chown in Table 2.
 

Table 2 : description of the JIRA_DATASET : yellow (issues of the first project) and green (issues of the second project), the variables used for the calculations performed far in the document are outlined with a white background in the below table: (D_FETCHING, TX_PROJ, TX_STATUS, TX_MAND, TX_PHAS, TX_TRACK, TX_PHASE, TX_TASK, TX_SERVICE, TX_WAVE)



 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255