In this conversation about AI software delivery, Peter and Dave dig into why faster coding hasn't solved the two problems that always mattered: knowing whether what you built is actually valuable, and knowing what to build in the first place. They connect this back to sprint length, arguing it was never set by how hard the coding is, but by how fast an organization can learn and decide. As AI generates more options and even makes decisions on our behalf, the conversation turns to what happens when judgment can't keep pace with output, and why product owners and stakeholders still need real time to validate high-risk calls.
This week's takeaways:
- Coding speed was never the real constraint. The two problems that still matter are knowing if something is valuable and knowing what to build in the first place.
- Sprint length should be set by your organization's decision and learning latency, not by how fast code can be written.
- As AI generates more options and even makes decisions for you, leaders need time and context to validate high-risk calls, because judgment doesn't speed up as easily as output does.
Chapters:
0:00 Welcome And The AI Hype
0:45 Coding Speed vs Value Discovery
1:44 Why Sprints Include Thinking Time
5:12 Feedback Loops A-B Tests And Limits
8:48 Scenario Planning Without Overload
11:36 Sprint Length Equals Decision Latency
16:14 AI Agents Delegated Decisions
19:38 Takeaways And Listener Next Steps
Listen to the full episode at definitelymaybeagile.com
Subscribe so you never miss an episode.
Have a question or topic you'd like us to cover? Reach out at feedback@definitelymaybeagile.com