Scrum does not say “only focus on output”, but, unfortunately, humans will optimize for what they measure.
If you worry about story points & hitting your estimations, that’s what is going to consume your attention. That is what you and your team will optimize for.
And that is the core critique of Scrum as it is practiced: That it focuses a product team’s attention so heavily on delivery — on building lots of features quickly & efficiently — that teams fail to focus on spending time to discover what the right thing to build is.
“Togetherness” is a fittingly nauseating name for an old ideal in planning theory. This ideal is that if anything is shared among people, much should be shared. “Togetherness,” apparently a spiritual resource of the new suburbs, works destructively in cities. The requirement that much shall be shared drives city people apart.
When an area of a city lacks a sidewalk life, the people of the place must enlarge their private lives if they are to have anything approaching equivalent contact with their neighbors. They must settle for some form of “togetherness,” in which more is shared with one another than in the life of the sidewalks, or else they must settle for lack of contact. Inevitably the outcome is one or the other; it has to be; and either has distressing results.
City residential planning that depends, for contact among neighbors, on personal sharing of this sort, and that cultivates it, often does work well socially, if rather narrowly, for self-selected upper-middle-class people. It solves easy problems for an easy kind of population. So far as I have been able to discover, it fails to work, however, even on its own terms, with any other kind of population.