Agile Ceremonies Format and Sample Agenda

1. Daily Standup
Daily Standups are not status meetings. Team swarms everyday and ensures the delivery.

1. What did we do yesterday (Towards our sprint goals)?
2. What are we going to work on today (Towards our sprint goals)?
3. Are there any blockers (or) issues/inhibitors on our work towards completing our sprint goals? 

Links

• Agile Board :
• Team SharePoint: 
• Team OneNote: 

 
Daily-Standup Protocol:

• This ceremony is time-boxed to 15 mins only. Please come prepared with the short and crispy status to save everyone’s time.
• Please update your work items before the standup (tasks/hours/comments). This helps to reduce the discussions and explanations.
• If you are not planning to attend the daily standup, either Ping the status in the Team’s channel (or) email status to the Scrum Master and cc the team.
• Misc/In-depth discussions can be discussed at the end of the session (Parking lot discussion).

2. Backlog Refinement:

     1. Discuss the stories for next sprint including requirements/scope and architecture.

             a. Identify the dependencies

             b. Estimate the Story

             c. Assess the sprint readiness. If ready, add the tag – SprintReady.

3. Sprint Planning

1. Review Team’s Capacity – (5 Minutes)
2. Planning – (45 Minutes)
   • Define the Sprint Goal.
   • Discuss and answer any additional questions on the work item scope. 
   • Determine work items ownership
3. Dependency matrix with the cross teams and within the team – (5 Minutes) 
4. Check List – (5 Minutes)
   • Are all the US assigned with owners along with estimation?
   • Sprint’s cumulative estimation met with Team’s velocity?
   • Individual team member’s commitment and whole team’s commitment?

4. Demo & Retro:

     1. First 30 Mins – Demo: 

1. Team Members demo their work – > Open to guests.
2. Its a best practice to provide the US#, desc along with the screenshot, just in case if a QA runs into an env issue while giving the demo.

     2. Last 30 Mins – Retrospective:

1. Go through the Sprint Report – Link to the Report
2. Retro feedback entry and discussion.
3. Link to the Retro – Retro Board Link

Other/Misc  Meetings:

1. Weekly On-Call handoff meeting: 

Only previous and incoming On-Call guys need to attend each week. Others welcome to join if interested. 

Tentative weekly agenda:

1. Summarize previous week issues
2. Summarize previous week assistance requests
3. Status update / handoff for any issues carrying over to current week
4. Anything else worth noting

2. Learning Session Meeting:

Link to the Technical topics sheet  –   Link to the Excel in the SharePoint

Please note there is no limit for the topics, it could be on any technical topics from Windows OS, Office, SharePoint, Code specific, Data Structures & Algorithms etc. Please update the Excel spreadsheet 

• With the topic you are interested in.
• If anyone is interested in the same topic that is already listed please update the Vote Count. The higher the vote count that topic gets priority. 
• If anyone has knowledge on the topic listed and you are interested in presenting, Please add your name in the presented by column.
• All the sessions will be recorded and uploaded to Team SharePoint site. 

3. DevOps Team Weekly Retro:

Scheduling this meeting to discuss on Environment issues encountered during last week.

1. Issues like Memory, CPU spike and core scenario failures.
2. Deployment failures including deployment blockings for more than 24 hours.
3. Decide on Bugs to Follow-up with the Dev Team for the RCA.

4. Team Mobbing session:

    All the brilliant brains work on:

• The same thing..
• at the same time
• in the same space
• on the same computer