I5 (2 points)
https://knobit.org/id/task/dg-strategy-scorecard-trace/I5
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/dg-strategy-scorecard-trace/I5 |
| rdfs:label | I5 (2 points) en |
| schema:hasPart | dg-strategy-scorecard-trace I5: glossary terms owned and approved by governance, not the modelling team |
| schema:hasPart | dg-strategy-scorecard-trace I5: the Council approves models and standards, architecture applies them |
| schema:hasPart | dg-strategy-scorecard-trace I5: a glossary and a workflow tool instead of a personal workbook and a mailbox |
| schema:hasPart | dg-strategy-scorecard-trace I5: governance continues and is embedded after 2027 |
| schema:identifier | I5 |
| schema:position | 8 |
| schema:text | Decision rights, tools and staying power, 0.5 each. (a) T-1 to T-3 are approved by the Data Architecture team in its modelling tool and have no owner: governance assigns each term an owner (the CRO or the Retail lending data owner) who approves the definition, with the Council for disputes; the modellers may draft and reuse it. (b) The Architecture Review Board approves data models and standards and the Council is only informed: the Council approves data standards and the business content of models; architecture applies them, with joint design review. (c) The tooling is a personal Excel workbook and a mailbox: a governance toolset proposed - at least a shared business glossary and a workflow for issues and decisions (a published scorecard and an intranet home for policies are further parts). (d) After 2027 the Council is dissolved and the DMO returns to IT: governance is a standing function, not a project - the Council and the DMO continue (possibly at a lower cadence) and steward duties are embedded in job descriptions and business processes. en |