> 2) We need at least some visibility on what to do so let's bundle a few short tasks for the (literally) foreseeable future. Backlog on every level is always

> 2) We need at least some visibility on what to do so let's bundle a few short tasks for the (literally) foreseeable future. Backlog on every level is always non-empty. So sprint filling is not a problem. Planning step is not about visibility. You can have a near roadmap with any process. But scrum tries to promise that we put only particular amount of tasks to be able to finish it. Sorta, in my experience there were only few finished sprint cases in different jobs with different teams, with and without scrum master. And from this moment scrum goes over the rails. Why we need this restriction at first place?