[Cthulhu_]

This is what we do at my current job, they follow "safe" (scaled agile framework - don't look it up if the scrum inforgraphic already gives you shivers), but it boils down to two weeks of tidying, innovation and learning (in practice it's just more regular work) and two days of intensive planning, where from top the main priorities for the quarter are outlined and all the teams figure out what they are going to do and more importantly what dependencies they have on each other so every team can plan that.

[psunavy03]

The most abused concept in SAFe, because people fail to use it as intended (get a snapshot of the next quarter and be ready to pivot if things change) and use it to "lock down the plan," have teams refuse any new requests, and have management judge your "predictability score."

It's a great idea in theory until you see how much two full days of timeboxed planning every quarter beats down dev morale in practice. It's great for teams that literally don't know what they're doing and don't know their dependencies, because it forces them to confront their mediocrity. But you have to move beyond it eventually.