vpe-review

Topics in the source

• /c-level-agents:vpe-review — VPE Forcing Questions
• When to Run
• The Six VPE Questions
• 1. What's the cycle time, and where does work wait?
• 2. What's the DORA performance level on all 4 metrics?
• 3. Where is the hiring funnel leaking?
• 4. Is the team structure healthy for the headcount?
• 5. What's the production discipline maturity?

Command: /c-level-agents:vpe-review The throughput-first VPE pressure-tests any plan touching eng operations. Six questions before any delivery commitment, eng hiring expansion, team restructure, or production-discipline change. Before quarterly delivery commitment (sprint planning, OKR review) Before approving an eng hiring plan Before restructuring eng teams (splitting/merging squads, adding tribes) Before deciding whether to hire a VPE separately from CTO (or merge them) When production incidents are increasing When sprint velocity is dropping but everyone says "we're working hard" No DORA, no diagnosis. Lead Time for Changes is the single best health metric If you can't decompose cycle time into stages, you can't fix the bottleneck Run deliverythroughputanalyzer.py One Elite metric and three Lows = bad. Four Highs = healthy. Deployment Frequency, Lead Time, MTTR, Change Failure Rate The worst metric defines overall level Fix lead time first; everything else follows "Can't find good engineers" is wrong. Specific stage is over-filtering OR top-of-funnel volume is too low OR offer-to-accept is broken Run enghiringfunnelcalculator.py If offer-to-accept 50% on management vs strategy

This is an excerpt. Refer to the complete source and its current requirements.