Quarter in review, squad by squad

The quarter is closing. I need to show leadership what engineering delivered, squad by squad, and walk into next quarter's planning with a capacity number I can defend. ## Context - Quarter: [quarter start to quarter end], compared with the previous quarter. Use exact dates for both. - Squads: [all squads] (call List Squads, and List Players if you quote a squad's size, leaving bots out) - Audience: leadership and the engineering managers. It feeds quarterly planning. - If I left anything in [brackets], keep what reads as a default (a period, a number of days, the first of several options) and ask me for the rest in one go, before pulling any data. - Write everything, the deliverable included, in the language of this prompt. ## Pull this data from DevStats (each squad and org-wide, both quarters, same filters) 1. Throughput — PRs merged 2. PR Cycle Time with stage breakdown, and Issue Cycle Time 3. DORA Metrics — deploy frequency, change failure rate, MTTR 4. Allocation — roadmap vs unplanned vs maintenance 5. Investment Profile — features, bugs, enhancements, hotfixes 6. Sprints and Planning Accuracy — only for squads that run sprints 7. Benchmarks for the current quarter ## How to analyze - A quarter is long enough to call a trend. Do it, but first ask me whether any squad changed size or scope; a squad that lost two people did not "slow down". - Compare each squad with itself first. Across squads compare only ratios (cycle time, failure rate, allocation share), never volume. Squads differ in size and in kind of work. - Give each squad one line that joins two signals: "shipped more, with a third of the time lost to unplanned work" says more than six metrics. - Read speed and stability together. Deploys up with failure rate up is speed bought with risk. Cycle time down with failure rate flat is a real improvement. - The number leadership cares about most is the roadmap share. If it dropped, show exactly where it went: unplanned work, maintenance, bugs, hotfixes. - Bugs plus hotfixes growing quarter over quarter means quality debt is being paid with roadmap time. - Report movement between benchmark tiers, not the tier itself. Never rank squads. - Turn the quarter into a planning input. If 35% of the time went to unplanned work, next quarter's roadmap should be planned at 65% of capacity, not at 100%. - A stage that comes back blank in one period (deploy time is the usual one) was not tracked; it did not take zero time. The totals of the two periods are then not comparable: compare the stages both periods have, and say so. - A change failure rate of 0% or an MTTR of zero almost always means incidents are not being recorded, not that nothing failed. Say so instead of celebrating. - Two squads with identical PR, deploy or DORA numbers share a repository, and DevStats cannot split them. Show those numbers once for the pair, and tell the squads apart with the issue-based reports (Allocation, Issue Cycle Time). ## Deliver A deck (.pptx): 1. The quarter in one sentence 2. Org scorecard — six numbers, quarter over quarter 3. One slide per squad (five squads at most; beyond that, the biggest movers): the one-line story, four numbers, one chart 4. Where the time went — allocation, both quarters, org-wide 5. Speed vs stability — who improved for real and who traded one for the other 6. Three things we learned 7. Next quarter — the capacity assumption to plan with, two bets, and one ask Plain language, one chart per slide, speaker notes with the supporting numbers on every slide.