Meetings aren't inherently bad, but they have the stigma of interrupting and delaying work. In Agile, meetings are part of the work. Therefore, each meeting in an Agile framework has a specific purpose, agenda, attendees, and expected outcomes. Other meetings not described or suggested by a framework MAY OR MAY NOT be important to accomplishing work. Joining meetings in which you are not required MAY OR MAY NOT be valuable to you and the other participants. Attend meetings judiciously. Add "extra" meetings judiciously. ALWAYS have an agenda, timebox, and come away with action items. Learn more about meetings here.
Everyone loves meetings, right?
References
1 - Scrum Guide https://scrumguides.org/scrum-guide.html
2 - Scaled Agile Framework https://www.scaledagileframework.com/
PI Planning Committed PI Objectives per team with Business Value Program Board with forecast feature delivery, dependencies, and relevant milestones Before the start of each Program Increment (every 10-12 weeks) Planned during I&P Iteration Facilitator: Release Train Engineer (RTE) Once at the end of every Iteration (every 2 weeks) Final integrated PI System Demo would occur during I&A Workshop Facilitator: Release Train Engineer (RTE) Before the start of each Program Increment (every 10-12 weeks) Planned during I&P Iteration Occurs before the PI Planning Required: Product Owners, Solution Management & Architect (if applicable) Daily Once every end of the Sprint (2 weeks) Occurs after the Iteration Review and before the Iteration PlanningProgram Level/ART Ceremonies
Name Outcomes Frequency Timebox Attendees 2 Days Required: ADO Teams, Scrum Masters, Product Owners, Product Manager(s), System Architect, System Team, Business Owners, Solution Management and Architect (if applicable), COR, Security & Compliance Recommended: CCSQ Leadership System Demo 1 Hour Required: Product Owners, Product Manager(s), System Architect, System Team, Business Owners, Relevant Team Members Recommended: Scrum Masters, Solution Management and Architect (if applicable), COR, Security & Compliance Inspect & Adapt (I&A) Workshop 6 Hours Facilitator: Release Train Engineer (RTE) Required: ADO Teams, Scrum Masters, Product owners, Product Manager(s), System Architect, System Team, Business Owners Recommended: Solution Management and Architect (if applicable), COR, Security & Compliance Agile Release Train (ART) Sync Once or twice a week 30-60 Minutes Facilitator: Release Train Engineer (RTE) Required: Product Owners, Scrum Masters, Product Manager(s) Recommended: Relevant Team Members, Solution Management and Architect (if applicable) Program Kanban Refinement Continuous (meeting as necessary) As needed Facilitator: Product Manager(s) (Feature author/owner) Recommended: Release Train Engineer (RTE), Scrum Masters Team Level Ceremonies
Name Outcomes Frequency Timebox Required Attendees Daily Stand Up 15 Minutes Facilitator: Scrum Master Required: Team Members, Product Owner Recommended: Business Owners as needed Iteration Planning Once at the start of every iteration (2 weeks) 4 Hours Facilitator: Scrum Master Required: Team Members, Product Owner Recommended: Business Owners as needed Iteration Review Once every end of the Sprint (2 weeks) 1 Hour Facilitator: Product Owner Required: Team Members, Product Owner, Product Manager(s) (Feature author/owner) Recommended: Business Owners as needed Iteration Retrospective 1 Hour Facilitator: Scrum Master Required: Team Members, Product Owner Recommended: N/A (Agile Team members only) Backlog Refinement Continuous (at least 1 or 2 touch-points per Iteration) As needed Facilitator: Product Owner Required: Team Members, Product Owner Recommended: Business Owners as needed