Meetings and Events

This page shows all challenges and their respective Best Practices related to meetings and events taking place throughout the Scrum process

Index Challenge Best Practice
(24) Hosting meetings, events or ceremonies is not possible for the scrum team [28, p. 129] Use another form of communication (e.g. a dashboard) [28, p. 129]
(25) High level of improvement of Scrum Masters efforts possible [6, p. 201, 4, p. 91, 24, p. 313] Recruit externals to help with hosting retrospectives [6, p. 201]
(26) Sprint Planning tends to be difficult [29, p. 5040] Communicate a single main goal for each upcoming Sprint [9]
Communicate objectives clearly [10]
Only pull as many Product Backlog Items as you are likely to accomplish during one Sprint to create the necessary focus on these tasks [29, p. 5040]
Use the teams velocity as a guideline on the volume of pulled tasks [14, 9, 30, p. 109]
Improve through using past experiences with the team's velocities [9, 30, p. 109]
(27) Punctuality for meetings is a lesser valued attribute within the team [23, p. 97, 4, p. 87, 24, p. 313] Establish consistency (e.g. start your meeting at 8 o’clock sharp) [12, 17]
(28) Ineffective Daily Scrum meetings [17] The team should stand up during your Daily Stand-Up meeting [9, 10, 17]
Establish consistency (e.g. start your meeting at 8 o’clock sharp) [12, 17]
Run the Daily Scrum meeting at the same place every time [31]
Have the same team members on your Daily Scrum every time [31]
Conduct your Daily Scrum within a time-box of 15 minutes to improve focus [31]
Aim to answer only the three main questions (What did I do yesterday? What will I do today? What’s in my way?) and concisely [17]
(29) The Daily Scrum morphs into a status update meeting towards stakeholders [23, p. 97, 31, 32, 0:20] Stakeholders should be updated elsewhere [31]
Aim to answer only the three main questions (What did I do yesterday? What will I do today? What’s in my way?) [31]
(30) The Daily Scrum morphs into a meeting to mainly solve problems rather than to update each other and discuss [31, 32, 0:20] The Scrum Master may moderate the meeting in order to bring attention to the three daily Scrum questions [31]
Dedicate a fixed length of time to problem solving [10]
(31) The Daily Scrum morphs into a gathering around the Scrum Board [31, 32, 0:20] Set your focus on discussions and updates again [31]
(32) Too much nonconstructive feedback is provided while conducting a retrospective [15, p. 69] Focus the teams attention on finding just a single aspect to improve upon instead of multiple [15, p. 69]
Refine given feedback with the team until everyone agrees to around one to three of the most important points [15, p. 69]
(33) Insufficient reflection of the bygone Sprint is being done by the team [6, p. 201, 15, p. 70] Establish regular retrospectives after every Sprint. [12, 33] If Sprints are ≤ 2 weeks in length, settle for a retrospective every second Sprint [16, p. 201]
Try reducing the frequency of retrospectives [15, p. 70]
The Scrum Master may try out different approaches to retrospectives each time [15, p. 70]
“Use the retrospectives as a postmortem meeting.” [15, p. 70]
Utilise remaining time for games or entertainment purposes (e.g. let the team decide on an action item) [15, p. 70]
Aim for fast improvements [11]