| International Journal of Computer Applications |
| Foundation of Computer Science (FCS), NY, USA |
| Volume 187 - Number 139 |
| Year of Publication: 2026 |
| Authors: Ajay Roy |
10.5120/ijca9a6d76e6230d
|
Ajay Roy . Domain-Specific Contexts versus General Enterprise Contexts: Effects on AI-Driven Agile Requirements. International Journal of Computer Applications. 187, 139 ( Aug 2026), 13-21. DOI=10.5120/ijca9a6d76e6230d
Speed is the lifeblood of modern software engineering, where global tech firms rely on Agile frameworks to slash time-to-market. Within this high-velocity environment, Artificial Intelligence has become indispensable, embedding itself across every stage of the Software Development Life Cycle (SDLC) to ensure teams hit their delivery targets. Yet, the caliber of output from these AI solutions is far from uniform. Consider Atlassian Rovo, a native agent inside Jira designed to draft user stories directly within the workflow. Our research leveraged Rovo for this specific purpose, pitting its generated content against Microsoft Copilot 365 in a head-to-head evaluation. While both tools aim to accelerate the requirements phase, our comparative study highlights distinct variations in the clarity, context-awareness, and overall utility of the user stories produced by each platform.Ten user stories, ranging from standard CRUD operations to complex financial logic, served as the testbed. Rovo achieved a mean INVEST fit of 4.6/5 and a technical accuracy of 4.6/5. The Copilot scored 3.6 and 3.1 points. Human revision time decreased by 60% Rovo (3.2 vs. 8.0 min). This variance stems from the context. We compared Atlassian Rovo, which accesses structured development artifacts (Jira/Confluence), with Microsoft Copilot 365, which queries unstructured communication logs (Outlook/Teams). The data confirms a singular truth: domain-specific contexts outperform general enterprise contexts in requirements engineering research. Structured artifacts help reduce hallucinations, whereas conversations can add noise.