Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Lets go back to waterfall even harder and write the super correct and detailed design doc.


You jest but this is precisely what we have done. Our customers have downright rejected SCRUM. It is considered a waste of money.


At a recent AI workshop management made clear that they see AI as rendering sprints and scrums obsolete, that Kanban makes a lot more sense, and that estimating effort/story-points is also becoming meaningless. Which is a strong silver lining if you ask me.


I want to understand how AI leads to this outcome.


I think it's to do with the bottleneck shifting away from code generation and towards specifying and reviewing and integrating code. The process of working with AI agents to produce specs, tech specs, code, and reviews lends itself more to a flow-based structure (like kanban).

Bear in mind this is a B2B enterprise company with a mix of legacy and greenfield. And management has invested heavily into designing a robust spec/context-based workflow for using agents. Might be different elsewhere.

Personally I don't think scrums, planning, retros etc were better than kanban even before AI, at least if you have switched-on, motivated and smart people on your team. They actually made things less agile, and story-points give a false sense of predictability. Imo the crucial factor may be that AI agents are smart and switched-on (with the right context).


Its a good excuse to move away from a shitty process, I'll take it! Fuck SCRUM, fuck Agile. No one was doing it anyway. I had to quit an Agile job because I was shipping shit without ever getting a lick of feedback, and this was not some webdev low stakes work, it was for planning expensive real world installations.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: