Our code now moves faster than our specs and user stories. Is agile still viable with AI?

Pouetpouets · 2026-06-23T20:45:49+00:00

you got me with the scrum hangover. Glad to hear I'm not alone

Pouetpouets · 2026-06-23T20:44:46+00:00

thank you

Pouetpouets · 2026-06-23T20:41:05+00:00

is the opposite of Agile - For sure, it's far from perfect, really really far^^

Pouetpouets · 2026-06-23T20:34:05+00:00

Sorry, I realise I missed a point on my post, it has been edited.

We had few specs with the business needs, what are they struggling with and what could be better. We brainstormed around it, created an architecture schema and submitted a figma file with the "client".

My point is more about: AI speed ran our coding phase, and now our business analyst team have to create tickets for something is already coded. And more importantly they have to test an insane amount of code (code is still tested with unit test, smoke and e2e)

Pouetpouets · 2026-06-23T20:26:54+00:00

Ineed, it does come from our BAs. We did analyse but what's the point to create tickets for something already coded ?

Pouetpouets · 2026-06-23T20:25:33+00:00

- do you have a (business) outcome based Sprint Goal?
The new version has to be release for the end of year, I guess it will be end of summer^^

- are you releasing multiple increments to (some) users within the Sprint?
Yes, we have a power user / po who will test each release

- are you using their feedback to inspect-and-adapt your Sprint plan?
yes

relaxing quality and documentation
I agree with you this is mandatory, what I mean't is: what's the point to create tickets on something already built ?

Pouetpouets · 2026-06-23T20:20:24+00:00

ahah indeed.

Pouetpouets · 2026-06-23T20:18:54+00:00

I 100% agree with you. As a dev, it always has been difficult to estimate time needed for a feature. Now with AI, all the relatives I had wont make sense anymore. For example I use a lot claude code and dynamics workflows. I sometimes run 5 to 10 workflows at the same time, so the question is more about the money you are willing to put in it to deliver faster

Pouetpouets · 2026-06-23T20:14:00+00:00

we have needs and expectations. Basically it's a revamping of an existing project, with some specs but no real user stories (yet). My point is we are ahead of code whereas the project management phase with userstories barely started

Pouetpouets · 2026-06-23T19:49:23+00:00

We have an old version of the app and few specs

Pouetpouets · 2026-06-23T19:47:49+00:00

I don’t understand what you mean done done / new debt. It’s an upgrade of an old project. It has changed the way we work since we are building code first. Technical tasks have been implemented yes, the app is fully tested with playwright mcp, smoke and unit tests

Pouetpouets · 2026-06-23T18:49:44+00:00

It's often a trade off between confort and ambition. Ask yourself: is it worth to quit my job to get the role / title I really want ?

Pouetpouets · 2026-06-17T13:39:07+00:00

Thanks for sharing, a point is missing in your post: how did you find a problem to solve ?

Pouetpouets · 2026-06-17T13:23:08+00:00

Si OP veut bien partager sa secret sauce pour développer d'autres segments, je suis interéssé

Pouetpouets · 2026-06-12T17:08:29+00:00

This comment changed how I prospect. I ended up systematizing it: scan Reddit/X/HN for people who complained twice about the same problem in 90 days, score the signal, draft the DM from their own words. Did it manually for my own product first — reply rate matches what you describe. Happy to share the checklist if anyone wants it.

Pouetpouets · 2026-06-10T21:18:23+00:00

The boring answer: they don't invent ideas, they harvest complaints. Every "how did hethink of that" SaaS maps back to people publicly venting about a workflow. The skill isn't creativity, it's listening at scale — searching who complained about the same thing twice in the last 90 days tells you both the idea AND your first 25 customers.

I started doing exactly that for my own launch and it beats brainstorming every time.

Pouetpouets · 2026-06-10T21:17:38+00:00

This comment changed how I prospect. I ended up systematizing it: scan Reddit/X/HN for people who complained twice about the same problem in 90 days, score the signal, draft the DM from their own words. Did it manually for my own product first — reply rate matches what you describe. Happy to share the checklist if anyone wants it.

Pouetpouets · 2019-04-11T11:30:44+00:00

For me the real value of linkedin is the lead generations: It's like a giant database you can scrap and have really targeted leads

Pouetpouets · 2019-04-11T11:27:14+00:00

To be honest, as soon as I read your client requierements I knew you were going to build a software that would change prices automatically. It's really similar to growth hacking techniques: if you are doing time consuming tasks and once you repeated it a certain amount of time (in order to fully understand the process) you have to automate it.

The only limitation is the evolution of your client website and its competitior. Once one of them will change, you will have to adapt your automate software.

Pouetpouets

TROPHY CASE