EDBT 2026 Demo / reviewers in the wild / expert
Jirat Pasuksmit
dblp:296/4337
· DBLP profile ↗
3ranked-venue papers in the field
3as first author
3since 2021 · last 2025
0000-0003-4059-757XORCID · corroborated
Domains — venue-derived; a paper can count in several
Other / Interdisciplinary · 3 (3 first)
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2025 | Human-In-The-Loop Software Development Agents: Challenges and Future DirectionsabstractMulti-agent LLM-driven systems for software development are rapidly gaining traction, offering new opportunities to enhance productivity. At Atlassian, we deployed Human-in-the-Loop Software Development Agents to resolve Jira work items and evaluated the generated code quality using functional correctness testing and GPT-based similarity scoring. This paper highlights two major challenges: the high computational costs of unit testing and the variability in LLM-based evaluations. We also propose future research directions to improve evaluation frameworks for Human-In-The-Loop software development tools. Jirat Pasuksmit, Wannita Takerngsaksiri, Patanamon Thongtanunam, Chakkrit Tantithamthavorn, Ruixiong Zhang, Shiyan Wang, Evan Cook |
MSR | 1 |
| 2023 | Improving Agile Planning for Reliable Software DeliveryabstractAgile software development prioritizes the delivery of working software. However, there are challenges in the sprint planning process that could impact the reliability of sprint delivery. In this paper, we list three challenges related to the sprint planning process. We also discuss future work directions to facilitate the sprint planning process and mitigate those challenges for software teams. Jirat Pasuksmit, Kemp Thornton, Arik Friedman, Natalija Fuksmane, Isabelle Kohout, Julian Connor |
MSR | 1 |
| 2022 | Towards Reliable Agile Iterative Planning via Predicting Documentation Changes of Work ItemsabstractIn agile iterative development, an agile team needs to analyze documented information for effort estimation and sprint planning. While documentation can be changed, the documentation changes after sprint planning may invalidate the estimated effort and sprint plan. Hence, to help the team be aware of the potential documentation changes, we developed DocWarn to estimate the probability that a work item will have documentation changes. We developed three variations of DocWarn, which are based on the characteristics extracted from the work items (DocWarn-C), the natural language text (DocWarn-T), and both inputs (DocWarn-H). Jirat Pasuksmit, Patanamon Thongtanunam, Shanika Karunasekera |
MSR | 1 |