My take from the article is to not sacrifice good engineering principles (e.g. code quality, tests, scalability, performance...) and re-scope, adjust number of

My take from the article is to not sacrifice good engineering principles (e.g. code quality, tests, scalability, performance...) and re-scope, adjust number of feautures, etc when needed. That’s just the nature of engineering. As Product owners get more experienced (contextually) and better communicate with Engineers, scopes get better and sprints are more accurate. Can sprints be used as highger level structure grouping pieces of work together, without any hard deadline involved? I think that happens in some organisations, with no or soft deadlines.