I4 (2 points)
https://knobit.org/id/task/dg-strategy-scorecard-trace/I4
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/I4 |
| rdfs:label | I4 (2 points) en |
| schema:hasPart | dg-strategy-scorecard-trace I4: IN-102 valued by the risk it avoids, not by revenue |
| schema:hasPart | dg-strategy-scorecard-trace I4: readiness assessed on maturity, capacity, collaboration and alignment |
| schema:hasPart | dg-strategy-scorecard-trace I4: governance acts in the CRM procurement and the SDLC, not after go-live |
| schema:hasPart | dg-strategy-scorecard-trace I4: rollout with a sponsor, training and communication |
| schema:identifier | I4 |
| schema:position | 7 |
| schema:text | Making the case and the change, 0.5 each. (a) IN-102 is valued at EUR 0 because it earns no revenue and recommended for deferral: valued instead by the risk it avoids (supervisory findings carried over, misstated exposures in the Board report, manual adjustment effort) and not deferred on the revenue argument - any deferral left to the Steering Committee. (b) Readiness is judged by counting the policies written: assessed instead on data management maturity, capacity to change, collaborative readiness and alignment with the business (at least three named). (c) IN-104's governance involvement starts after go-live: governance acts in procurement (data clauses in the vendor contract - ownership, quality obligations, export at exit) and in the build (data model and design review, data acceptance criteria as an SDLC gate) - both needed. (d) The rollout is one e-mail with no training and no sponsor: a sponsor named (the Steering Committee chair, the COO), role-based training for owners and stewards, and communication beyond one message. en |