7.2 — AI-Assisted Developer Workflows: Measure the Work, Package the Practice

CCAR-P Domain 7 · Task 7.2

What You Need to Know

Measure the Work, Not the Tooling

Outcome measures (properties of the work): cycle time, defect escape rate, review latency, time for a new joiner to make a safe change, incident time-to-resolution.

Adoption figures (how much the tooling was used): sessions per week, accept rate, share of merged changes containing assisted code.

Read adoption alongside engineering measures, never in place of them. Name the outcome measure and its baseline before the quarter starts.

Verifiability Decides What to Automate

Before automating, ask what checks the output cheaply (test suite, build, linter, fixture comparison). Without a check the agent can run, you become the verification loop. Work whose correctness only an experienced human can judge slowly is the worst candidate for automation — volume arrives faster than judgement absorbs it.

Packaging Turns a Habit Into a Capability

• Repeatable procedure → shared, version-controlled workflow anyone can invoke by name
• Recurring specialist task → defined role with its own instructions and restricted tools
• Recurring context need → shared project context

Outcome quality stops depending on who ran it; the gain survives a resignation.

Review Stays Independent; Humans Keep Merge Authority

Whatever produced a change still holds the assumptions it was written under. Review in a fresh context. Machine review adds a signal; a named human keeps merge authority. Scope independent review to correctness and stated requirements, not taste.

Autonomy Follows Reversibility

Bound what automation may execute; gate irreversible actions behind approval; protect important branches; let CI be the objective gate.

Exam Traps

• Reporting an adoption percentage / accept rate / satisfaction survey as the ROI
• Letting whatever produced a change review it, then recording the change as reviewed
• Pointing automation first at the work that hurts most when nothing checks its output cheaply
• Measuring the improvement honestly but leaving the procedures that produced it in individuals’ heads