Keeping Humans Accountable as AI Agents Take On the SDLC

Who is responsible when an AI agent finishes a development task? Ming Wu, head of engineering for Dev AI at Atlassian, puts that responsibility with people. In her interview with Alan Shimel, she separates the ability to automate work from the obligation to understand and control the result. That distinction matters as teams move beyond individual coding prompts and start assigning agents larger portions of the software development lifecycle.

Wu describes governed agent loops as two related capabilities. Governance supplies visibility, guardrails and enforcement; loops allow agents to process batches of jobs under defined conditions instead of waiting for someone to trigger each task. The scope can include taking on an issue, carrying out the work and reviewing a pull request. Automation may handle more steps, but teams still need a way to trace activity and judge whether the output meets their expectations.

Existing work-tracking systems offer a place to organize that activity. Wu explains why Jira is an initial interface for the approach: it already records work across teams and organizational boards. She also describes support for third-party coding agents and a shared context layer intended to give agents a consistent understanding of team priorities, organizational requirements and business intent. Coordinating those inputs is part of the engineering problem, particularly when several agents contribute to the same body of work.

Customers are asking how to scale these workflows and demonstrate real improvements in delivery speed, according to Wu. Some software teams are already experimenting, while organizations in more traditional industries are at different stages of adoption. Her examples put visibility into work alongside automation itself: teams need to see what agents are doing, where people remain accountable and whether the investment is producing useful gains. Completing more automated tasks is only part of that assessment; understanding their contribution to the software lifecycle is the harder question.