Meetings

Everyone loves meetings, right?

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.

References

1 - Scrum Guide https://scrumguides.org/scrum-guide.html

2 - Scaled Agile Framework https://www.scaledagileframework.com/

Program Level/ART Ceremonies

Name	Outcomes	Frequency	Timebox	Attendees
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	2 Days	Facilitator: Release Train Engineer (RTE)
				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	Brief description of the actual feature, its business context and the PI Objectives supported Integrated production-like demo of each new feature finished Identification of risks and impediments (if applicable) Open discussion for questions and feedback	Once at the end of every Iteration (every 2 weeks) Final integrated PI System Demo would occur during I&A Workshop	1 Hour	Facilitator: Release Train Engineer (RTE)
				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	PI System Demo Quantitative Measurement Relevant ART Metrics Business Value vs. Actual Value Program Predictability Measure Retrospective and Problem-Solving Workshop Identification of biggest root cause Brainstorming and Creation of Improvement Backlog items	Before the start of each Program Increment (every 10-12 weeks) Planned during I&P Iteration Occurs before the PI Planning	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	Scrum of Scrums Discussion and coordination of major dependencies Discussion and problem-solving of feature impediments Product Owner Sync Progress towards PI Objects Assessment of any scope adjustments (if applicable)	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	Funneling new feature ideas Analysis, definition, and adding details to feature description, benefit hypothesis, acceptance criteria and sizing Prioritization through WSJF and approval of Product Manager(s) for feature readiness	Continuous (meeting as necessary)	As needed	Facilitator: Product Manager(s) (Feature author/owner)
				Required: Product Owners, Solution Management & Architect (if applicable)
				Recommended: Release Train Engineer (RTE), Scrum Masters

Team Level Ceremonies

Name	Outcomes	Frequency	Timebox	Required Attendees
Daily Stand Up	Daily team plan to accomplish Iteration Goals/PI Objectives Coordination of dependencies and impediments	Daily	15 Minutes	Facilitator: Scrum Master
				Required: Team Members, Product Owner
				Recommended: Business Owners as needed
Iteration Planning	Determined Iteration Goals Prioritized and committed Iteration Backlog based on PI Objectives and team capacity	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	Review of iteration Goals and Demo of accomplished stories in production-like environment Presentation of Spikes/Enablers (if applicable) Product Owner/Stakeholder feedback	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	Discussion of what went well, what didn't and what could be improved for next Iterations Quantitative and/or Qualitative Improvement Backlog/Action Items	Once every end of the Sprint (2 weeks) Occurs after the Iteration Review and before the Iteration Planning	1 Hour	Facilitator: Scrum Master
				Required: Team Members, Product Owner
				Recommended: N/A (Agile Team members only)
Backlog Refinement	Analysis, definition, and adding details to Story description and acceptance criteria "Ready" backlog with prioritization by the Product Owner Sliced/chunked-down and estimated Stories	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

Page tree

Meetings

References

Program Level/ART Ceremonies

Team Level Ceremonies