8 — Reconstruction Key, Completion Rubric & Source Notes
← Independent Rebuild & Debrief · Lab Home · Chapter 1 Evidence Checklist
✅ Use this only after attempting the eight closed-book debrief questions. Your Meridian-specific examples can differ if they stay consistent with the Casebook and Chapter 1.
Reconstruction / answer key
1. Why is the customer issue a Data Management problem before choosing a system?
The issue spans definitions, representation, quality, enterprise reuse, risk, lifecycle, and cross-functional decisions. Choosing a database does not resolve business meaning, stewardship, quality, or appropriate use.
2. Why isn't a list of tables enough for an asset inventory?
Data is abstract and context-dependent. Knowing a table exists does not explain why the data exists, what it means, who depends on it, how valuable it is, what risks attach to it, or how it should be managed.
3. How is data unlike a physical asset?
The same data can be reused, copied, shared, and used by many people without being consumed; value depends on use and context. Replacement difficulty and risk can be high even though there is no physical object to wear out.
4. Lifecycle vs lineage
Lifecycle describes management stages/events across the asset's life. Lineage follows a particular data set from origin through movement/transformation to use. Example: customer lifecycle includes definition/capture/use/maintenance/disposal; customer lineage traces CRM/POS/SERV through transformations to a report or master view.
5. Requirement before technology
Examples include defining “active customer” before selecting master-data technology; defining KPI meaning/traceability requirements before catalog/BI tooling; or deciding least-privilege business need before configuring roles.
6. Charter vs Scope Statement vs Roadmap
The Charter sets mandate, vision, business case, and overall intent. The Scope Statement defines planning-horizon boundaries, goals, and accountability. The Roadmap sequences initiatives/projects/milestones used to implement the direction.
7. Why isn't Data Governance the same as all Data Management?
Governance coordinates direction, decision rights, policy, and oversight across the discipline. Architecture, Modeling, Storage, Security, Integration, Content, Master/Reference, Warehousing/BI, Metadata, and Quality remain distinct work.
8. Acquisition reprioritization
A defensible answer connects the acquisition to enterprise perspective, planning, lifecycle/risk, Metadata/quality, or leadership commitment. The key is explaining why a changed business situation changes Data Management priorities.
Completion rubric
| Dimension | Not yet | Working | Complete for Sequences 021–022 |
|---|---|---|---|
| DMBOK explanation | Names terms but cannot explain business reason | Explains most concepts with prompting | Explains asset/value, lifecycle, Metadata/quality, enterprise perspective, strategy, and business-first technology decisions in DAMA-aligned language |
| Applied reasoning | Copies template or ranks without reasons | Completes work with basic reasons | Uses process, consumer, value, risk, lifecycle, and context evidence to justify priorities |
| Technology independence | Names a tool before requirement | Usually states requirement first | Explains why a tool supports—but does not define—the Data Management requirement |
| Transfer | Handles only original case | Responds to acquisition with prompting | Reprioritizes coherently when facts change and explains which Chapter 1 principles drove the change |
| Evidence | Missing or screenshot-only | Artifacts exist but rationale is thin | Artifacts + decisions + reasoning are inspectable and linked |
✅ DONE WHEN: You can justify Meridian's Data Management priorities without the template, explain why the work is broader than IT administration, and translate every major output back into Chapter 1 terminology.
Current 00C handoff
- The Chapter 1 Meridian lab is entered through Sequence 021 — plan and prediction and Sequence 022 — execute, vary and prove.
- After the lab completion gate passes, return to Sequence 023 — Chapter 1 DMBOK debrief, error repair and spaced revisit.
- Record only actual misconceptions or weak patterns for Sequence 023 repair; do not pre-fill generic Chapter 1 errors.
Source and implementation notes
- Controlling DAMA source: DAMA-DMBOK2 Revised, Chapter 1: Data Management, pp. 19–49. This lab paraphrases the chapter; it does not create new DAMA rules.
- Meridian source: Meridian Commerce Group — Enterprise Data Management Casebook, especially company profile, processes, systems, data domains, and MCG-001 through MCG-012.
- The High/Medium/Low prioritization method, acquisition change-fact, specific evidence filenames, and training-scale templates are Meridian instructional designs, not DAMA-prescribed formats.
- No SQL/Python/PostgreSQL competence is required for Chapter 1 Sequences 021–022.
- If the lab exposes a real misconception, record it for Sequence 023 Error Repair. Do not pre-fill generic Chapter 1 repair material.