Role Playbooks tracks how each delivery role changes under AI — developer, QA, PM, business analyst, solutions architect, DevOps. Field-tested playbooks for CTOs and the delivery teams doing the work.
Role Playbooks
Test count is up, the suite runs in minutes, coverage climbed after the AI generators went in. And escaped defects have not moved, or drifted the wrong way. More tests, same protection.
Role Playbooks
PMs are producing far more, faster, and nothing downstream improved. Requirements that took a day now take minutes. Yet acceptance criteria are no sharper and the wrong features still ship.
Role Playbooks
The diff is clean, tests pass, and the work lands in half the time. Then a reviewer asks why the bug happened, and the answer does not come. Not because the junior is careless.
Role Playbooks
A background agent opened a PR at 2 a.m. and the gate let it through, because the gate was built for a worker who could be reasoned with. The DevOps job is no longer writing infrastructure. It is owning the bounded environment agents act inside.
Role Playbooks
You bought the tools. The team is using Copilot. There is an AI lead, a working group, maybe an AI center of excellence deck on a shared drive. Delivery metrics are flat. An AI champions program built as evangelism produces a Slack channel.
Role Playbooks
The diagram is still requested. But if you are a Solutions Architect on a team that has gone agentic, the most consequential thing you shipped last quarter was not a design document.
Role Playbooks
The dashboard says ninety percent of the team is using the AI tools. More code is shipping than last quarter. Cycle time is flat, the review queue keeps growing, and a tester just flagged a defect that should have been caught two stages earlier.
Role Playbooks
Most developers adopted AI and ran a delegated engineering workforce as a faster keyboard. Usage went up, review load went up, and cycle time barely moved. That is a role-design problem. The developer's new leverage is the harness the agent works inside, not the keystrokes per hour.
Role Playbooks
A business analysis function turns on AI story generation. Story count climbs, spec volume rises, time-to-draft falls. The one number that does not move is requirement-related rework. That is not a tooling problem. The BA role was never redesigned for a world where authoring is free.
Role Playbooks
A QA function turns on AI test generation. Test counts, suite size, coverage all rise. Escaped defects stay flat. The team was promised faster quality and got faster activity instead. That is not an adoption problem. It is a design problem AI made visible.
Role Playbooks
Dev, QA, PM, BA, SA - five delivery roles, five different ways AI breaks them. Generic training fits none. The fix is a per-role playbook with four components, the last of which is the part a manager can inspect in five minutes.