Don't Redesign Your Process Yet. Change Who Writes the Artifacts.

The useful part

The first thing to change is who writes the artifacts, not how you work "We didn't change the process. What they changed instead is who writes the artifacts: in order to create good requirements there are a set of steps you need to do, and they created a skill for each one of them. The people in engineering, and in product, are not supposed to write anything on their own anymore.

How it works

• You can tell when it comes due: it's when your board stops telling you where the work is.
• So essentially everybody is developing this system that is the agentic development lifecycle, which is the right mindset.
• That is the change I would make first, and it's a much smaller change than the one most leadership teams reach for after a demo.
• What they changed, and what they left alone on purpose Quarterly planning is unchanged.

Details worth keeping

We still have a quarterly planning and we have sprint planning and we have roadmaps and a list of features that we want to deliver in a quarter." That is Shay Mandel, describing an organization of about two hundred people that has spent three or four months putting an agentic development lifecycle into production. They just need to fix the skills or fix the context. It's clear that the model is not going to be perfect.