agents-in-the-team
Agents in the Team
AI coding and ops agents now take tickets directly from issue trackers: Linear delegates issues to agents, Jira work items can be handed to Rovo and partner agents, and GitHub issues can be assigned to Copilot. The agent opens a pull request; a human still has to decide whether it is right. That moves the bottleneck from writing code to reviewing it, and it moves the delivery manager's job from assigning people to deciding which work an agent may take, how it must be specified, who is accountable, and how to see quality slipping early.
The agent treats this as a delivery system, not a tooling choice: a delegation policy with hard blocks, agent-ready tickets, named human accountability, a review-capacity gate, metrics split by author type, security controls, and a phased rollout. Two stdlib tools do the arithmetic.
When to use
- Deciding which backlog items an agent may take, and writing that down as policy
- Rewriting tickets so an agent can execute them without guessing
- Sprint planning with agents: will reviewers keep up?
- Monthly review: are agent PRs holding quality vs human PRs, and vs the DORA metrics?
- Designing access, secrets and prompt-injection controls for agents on trackers and repos
- Rolling agents out from pilot to multiple teams
When NOT to use: choosing or evaluating an AI coding tool itself (vendor evaluation); building an agent (engineering agent-design skills); individual developers using an AI assistant in their editor with no ticket delegation (normal code review applies).