Portfolio Quality Index(4.1.8)

The quality index translates reopen rate into a simple score — the lower the reopen rate, the higher the score. The reopen rate is the week's reopens as a share of the issues the project completed that week, so the index answers one question: of the work this project finished, how much came back? A week reads 100 when nothing came back. It can read below zero in a week where more issues were reopened than were completed, because a reopen may undo a completion from an earlier week; that is reported as measured rather than raised to zero. This makes it possible to compare quality across projects that may have very different absolute volumes of work, and to track whether the portfolio is improving over time.

What you can conclude

• A project with a consistently high quality index is delivering work cleanly — issues are being delivered and staying delivered.
• A declining quality index across multiple projects simultaneously suggests a portfolio-wide issue — shared processes, shared tooling, or a shared pressure that is driving down quality everywhere.
• A project whose quality index recovers after a dip has returned toward its earlier level; the chart shows when, not why.
• A gap in a line is not a quality reading of any kind. It marks a week the project completed fewer than five issues, which is a statement about how much finished work there was to judge, not about quality.

How this chart works

Small multiples, one tile per project, each drawing the project's weekly quality index as a line on a scale shared by every tile. Quality index = (1 − reopens ÷ completions) × 100, computed only for weeks in which the project completed at least five issues. Below five the arithmetic still runs but the answer is dominated by a single event: with one completion the index can only be 100 or 0, and with four it moves in steps of 25. Those weeks are left unscored and draw as a break in the line, so a thin week cannot lift a project to the top of the chart or drop it to the bottom. The completions, the reopens, the revivals and the project's total recorded changes are published for every week, scored or not, so the evidence behind each point — or behind each gap — is always visible. Total recorded changes are context only and are not the denominator of anything on this chart.

A reopen is a transition out of a delivered-classified terminal status back into the workflow; revivals of issues closed as abandoned or duplicate are counted separately in the revived column, not as reopens. Use the date and project filters to focus on specific teams or periods.

The week in progress is not counted: only complete weeks enter the tiles, and a project with no complete week in the selected range has no tile.