Why do you feel this claim is related to Agile or Scrum in any way? Because one of your principle complaints about scrum is the regular cadence. You said that

Why do you feel this claim is related to Agile or Scrum in any way? Because one of your principle complaints about scrum is the regular cadence. You said that it created an artificial breakpoint that frequently could not be lined up with demonstrable code. I pointed out that if you are skilled at breaking complex projects into smaller pieces, it should almost never be a problem to find a piece that fits into a two-week window. And indeed, I've never encountered that problem. The much more common problem is breaking the project into the wrong chunks, with faulty abstractions. But agile doesn't affect that one way or the other. It's a skill of software design that seems to have utterly no relationship to what overarching workflow management process is used. I agree, which is why the cadence is a non-issue in scrum: the aforementioned skill allows a team to virtually always find a set of chunks to fill out an arbitrarily-sized sprint.