Weekly Status Report Dashboard Template

Standard Operating Procedure: Weekly Status Report (WSR) Dashboard

Document Control Block

• Document ID: TR-OPS-WSR-001
• Effective Date: 2023-10-27
• Version: 1.0.0
• Review Cadence: Quarterly (or upon major schema changes)

1. Executive Summary & Purpose

The purpose of this SOP is to standardize the generation of Weekly Status Report (WSR) dashboards across Template Registry engineering squads. This process ensures data consistency, cross-departmental visibility, and immediate identification of project slippage or resource bottlenecks.

2. Scope & Prerequisites

• Scope: All technical project leads, engineering managers, and product owners.
• Tools: Jira (Project Management), Confluence (Reporting Hub), Tableau/PowerBI (Visualization Layer).
• Prerequisites: Validated Jira API key, access to the Master Project Board, read/write access to the Corporate Dashboard Repository.

3. Roles & Responsibilities (RACI Matrix)

4. Step-by-Step Procedure

Phase I: Data Extraction & Validation

• Sync Jira Sprint status to current WSR_SCHEMA_V1.
• Validate that all tickets in the "In Progress" column contain updated Story Points and Blocked flags.
• Export raw JSON payload to the Registry-Analytics staging environment.

Phase II: Dashboard Assembly

• Open the Template Registry Master Dashboard template.
• Update the Data Source path to the current week’s Export_ID.
• Refresh data connectors and verify successful handshake.
• Audit the Velocity vs. Capacity graph for anomalous variance (>15%).

Phase III: Review & Sign-off

• Annotate high-impact risks in the Risks/Blockers component.
• Perform a "sanity check" of the Burn-down chart against actual code deployments.
• Publish to the Executive Confluence portal and trigger notification webhooks.

5. Quality Assurance & Pro-Tips

• Metric Thresholds:
  • Scope Creep: Any addition of >5% story points mid-sprint must be highlighted in red.
  • Blocked Time: Any ticket in "Blocked" status > 48 hours requires a mandatory status update comment from the assigned owner.
• Pro-Tips:
  • Automation: Use the Jira API to pull stats directly into the dashboard to eliminate manual entry errors.
  • Context: Data without context is noise. Always include the "Why" behind a deviation in the Executive Notes section.
• Common Pitfalls: Forgetting to close completed sub-tasks, which artificially inflates the "Work Remaining" metric.

6. Frequently Asked Questions (FAQ)

Q: The dashboard shows a discrepancy between Jira and the report. What is the cause? A: This is typically a cache latency issue. Force a manual refresh of the Tableau data source and verify that all Jira filters include the current Sprint ID.

Q: Can I modify the dashboard layout to fit my team’s specific needs? A: No. Standardized reporting is required for cross-team aggregation. If a specific metric is missing, submit a formal request via the Dashboard-Expansion JIRA ticket template.

Julian Vance Chief Architect | Template Registry