Some Scrum teams in my organization start working on stories which are potentially part of the release, but not part of the current sprint.
1. Teams plan the next few sprints (at a high level) during each SAFe PI planning, so they have an understanding of what's coming in future (although it might change)
2. Only 1 member works on any story, with an exception of an automation test engineer. Peer reviews are done by a couple of senior members. Team and management are not convinced about the benefits of pair programming or mob programming. Team size is 7 + PO & SM.
