Scrum Meetings

Guidelines
Speaker’s Name, SAP
Month 00, 2017

PUBLIC

Partner logo
Objective of this Guideline

This guideline provides the characteristics of:

A. Daily Stand-Up Meetings
B. Scrum of Scrum Meetings

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Characteristics Daily Stand-Up Meeting

 Same time daily

 Same place (preferably at task board)
 Stand-up meeting: Everybody stands in front of the task board
 Entire duration: max. 15 min
 Not a problem-solving or design session, not a status meeting to anybody else than team
 Scrum master reports on obstacles. Update of impediment and obstacle backlog
 Update work remaining on tasks for burn-down. Sprint is fixed on backlog item level but flexible on task level
The team is allowed to add, change or remove tasks or to adapt estimations
 Non-team-member invited to listen and observe (PO, user, manager and other stakeholders)

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Daily Stand-Up Meeting Questions PRIN
T-OU
T an
d pin
to t a
sk bo
Each participant answers four questions: ard
1. What did I accomplish since the last meeting?
2. What will I accomplish today?
3. What obstacles are in my way?
4. What will you accomplish tomorrow?

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

Meeting Rules PRIN
For Daily Stand-Up/Daily Scrum Team T-OU
T an
d pin
to t a
 Arrive on time or early sk bo
ard
 Be ready to say what you did since the last meeting and what you plan to do today
 Keep your report specific, precise and short in order to help the meeting end within 15 minutes
 Listen to other team member's status in case it might relate to your tasks or impact you
 Don't interrupt people when they are talking
 Note the tasks or action items you volunteer for
 If you raise an issue or question that can't be resolved in a minute, ask to discuss with the parties involved
after the meeting
 For those calling in, be sure to start your report with "This is [your name]“
 Non-team-members invited to listen and observe but not to actively participate (product owner, user,
manager and other stakeholders)

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Scrum of Scrum Meeting
To Coordinate Work Amongst Teams

 Scrum of Scrum meetings allow teams to discuss their work, focusing especially on areas of overlap and
integration
 Examples of possible subjects for SAP projects:
– Master Data, Interfaces, Security, Conversion, Reporting.
 Scrum of Scrum Meetings differ from daily Scrums:
– They do not need to be held daily (e.g. 2-3 times a week).
– They are problem-solving meetings.
– They do not need to be timeboxed to 15 minutes. Recommended length is between 30 and 60 minutes.
– The team will choose the best representative to participate in the Scrum of Scrums. (Can vary from
meeting to meeting)
Duration Agenda Item
Timeboxed to 15 minutes Each participant answers 3 questions:
• What has my team done since we last met that could affect other teams?
• What will my team do before we meet again that could effect other teams?
• What problems in my team having with whch it could use help from other teams

As needed Resove problems and discuss items on an issues Backlog.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Thank you.
Contact information:
F name L name
Title
Address
Phone number

Partner logo