Duration: 4–6 weeks · Exit criterion: The sponsor and the council approve the roadmap and the priority use cases.
Measure the gaps against a target governance framework on eight dimensions, choose the priority domains, describe concrete use cases and agree a data governance roadmap with the sponsor and the council.
Data Governance Lead
Council
Data Owners of the candidate domains
Data Stewards
IT, architecture and security
DPO and legal
PMO
Dimension | Key questions | Output | Status / gaps |
|---|---|---|---|
Governance framework | Is the framework clear, understood and followed? · Is the organisation structured? What are the gaps? · Which documents exist: policy, standard, guideline, procedure? · What is the draft – review – approve – publish flow, and which software supports it? | Gaps; target framework and operating model | [to fill] |
Data catalogue | What are the domains? What are the terms and their hierarchy? · Who creates domains and terms, with which flow? · Which software is used? | Gaps; priority domains; catalogue use case | [to fill] |
Data quality | How is quality defined and measured? · Are there quality standards? Who defines them, with which process? · How are bugs and quality incidents reported? | Gaps; priority domains; quality use case | [to fill] |
Data projects | How are projects managed (agile method)? · What is the current roadmap, how and when is it defined? · Who decides the priorities, and how? | Project structure for phase 3 | [to fill] |
Legal and ethics | Which legal constraints apply? Are the controls in place? · What is missing? Who decides? | Gaps and risks; priority use case | [to fill] |
Security | How is physical security managed, and by whom? · How are data access rights defined, and by whom? · How is data classified, and by whom? | Gaps and risks; priority use case | [to fill] |
Data architecture | Which databases exist, and who manages them? · Who has access? Who manages the table structures? · How are the physical structures linked to the semantic layer (catalogue)? | Gaps; lineage and mapping needs | [to fill] |
People | Who are the data owners and data managers? Do they have a job description? · What are their training and coaching needs? | Training and coaching plan | [to fill] |
Code | Deliverable | Content | Link | Status |
|---|---|---|---|---|
D2.1 | Gap assessment | Maturity and gaps per dimension, with evidence from phase 1. | [link] | To do |
D2.2 | Risk register | Legal, ethical and security risks, with owner and proposed treatment. | [link] | To do |
D2.3 | Priority domains and use cases | One use case card per priority (business question, data, owner, value, risk, KPI). | [link] | To do |
D2.4 | Data governance roadmap | Target framework and a 12 to 18-month roadmap, by quarter. | [link] | To do |
D2.5 | Roadmap decision | Presentation to the sponsor and the council; go decision for phase 3. | [link] | To do |
Activity | Consultant | Sponsor | DG Lead | Council / PRB | Data Owners | Data Stewards | IT & Security | DPO / Legal | PMO |
|---|---|---|---|---|---|---|---|---|---|
Assess framework and organisation | R | – | A | C | C | – | – | – | – |
Assess catalogue, quality and architecture | R | – | A | – | C | C | C | – | – |
Assess legal, ethics and security; build the risk register | R | – | A | I | – | – | C | C | – |
Assess projects and people | R | – | A | – | C | C | – | – | C |
Select priority domains and write the use cases | R | – | R | A | C | C | – | – | – |
Build the roadmap and target framework | R | C | A | C | – | – | – | – | C |
Approve the roadmap | C | A | R | R | – | – | – | – | I |
R = Responsible · A = Accountable (one per activity) · C = Consulted · I = Informed