An organization is choosing which SDLC activities to keep human-driven versus automate with agents. They have four candidates: (1) gathering ambiguous stakeholder requirements, (2) generating boilerplate service scaffolding from an approved template, (3) performing final architectural review of a new microservice, and (4) running regression tests after each commit. Which TWO activities are MOST appropriate for full agent automation?
Select an answer to reveal the explanation.
Short Explanation
Agents thrive where success criteria are clear before the work starts. You can automate template-based scaffolding and regression testing because they're rule-based and objectively validated. Keep humans on ambiguous requirements and architectural review.
Full Explanation
The fundamental question for agent suitability is whether success can be defined objectively before the task begins. When the answer is yes, agents excel. When the answer requires human judgment, context, or relationship navigation, agent automation adds risk.
The correct pairing is generating boilerplate service scaffolding from an approved template and running regression tests after each commit. Scaffolding from an approved template is ideal for agents: the input is a specification, the transformation rules are fixed, the output can be validated against the template, and there is no ambiguity. Regression testing is the canonical agent task: run a defined set of tests, collect pass/fail results, report. Both activities are high-volume, repetitive, rule-based, and produce objectively measurable outputs.
The pairing of ambiguous stakeholder requirements gathering with final architectural review is wrong. Requirements gathering for ambiguous stakeholder needs requires active listening, follow-up questions, political navigation, and the ability to detect what stakeholders mean but didn't say — none of which current agents handle reliably. Architectural review requires evaluating emergent trade-offs, organizational context, team capability, and long-term maintainability — again, judgment-heavy work where agent errors could have major downstream consequences. The idea that agents should handle the most critical or high-stakes work is backwards; high-stakes judgment belongs with humans.
The pairing of ambiguous stakeholder requirements gathering with regression testing is also wrong. Natural-language processing does not make requirements gathering agent-safe — the bottleneck is judgment and relationship management, not language processing. The regression-testing half is correct, but the pairing is not.
The pairing of final architectural review with regression testing is wrong as well. Architectural review is too judgment-intensive and high-stakes for full agent automation. It may benefit from agent-assisted analysis, such as detecting anti-patterns in code, but final review authority should remain human. The regression-testing half is correct, but the pairing is not.