Skip to content
The title slide and first slides of the Defect Status Slides template

Defect Status Slides

Presentation template for Google Slides and PowerPoint

Make a copy in Google Slides
Price
Free
Slides
11
Style
Minimal
Difficulty
Beginner
Updated
November 12, 2026

Every slide (11)

Overview

A release meeting goes badly when the team argues from memory about which bugs are still open and how serious they are. This deck gives the team one short run through the defects: counts by severity, the trend across the sprint, the blockers with their owners and the risk to the ship date. Each slide answers one question, and every number traces back to the triage export.

The sample is for Larkspur Software, a fictional software company preparing build 8.4.2 (1,284). It shows 11 open defects, none of them critical, two high and nine medium, with a 4% escape rate. Replace the counts, severities, owners and dates with figures from your own tracker, and keep the severity definitions visible so nobody ranks a defect by how loudly it was reported.

Useful for

  • A release meeting that must decide whether two high defects block the ship
  • A weekly triage review where the QA manager reports open counts
  • A product owner asking which defects affect customers this week

What's included

  • Slide 1: cover with the release title and the review date
  • Slides 2 to 4: defects open by severity, the severity rules and the trend
  • Slides 5 and 6: the weekly trend chart with insights and the blockers table
  • Slide 7: what must happen before release, with owners and dates
  • Slides 8 and 9: a release timeline and the risks that could delay it
  • Slides 10 and 11: a guide to writing a bug report, and contacts

How to use it

  1. 1

    Click Make a copy in Google Slides, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Replace the counts, severities and dates on slides 2 and 6 with your own tracker export.

  3. 3

    Update the blockers table on slide 6 so every high defect has an owner and a status.

  4. 4

    Keep the severity rules on slide 3 visible, and set each defect's severity by user impact.

  5. 5

    Delete the guide slide, then share the deck with the release team or present it from Google Slides.

What you need

Requirements

  • A Google account with access to Google Slides

Works with

  • Google Slides
  • Microsoft PowerPoint (File → Download → .pptx)

Questions

Are the company, people and figures in this deck real?

No. Larkspur Software, Lena Ortiz, Dara Lewis, Priya Shah, the email addresses ending in .example, the build number and every defect count are fictional sample data. Replace them with your own figures before the release meeting.

What should a bug report contain before it reaches this deck?

One defect per report, with a clear summary, the build and device, steps to reproduce, the expected and actual results, and one or two attachments. Remove customer data and secrets from every log or recording before you attach it.

How often should the severity counts be refreshed?

Refresh them from the tracker before each triage meeting, and at least twice a week during a release. A count more than a day old is a guess, so date every figure on the slide.

  • #bug-report-template
  • #defect-status-report
  • #bug-triage-slides
  • #release-readiness-deck
  • #defect-report-example
  • #google-slides-template

More bug report templates

See all 9

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…