romannikolaev

Yes, it sounds very familiar. Scrum is not really designed for this mode of operation. It works well when there are no interruptions, and the team knows the code and domain area inside out.

To be honest, I was only once in this situation. It was when I worked with a small team on a greenfield project. We knew the whole codebase, and the project wasn't deployed to clients yet - so no surprises during sprints.

When work is connected to outcomes—when you can see how your efforts contribute to the business - there’s a natural tendency to focus on the most important things and approach them in the most effective way.

I suppose the larger the organization, the more difficult this becomes to achieve.

To be fair, I have the advantage of being part of the leadership :) (CTO at a startup).

I think this style of delivery is fine as long as both management and the teams are comfortable with it. The only thing that frustrates me in this setup is the agile theater - planning, estimating, and refinement.