Most of the meetings for the SAFe process aren’t team oriented but collaboration oriented, to empower the team to work the way that’s best for them. Teams with

Most of the meetings for the SAFe process aren’t team oriented but collaboration oriented, to empower the team to work the way that’s best for them. Teams within SAFe can use any methodology that they want, scrum, kanban, lean, etc. The world outside of your dev team is what the other meetings are for: keeping business side informed of progress, checking in on cross team dependencies, deciding whether a change in plan needs to happen based on some unexpected problem, etc. That’s one of the reasons that SAFe insists on PI planning, it’s to consolidate as many meetings as possible into 2 days per quarter so they don’t invade every week as a back and forth. When the business side and dev side of the house are communicating and on the same page, there’s a lot less friction in the work relationship.