
How We Built an Autonomous Development Workflow at Nordic Corporate Bank
Keywords
Summary
238 words
Critical Evaluation
Value of the Information & Strength of the Argument
The talk provides valuable insights into a real-world implementation of an autonomous development workflow, offering concrete metrics and a detailed description of the system architecture. The speaker’s argument is persuasive, supported by specific examples and a live demo. However, the presentation is largely anecdotal and lacks independent verification or a critical examination of potential drawbacks, such as security risks or the long-term impact on code quality. The speaker does acknowledge some challenges, such as the need for human oversight and the new bottleneck of reviewing PRs, but the overall tone is optimistic and promotional.
Scientific Rigor, Source Quality, Title Accuracy
The talk is based on the speaker’s direct experience, which lends it authenticity, but it does not cite external sources or academic research. The title accurately reflects the content. The speaker mentions a report by DNB Carnegie on agentic workflows, but does not provide a specific reference. The talk is a personal account rather than a rigorous scientific study, and the lack of independent verification limits its scientific rigor.
178 words
Title / Content Match
The title accurately reflects the content, which details the construction and operation of an autonomous development workflow at a bank.
Quality & Reliability
7/10
The talk provides a detailed, first-hand account of a real-world implementation of an autonomous development workflow in a banking context. The speaker presents concrete metrics (e.g., 572 PRs in March 2026 vs 141 a year earlier) and describes the system architecture. However, the presentation is largely anecdotal, lacks independent verification, and does not provide a formal evaluation of risks or limitations.
Key Moments
Markers derived by PSI from the transcript: the creator did not define chapters.
- Introduction and context: the speaker introduces himself and the bank, and explains the team size.
- The inspiration from a conference talk and the decision to build an AI agent.
- Introduction of Nils Skog, the AI agent, and its integration with Azure DevOps.
- Example of a product owner interacting with Nils Skog, showing the autonomous workflow.
- Live demo: the agent implements a search feature, showing the monitoring dashboard and PR creation.
- Discussion of the impact on productivity, with metrics showing a significant increase in PRs.
- Lessons learned: the need for structure, the distinction between coding and developing, and the new bottleneck of PR review.
- Security considerations: the agent's lack of access to customer data and the human approval step.
- Future plans: expanding the agent's role to handle more bank operations and become a full 'employee'.
- Under the hood: the architecture of the system, including triggers, API gateway, PostgreSQL, and container app jobs.
Cited Sources
- NDC AI Conference — The talk was recorded at NDC AI in Oslo, Norway.
- NDC Conferences — The conference organizer, providing information about upcoming events.
Concurring Sources
- NDC AI Conference — The conference where the talk was presented, supporting the context of the presentation.
Contribution & Novelties
The talk provides a rare, detailed case study of an autonomous development workflow in a regulated industry (banking), with concrete metrics and a live demo. It offers practical insights into the architecture, integration with Azure DevOps, and the cultural aspects of introducing an AI agent as a ‘colleague’. The speaker also discusses the shift in bottlenecks and the importance of human oversight.
Pour aller plus loin :
- GitHub Copilot SDK — The SDK used to build the agent, relevant for understanding the technical implementation.
- Azure Container Apps jobs — The service used to run the agent’s workers, providing a cost-effective execution model.
- Agentic workflows — The concept of AI agents performing tasks autonomously, as highlighted in the talk.
- Azure DevOps Web Hooks — The mechanism used to trigger the agent from Azure DevOps events.
134 words
Radar Profile
The radar profile shows high scores in quantity of information and technical level, reflecting the detailed and technical nature of the talk. The quality of information and reliability are slightly lower, due to the anecdotal nature and lack of independent verification. The overall profile suggests a technically rich but not fully rigorous presentation.