AI & ML
Optimal Development Path: An Empirical Evaluation of Tiered Dependency-Aware Sequencing
arXiv cs.SE0 views
arXiv:2611.23303v1 Announce Type: new Abstract: The Optimal Development Path (ODP) in D-POAF orders Feature Blocks in a Wave Candidate by choosing the eligible block with the lowest effort-and-risk-to-value ratio (ERS/BVS), while respecting declared prerequisites. We evaluate native ODP (L0) against four dependency-aware strategies: unlock count (L1), unlocked value (L2), multi-hop potential (L3), and one-step rollout (L4), alongside local search, Sidney decomposition, and an exact reference. On held-out synthetic graphs with about one prerequisite per block, L0 attains 0.978 of the surrogate optimum at 12 blocks, versus 0.993 for L2 and 0.994 for L4. At 100 blocks, L0 attains 0.942 and L2 0.983. In contrast, 373 historical Jira sprints from 21 open-source projects in TAWOS, used as scheduling proxies rather than D-POAF Waves, contain sparse recorded dependencies. On these instances, L0 attains 0.998 of the surrogate optimum and is exactly optimal in 69% of sprints. Unlock bonuses calibrated on synthetic graphs do not deliver significant average gains on these sprint-derived instances and can worsen the surrogate. L4 never worsens the declared surrogate relative to L0, but this guarantee does not extend to operational outcomes. Retrospective calendar replays using recorded Jira durations show that surrogate improvements do not reliably improve value-weighted completion. The findings support keeping L0 as the default and presenting rollout and exact references as auditable alternatives. Dependency-valid sequences expose prerequisite readiness, but their effects on interruptions, rework, costs, and delivery times remain unmeasured.
Source:https://arxiv.org/abs/2611.23303PreviousWhen Code Works but the License Doesn't: Evaluating License Constraint Handling in Coding AgentsNextDependency Fabrication in Repository Deployment Agents
Related posts
Razorpay webhook not verified: anyone can fake a payment
0dev.to
From FAQPage Schema to Answerable AI Documentation
0dev.to
Wiring Android's MediaPipe LLM Inference API to a Multi-Turn Conversation Engine
0dev.to
What Is LLM Throughput? Tokens per Second, Concurrency, and Batching
0dev.to
Diese Woche haben mir zwei Tools etwas vorgeschlagen und es direkt abgeschickt.
0dev.to
AI Agent Observability: What to Log Before Production
0dev.to