5. PRACTICAL MEETINGS EVENTS
5
REMOTE
Checklist to determine if you need to meet:
Do you know what you need to move forward? If so, proceed, if
not, figure out exactly what you need before proceeding.
Do you need others to make progress? If so, proceed, if not,
plan your next steps and get to work.
Do you know who will provide what you need? If so, proceed, if
not, decide who must be engaged and who should be kept in
the loop before proceeding.
Is a meeting the right format? Do you need real-time
interaction and synergy? If so, proceed, if not, try using an
alternative form of collaboration such as email, chat, or a
shared document.
Thoughtfully prepare for the meeting.
Reasons to Meet:
Decide. Make a decision so that work can move forward.
Ideate. Brainstorm a list of potential ideas, solutions, or
questions for further exploration.
Produce. Collaborate to accomplish a specific output.
Plan. Strategize or outline steps to achieve a result.
Align. Generate shared understanding of complex information.
Connect. Build stronger relationships among participants.
Determine the reason(s) to meet, and state the desired outcome,
and goal for that outcome.
Source: https://www.meeteor.com/momentum
Suggested outline for remote events:
Allow 5 minutes for set-up and banter.
Consider doing a quick grounding exercise, e.g. box-breathing.
State objective, intended outcome, and timebox.
Explain agenda, chosen approach, and rules for the event.
Establish pace and rhythm.
Get after it!
Send out notes and action items right after the event.
Rules for remote events:
Everyone joins from a quiet place with headphones and video
on with audio muted and system set to gallery view.
Only unmute and talk when called upon by the host. Signal you
want to talk by raising your hand.
Agree on a signal to use when you want the event to move on.
Be present, or don’t be there, and agree on a mechanism to
tune out temporarily if necessary. No multi-tasking!
Keep focus and pace through collaborative moderation.
At regular intervals, do something to (re)engage/energize all
participants. Set a timer to ensure this happens.
Practice Radical Candor to get, give, and encourage guidance
and feedback on the event as it unfolds.
Pro-tip: Remind participants a day before, on the day of, and 15
minutes before the event that it is happening and how to prepare
for it in terms of tech and input.
6. WHAT HAVE WE LEARNED ABOUT
REMOTE SPRINT PLANNING?
6
7. SPRINT PLANNING
OBJECTIVE
Determine what can be delivered in the Increment resulting from the upcoming Sprint and how the
work needed to deliver the Increment can be achieved. Read more…
INSPECT
• Product Backlog, DoD, Velocity, Capacity, Retrospective Commitments.
OPTION 1
• Keep It Sweet & Simple: Video call with all
people visible, and the entire team
collaborating on understanding the work of
the Sprint.
• Determine the Sprint Goal and the Product
Backlog Items that would help achieve it.
• Forecast the functionality that will be
developed in the Sprint.
• Craft a Sprint Backlog by discussing
options for how to create a done product
Increment during the Sprint.
• Use Liberating Structures to maximize
inclusion and engagement, e.g. Purpose to
Practice, Wicked Questions, and Triz.
OPTION 2
• Draw a Sprint Planning board in an online
whiteboard tool such as MS Whiteboard,
Google Canvas, Mural, Miro or IdeaFlip.
• Have the Product Owner populate the
board with Product Backlog Items that
would help achieve the Sprint Goal.
• Share the board with all team members
and set it to allow editing by all.
• The team member who knows most about
an item facilitates the discussion about it.
• After an item is discussed, evaluate shortly
if the next item might still fit in the
upcoming Sprint. Adjust the Sprint Goal
accordingly.
OPTION 3 – ASYNCHRONOUS
• Sprint Planning by collaboratively crafting a
Story Map in FeatureMap, or any other
tool that allows for asynchronous
communication.
• Send out email prompts to make sure
everyone gets to contribute.
• Promote video updates in addition to text.
TOOLS
• Slack, MS Teams, Zoom, Google Meet or
any other tool with videoconferencing.
• Pointingpoker or scrumpoker. Free.
• FeatureMap. €50 per user/year.
• StoriesOnBoard. $228 per user/year.
• Use the tools you already have!
ADAPT
• Sprint Goal, Forecast, Sprint Backlog.
7
REMOTE
≤ 8 HOURS
9. DAILY SCRUM
9
REMOTE
≤ 15
MINUTES
OBJECTIVE
Create a plan for the next 24h and identify impediments to development for removal. Read more…
INSPECT
• Progress toward Sprint Goal.
OPTION 1
• Keep It Sweet & Simple: Video call with all
people visible, answering the regular Daily
Scrum questions in a disciplined, one
person at a time talking, fashion.
• What did we do yesterday that helped us
meet the Sprint Goal?
• What will we do today to help us meet the
Sprint Goal?
• Do we see any impediment that prevents
us from meeting the Sprint Goal?
• Do we need or want any help to accelerate
our progress toward the Sprint Goal?
• Is there anything we can do to accomplish
the Sprint Goal today?
• Use Liberating Structures to maximize
inclusion and engagement, e.g. Troika
Consulting or 15% solutions.
OPTION 2
• Daily Cafe or Weekly Huddle, combine a
daily event with a social call.
• Start your weekly huddle with a grounding
exercise, e.g. box-breathing.
• High-fives all around. Share genuine
appreciation and praise for each other.
• Assign a timekeeper for the next round
and set a time-box. The timekeeper holds
up three fingers when there are 30
seconds remaining.
• Ask who wants to go first in checking-in
and answering the question of the week.
After doing so, that person selects who is
next. Check-in by telling how you’re doing
and feeling. Then, answer the question of
the week.
OPTION 3 – ASYNCHRONOUS
• Daily Scrum in a Slack channel, MS Teams,
WhatsApp, or any other tool that allows
for asynchronous communication.
• Use a bot to automate the process.
• Send out email prompts to make sure
everyone gets to contribute.
• Promote video updates in addition to text.
TOOLS
• Slack, MS Teams, Zoom, Google Meet or
any other tool with videoconferencing.
• Tatsu.io for Slack. Free during COVID-19,
then $1 per user/month.
• Jell for Slack and MS Teams. $4 per
user/month.
• Use the tools you already have!
ADAPT
• Sprint Backlog.
10. WHAT HAVE WE LEARNED ABOUT
REMOTE SPRINT REVIEW?
10
11. SPRINT REVIEW
11
REMOTE
≤ 4 HOURS
OBJECTIVE
Inspect the Increment and adapt the Product Backlog if needed. Elicit feedback and foster
collaboration. Read more…
INSPECT
• Increment, Sprint, Product Backlog, Current Business Conditions.
OPTION 1
• Keep It Sweet & Simple: Video call with all
people visible.
• The Product Owner explains what’s
Product Backlog Items have been done and
what has not been done.
• The Development Team discusses what
happened during the Sprint and
demonstrates and answers questions
about the work that it has done.
• The Product Owner discusses the Product
Backlog as it stands and everyone
collaborates on what to do next, as input
for the Sprint Planning.
• Use Liberating Structures to maximize
inclusion and engagement, e.g. User
Experience Fishbowl.
OPTION 2
• Soapbox Sprint Review: Ask all
stakeholders to record a video of them
using the Increment and provide feedback
while doing so, e.g. with Soapbox.
• Collect all videos and host a watch party
with the team.
• As the team watches the videos, they take
notes and compare and contrast what
they see and hear with their personal
experience with the Increment.
• The Soapbox Sprint Review can be
combined and augmented with the Sprint
Review Bazaar with several team members
per stall in virtual breakout rooms.
• After the watch party, discuss insights and
adapt the Product Backlog to reflect this.
OPTION 3 – ASYNCHRONOUS
• Sprint Review by collaboratively reviewing
the Story Map made in Sprint Planning in
FeatureMap, or any other tool that allows
for asynchronous communication.
• Send out email prompts to make sure
everyone gets to contribute.
• Promote video updates in addition to text.
TOOLS
• Slack, MS Teams, Zoom, Google Meet or
any other tool with videoconferencing.
• FeatureMap. €50 per user/year.
• StoriesOnBoard. $228 per user/year.
• Use the tools you already have!
ADAPT
• Product Backlog.
12. WHAT HAVE WE LEARNED ABOUT
REMOTE SPRINT RETROSPECTIVE?
12
13. SPRINT RETROSPECTIVE
13
REMOTE
≤ 3 HOURS
OBJECTIVE
Create a plan for improvements to be enacted during the next Sprint. Read more…
INSPECT
• Sprint, people, relationships, process, tools, DoD.
OPTION 1
• Keep It Sweet & Simple: Video call with all
people visible, and the entire team
collaborating on inspecting itself and
creating a plan for improvements to be
enacted during the next Sprint.
• Follow the 5-stage format for great remote
retrospectives proposed by Esther Derby
to set the stage, gather data, generate
insight, decide what to do, and close the
Sprint Retrospective.
• Generate a plan with Retromat and host it
on an online whiteboard, and/or use Aino
Corry’s templates for Google Drawings.
• Use Liberating Structures to maximize
inclusion and engagement, e.g. Ecocycle
Planning, Panarchy, and WINFY.
OPTION 2
• Follow David Horowitz’ rules & tips:
• Let the whole Scrum Team decide who to
invite to the Sprint Retrospective.
• Change who facilitates and have that
person focus on it, i.e. not participate.
• Facilitate open discussion by asking
Powerful Questions.
• Follow the energy of the Scrum Team!
OPTION 3 – ASYNCHRONOUS
• Sprint Retrospective in a Slack channel, MS
Teams, WhatsApp, or any other tool that
allows for asynchronous communication.
• Use a bot to automate the process.
• Send out email prompts to make sure
everyone gets to contribute.
• Promote video updates in addition to text.
TOOLS
• Slack, MS Teams, Zoom, Google Meet or
any other tool with videoconferencing.
• Reetro.io. Free.
• Retrospected. Free.
• Retrium. $29 per team/month.
• Use the tools you already have!
ADAPT
• Actionable and committed improvements for implementation in the next Sprint.
"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand."
—Norm Kerth, Project Retrospectives: A Handbook for Team Review
15. Scrum, Beyond The Lockdown
The Good, The Bad, The Ugly, and The Awesome:
GOOD: Working from home is not just possible, but
in most cases preferable.
BAD: We tend to loose touch with each other on an
emotional level when we work from home.
UGLY: We tend to overwork ourselves on a regular
basis when we work from home.
AWESOME: The office is no longer for getting work
done, but a meeting place to interact with your
coworkers and to get to know them better on a
deeply human level.
15