← Command Centre

Jira Data Quality Report

Initiative Portfolio Assessment

Report Date: April 28, 2026 | Assessment Period: April 10 - April 24, 2026

Overall Data Quality Score

76%
199 of 261 data quality checks passing across 26 initiatives
Total Initiatives
26
Ranked Bets
7
Unranked
7
Parked
12

Legend: Data Quality Checks

OKR Set - OKR field contains value
Outcome Articulated - Expected outcome is documented
Health Tracked - RAG status is not Gray
Status Current - Last updated within 14 days
Owner Named - Product Owner is assigned

Initiative Data Quality Scorecard

How to read this table: Each initiative is scored 5/5 if all data quality checks pass. Scroll right to see detailed check status. The "Responsible" column indicates who needs to fix each data gap. Green (5/5) = excellent data quality; Amber (3-4/5) = attention needed; Red (0-2/5) = urgent remediation required.
Initiative Score OKR Outcome Health Status Current Owner Responsible for Gaps

Remediation Priority

Fix Ranked Bets First

  1. PM-749 (CDP Phase 1) - Score 2/5 - Critical: Missing OKR, outcome, and product owner. Assign PO immediately and set objectives in Jira.
  2. PM-80 (Cloud Cost Optimisation) - Score 4/5 - Engineering Manager (Anas Semesmieh) to update health status and last-updated date.
  3. PM-562 (PayTo Phase 1) - Score 4/5 - Engineering Manager (Adrian Chew Kah Hoong) to set RAG status to tracked (not Gray).

What to Fix in Jira

1. Setting OKR Field

  1. Open the initiative in Jira
  2. Navigate to Plans board → Initiative detail view
  3. Find the custom field "OKR" (or "Strategic Objective")
  4. Enter a clear, measurable objective (e.g., "Increase cloud efficiency by 30%" or "Complete Phase 1 by Q2 2026")
  5. Save and verify it appears in the portfolio report refresh

2. Setting Expected Outcome

  1. Open the initiative in Jira
  2. Find the custom field "Expected Outcome" or "Business Outcome"
  3. Describe the business impact (e.g., "Reduce infrastructure costs by $200K annually" or "Enable 50% faster transaction processing")
  4. Save changes

3. Updating RAG Status (Health Tracking)

  1. Open the initiative in Jira
  2. Find the "RAG Status" or "Health" field
  3. Set to one of: Green, Amber, or Red
  4. Do NOT leave as Gray or blank (indicates no tracking)
  5. Add a brief reason in "RAG Reason" field (e.g., "On track, dependencies resolved")
  6. Save immediately

4. Updating Status (Mark as Current)

  1. Open the initiative in Jira
  2. Make any edit (e.g., update status, add comment, or refresh RAG status)
  3. The "Last Updated" timestamp will auto-update to today
  4. Aim to update initiatives at least every 14 days during active work
  5. For parked initiatives, set status to "Parked" with expected revisit date

5. Assigning Product Owner

  1. Open the initiative in Jira
  2. Find the "Product Owner" field
  3. Search and select the responsible product owner from your team
  4. Save — this is non-negotiable for all initiatives

6. For Stale or Parked Initiatives

  1. If an initiative has not been updated in 14+ days, review its status
  2. If work is paused: Set status to "Parked" and document "Reason Parked" and "Revisit Date"
  3. If work is complete: Set status to "Done" and document outcomes achieved
  4. If work continues: Update RAG status and hit Save to refresh the timestamp

Who to Chase

The following people own gaps across multiple initiatives. Prioritize conversations with those managing the most remediation work:

Quick Wins

Highest Impact Actions (next 48 hours):

  1. Assign Product Owner to PM-749 (CDP Phase 1) — currently unassigned, affects ranked bet credibility
  2. Update RAG status for Adrian Chew Kah Hoong's 6 initiatives with Health gaps — most straightforward to fix
  3. Refresh last-updated timestamps for stale initiatives (14+ days old) — a simple save will suffice