Enterprise 'common' cadence for sprints and quarterly increments (big room planning)

replying to see if it triggers any more ‘views’ to my query above on enterprises and if anyone has seen a large corporation on the same sprint cadence and same QIP cadence within a business group? @sunasak @JessO @Ncherpak @eric.abonce  - you seem to be active members - tagging you on a whim you might have some input? Thank you in advance!

We plan quarterly with monthly sprints. In my previous job sprints were two weeks. However, we do not have a standard across the organization, since asking for any standard practice meets with a lot of resistance. Just getting project managers to put their projects in the system has been hard enough.

Additionally, not all parts of the Services area of our company is committed to Agile processes, though there is movement at last. Development, IT, etc., are much more used to working that way, but they use Jira and other tools.

We are a large organization primarily using SAFe (Scaled Agile methodology) with 20 Agile Release Trains and aproximately 112 agile teams.  All agile teams (using scrum) follow the same two week sprint cadence and we have 10 weeks per Program Increment.  We use Planview Portfolios, AgilePlace and Jira, we have straight agile work with development teams as well as hybrid projects (standard waterfall with dependencies on an agile team)

Implementation of this did create some friction with our business groups however, the leaders of our EPMO (Enterprise Portfolio Management Office) stayed strong and explained the benefits of following the same cadence across the organization which allows our agile teams to look forward and plan efficiently based on capacity. i.e. If they have a dependency on another agile team, it’s imperitive that they understand how that team plans so their requests are in early enough to have the work completed on time.