What problem does it solve? Teams struggle to ship software faster because they optimize the wrong things — adding people, extending hours, or buying tools — while the real bottlenecks are decision latency, oversized scope, large batches, and approval gates. This Skill provides an evidence-based playbook grounded in DORA, Standish CHAOS, QSM, and McKinsey research to systematically remove those constraints. ## Core Features & Use Cases - Fixed-Time/Variable-Scope Planning: Structure engagements around timeboxes with MoSCoW prioritization, capping Must-Haves at 60% of effort so scope absorbs schedule pressure. - WSJF Prioritization: Rank backlogs using Cost of Delay divided by job size, replacing opinion-driven sequencing with an economic framework. - Flow Optimization: Apply Little's Law, WIP limits (~2/3 of team size), 1–3 day batch sizes, and pipelined timeboxes to cut cycle time and multiply throughput. - Organizational Diagnostics: Identify delivery killers such as Change Advisory Boards, teams larger than 7, long-lived branches, and decision latency over 4 hours, with contract and team-structure fixes. - Use Case: A consultancy starting a new client engagement uses the Week 0 checklist to set up 2-week cycles, a CI/CD pipeline, trunk-based development, and a 4-hour client decision SLA before writing code. ## Quick Start Ask the AI to apply the delivery velocity playbook to plan an MVP scope and set up a two-week fixed-time delivery cycle for your project.
