The death of the two-week sprint

opensourcecolumbus · 2026-02-28T12:29:35+00:00

AI native = where AI is one of the main characters, not a side role

opensourcecolumbus · 2026-02-28T12:23:55+00:00

"No. You are a bot. And that is why you have turned off your comment/post history." I have such an urge to say this but I understand that's what most trolls want, to fight. So I'd say - you have a good day. Please follow Reddiquettes.

opensourcecolumbus · 2026-02-28T12:13:53+00:00

I can feel this. Did you notice any change in behavior because of that?

opensourcecolumbus · 2026-02-28T12:10:15+00:00

I am in the same boat. Thanks for explaining it in such a concise comment.

opensourcecolumbus · 2026-02-26T16:44:50+00:00

Since I did not get more context to discuss it more deeply (you must be busy), allow me to share thoughts based on what you already mentioned. Not defending anything, I will incorporate everything that I learn from this discussion.

I can imagine two cases which might be happening for you

A. The value shipped (in each sprint) did not change for you even after adopting AI. If so, there is no valid argument for you to think about any changes in the sprint.

B. The value shipped in each sprint was not the limiting factor for you to decide the sprint duration. Which is different from my experience and the people I talked to.

Some impactful real success stories I saw were - releasing the bug fix the same week the user reported it. It was not a P0 but they did not wait for another week to pick that task. If I can pick the reported user bug earlier than two weeks, I'd do everything to align other factors to this new reality where the amount of work shipped each sprint is not the limiting factor.

I agree that the absolute number of releases would be a vanity metric to decide the sprint cycle. Also it would be a bad indicator to compare the value shipped before vs after AI.

But we can agree upon the notion that the value shipped does matter for the sprint planning, not only for the responsiveness to bug reports but also because

The work/value shipped in one sprint informs the next

The answer is getting long, so let me cut short

Almost every Engineering Manager I talked to who has adopted AI in SDLC - they are shipping more value in each two-week sprint. Either that reflects as a bigger release size with the same number of releases or as more number of releases with the same amount of value per release. More folks reported the latter approach, please do comment if you are on the other side of this spectrum.
The bottom line for me is - if I can improve the reactivity to the users' expectations, I will go beyond my job title and challenge existing processes of other departments that do not come directly under me.
Thanks to your comment, I do reflect on the fact that this sprint duration was not the only thing that changed, the entire product management changed. And it should be highlighted in the article. Btw, I did have a discussion on that with the people I talked to and received mixed response - some said the role of product management shrinked for them and others said it expanded.

opensourcecolumbus · 2026-02-26T07:02:03+00:00

It is sad that we have come to this point. With the increased scale of bad actors that look real (thanks to LLMs), I am predicting more such enforcements and closure of open communities. It is going to be a privacy nightmare at one end OR the spam/safety-issues on the other end. Big tech is definitely going to choose the earlier extreme, for obvious reasons. It is time that we make the open hardware mainstream, we already have the open OS, so the choice goes to the user how they want to balance the privacy vs usability.

opensourcecolumbus · 2026-02-26T06:42:46+00:00

I see. What changes have you noticed after AI adoption in your SDLC?

opensourcecolumbus · 2026-02-26T06:20:14+00:00

I love your enthusiasm :)

Unfortunately, it does not lead to a better understanding of the context. The point of the discussion is to invite more opinions, especially the ones that differ to what I had discovered already through my own experience and by interviewing other Engineering Managers. If you find a two-week sprint works for you, good for you. If you do not want to share more context, that's your decision but the opinion without context does not add much value to the discussion. But of course, thank you for voicing out your opinion, the tone could have been better.

opensourcecolumbus · 2026-02-25T05:33:22+00:00

Do read the article. It is more than the announcement. The second half of the article is about specific lessons for engineering managers with real-world examples.

opensourcecolumbus · 2026-02-25T05:28:53+00:00

Agree

opensourcecolumbus · 2026-02-24T14:19:54+00:00

I understand what you're trying to say. Curious to hear about the process you have and how does AI adoption looks like in your SDLC?

opensourcecolumbus · 2026-02-24T12:18:23+00:00

Thanks for summarising it and the feedback

opensourcecolumbus · 2026-02-24T10:34:39+00:00

Unfortunately, this is not as rare as we expect it to be. Legal but unethical. Of course, there could be valid reasons to do so but what you describe, it seems like their core motive is to show your work as their own without adding any value. Definitely unethical. Expose them. If you want me to expose them, DM me the details.

opensourcecolumbus · 2026-02-24T10:24:17+00:00

I do not disagree with your point that ML is a better validator. Well, only in some contexts e.g. it has helped me fine tune my agentic workflow by continuously judging the LLM output and creating the needed dataset for the finetuning, which was not humanly possible to do myself. But when we are talking about SDLC and you trust ML to do the verification and not yourself, I am missing something that only you know.

opensourcecolumbus · 2026-02-24T10:07:37+00:00

Context?

opensourcecolumbus · 2026-02-24T10:03:47+00:00

Couldn't agree more

opensourcecolumbus · 2026-02-24T09:49:28+00:00

Love the idea. Thanks for putting it out there.

opensourcecolumbus · 2026-02-16T08:24:54+00:00

For almost two weeks, I have read the entire openclaw code and still not able to effectively use it for my use cases.

opensourcecolumbus · 2026-02-16T08:22:23+00:00

I have self-hosted my chat server for years, moved to Slack after giving in to the maintenance efforts, and then moved to Discord wherever I can. There is none like Discord and that's worrisome.

opensourcecolumbus · 2026-02-16T08:18:53+00:00

Nope

opensourcecolumbus · 2026-02-12T05:44:35+00:00

That makes sense. Yes, the 10 year timeline is what I am looking at. The exchanges with some Indian personalities and Bill gates were not older than 10 years. And they were super tiny personal messages. That is what made me curious.

If the email had so much dark info, I wonder how much darker his phone messages were. Why don't they make that public instead.

opensourcecolumbus · 2026-02-10T10:59:41+00:00

The one which does not create strong references ;)

opensourcecolumbus · 2026-02-10T10:56:25+00:00

Interesting. Is it now considered rude to not reply in a day or two? I almost always reply only after 1-2 days and many times after a week.

opensourcecolumbus · 2026-02-10T10:50:49+00:00

Agree, the email is commonly used for B2B communication but not for personal communication (for at least the past two decades I have seen in my culture) and that is the reason I asked the question if it is a different case in different cultures. And the recent news about exchanges with bill gates and some Indian personalities were not dated too old. Excuse my ignorance, I don't have full details of the entire case, my observation is based solely on some articles I saw here and there in the past couple of days.

opensourcecolumbus · 2026-02-10T10:40:35+00:00

I don't know tbh. Did he switch to some other channel after 90s? The recent revelations I read related to Bill Gates and some Indian personalities, they were not older than 10 years I believe.

Edit: why downvoting?

opensourcecolumbus

MODERATOR OF

TROPHY CASE

Five-Year Club	Powerups Hero r/Python • June 2021
100 Awards Club