Weekly Status Update Slide Template

Standard Operating Procedure: Weekly Status Reporting Protocol (WSRP)

1. Executive Summary & Purpose

The purpose of this SOP is to standardize the format, delivery, and data hygiene of weekly status updates across Template Registry. This ensures leadership maintains visibility into project health, resource allocation, and risk mitigation without the overhead of ad-hoc communication.

2. Scope & Prerequisites

• Scope: All internal engineering, product, and design team leads.
• Software Requirements: Template Registry Standard Deck (PowerPoint/Google Slides), Jira/Linear (for data pull), Slack (for dissemination).
• Prerequisites: Completed sprint velocity data, active project risk register, and verified milestone timelines.

3. Roles & Responsibilities (RACI)

4. Step-by-Step Procedure

Phase 1: Data Aggregation

• Extract raw sprint metrics from Jira (e.g., Velocity, Cycle Time).
• Identify top 3 "blockers" currently impacting the critical path.
• Verify milestone status against the master project roadmap.

Phase 2: Template Population

• Slide 1 (Overview): Summarize health using RAG status (Red/Amber/Green).
• Slide 2 (Execution): Bulleted list of completed items vs. planned items for the current week.
• Slide 3 (Risk/Blockers): Mandatory inclusion of escalation points requiring external intervention.
• Slide 4 (Next Steps): Primary objectives for the upcoming 5-day cycle.

Phase 3: Review & Distribution

• Perform "Self-Audit": Ensure no bullet point exceeds 15 words.
• Verify data consistency (Ensure slide dates match current reporting week).
• Export to PDF for final distribution via the designated #status-updates Slack channel.

5. Quality Assurance & Pro-Tips

• The 10-Minute Rule: If building the deck takes >10 minutes, the data is too manual. Automate the Jira-to-Slide pipeline using registry-approved plugins.
• RAG Calibration:
  • Green: All deliverables on schedule; no significant risk.
  • Amber: Off track but manageable with current resource allocation.
  • Red: Project objectives at risk; requires immediate executive intervention.
• Common Pitfall: Avoiding "fluff" adjectives (e.g., "doing great," "moving fast"). Use empirical evidence (e.g., "92% test coverage," "Deployment time reduced by 14%").

6. Frequently Asked Questions (FAQ)

Q: Can I use personal formatting for my team’s slides?

• A: No. Institutional consistency is required to allow stakeholders to parse data rapidly. Deviations will be rejected during the QA phase.

Q: What if I don't have any blockers this week?

• A: State "None identified" under the "Blockers" section. Do not omit the section; omission signals a lack of oversight.

Authorized by: Julian Vance Chief Architect, Template Registry