Working with the DQR List

Learning Objectives

By the end of this lesson you will be able to:

• Complete a DQR form for a given data quality issue
• Use the DQR list to assess migration readiness
• Interpret DQR metrics and traffic-light reporting

The DQR Form in Detail

Each DQR item is documented on a standard form. Working through the DHGS example of DQR0004 (Product Price Consistency):

Header fields:

• DQR ID: DQR0004
• Short Name: Product Price Consistency
• Cross Ref: DQR0002 (the preceding DQR that revealed the issue)
• Raised by: Johny Morris
• LDS/Entity: FSDB; Kelsey Pit; Pebbles
• Date Raised: 01/01/01
• Priority: Business 1, Technical 1
• Status: O (Open)

Data Quality Assessment:

• Description: DQR0002 revealed that the same product is being charged at different prices in different systems
• Qualitative Assessment: No more than 20 products are believed to be affected
• Quantitative Assessment: DQR tasks will generate an agreed count of affected records

Method Statement: First quantify the records, then facilitate agreement on a fix approach (consolidate on one price list, or retain variants).

Sub-tasks (each with owner and target date):

1. Put on Issues/Risks log to alert seniors (JM, 10/01)
2. Each BDE produces a product list from their LDS (WB, JH, RC, 10/01)
3. Facilitated meeting to agree matches and highlight price conflicts (WB, JH, RC, JM, 15/01)
4. Raise DQR0011 to carry forward the single-view-of-product work (JM)
5. Schedule meetings with seniors on the findings (JM, 20/01)
6. Following business decision, implement fix (28/02)

Metrics: 5% complete after Task 1; 15% after Task 2; 40% after Task 3; 45% after Task 5; 100% after Task 6.

The DQR Process Sequence

The standard process sequence for a DQR item:

1. Find - issue discovered (profiling, mapping, testing, LA)
2. Raise - DQR form created with initial description
3. Quantify - number of affected records, percentage of total, business impact assessed
4. Board - brought to the DQR Board for prioritisation
5. Plan - sub-tasks defined with owners and dates
6. Manage - progress tracked against sub-tasks
7. Complete - DQR closed when metrics show 100% resolution
8. (Optional) Escalate - unresolvable issues escalated to programme management

Migration Readiness Metrics

The DQR repository provides the primary data for migration readiness assessment. Key metrics reported by the DQR Board:

• Total open DQR by priority - how many Priority 1 (blockers) are still open?
• Late-running DQR - items past their target completion date (traffic-lit red/amber/green)
• Completion % by KBDA - what percentage of the Customer data is migration-ready?
• Record count - of the total records in scope, how many currently pass all validation?

These metrics feed the migration readiness dashboard and the go/no-go decision for each migration run.

The Traffic Light System

DQR items are traffic-lit for programme visibility:

• Green: On track, completing on time
• Amber: At risk, may require intervention
• Red: Late or blocked, escalation required

The traffic light is based on completion date vs. the date the records need to be ready for the next migration run. A DQR that is amber today may be manageable; the same DQR still amber the week before the migration run is a programme risk.

DQR in the DHGS Case Study

The DHGS DQR list includes:

• DQR0004 - Product price inconsistency across systems (resolved by consolidating price lists)
• DQR0012 - Equipment type codes need standardisation (537 Kelsey Pit equipment types, 200 found equivalent; BDEs create cross-reference table)

DQR0012 illustrates a common pattern: the issue is too large for one person to resolve, requires subject matter experts from the business, and takes weeks to complete. The DQR process provides the structure to manage this without it becoming an uncontrolled open issue.

Format note: this inline “foldout” is the go-forward standard for course artefacts (approved 16 Jun 2026) - the worked artefact is shown in the lesson, expandable, instead of attached as a handout; an optional download is kept only for genuine fill-in templates. See pdm-website/DESIGN.md §8 and pdm-course/ARTEFACTS_INVENTORY.md.

Key Takeaways

• Each DQR form captures header, assessment, method statement, sub-tasks, and metrics
• The standard process sequence: Find → Raise → Quantify → Board → Plan → Manage → Complete
• Migration readiness is assessed from DQR metrics: open Priority 1 items, late-running items, record completion percentages
• Traffic lighting gives programme visibility into DQR status relative to migration run dates

Book Reference

Practical Data Migration by Johny Morris (BCS, The Chartered Institute for IT):

• Chapter 05 - Introducing DQR