The document describes an activity called "Keep Talking and Nobody Explodes" where participants must work as a team to defuse a bomb. It explains the roles of operators in the field who can see and interact with the bomb, and experts in headquarters who provide instructions using a manual. The document then lists common communication issues teams may face, such as providing too much or too little information, getting stuck on initial ideas without progressing, and a lack of trust or coordination between roles. Finally, it emphasizes the importance of continuous improvement in communication as the game is played.

1. 1

2. Keep Talking and Nobody Explodes
Effective Communication
https://www.linkedin.com/pulse/agile-beer-current-
numbers-how-did-we-start-daniele-fontainha/
Our Story

3. Agile Beer Rio de Janeiro- https://www.meetup.com/Agile-Beer-Rio-de-Janeiro/
Agile Beer São Paulo- https://www.meetup.com/Agile-Beer-Sao-Paulo/
Agile Beer Campinas- https://www.meetup.com/Agile-Beer-Campinas/
Agile Beer Blumenau- https://www.meetup.com/Agile-Beer-Blumenau/
Agile Beer Dublin- https://www.meetup.com/Agile-Beer-Dublin/
Agile Beer London- https://www.meetup.com/Agile-Beer-London/
Agile Beer Holland- https://www.meetup.com/Agile-Beer-Holland/
Agile Beer Singapore- https://www.meetup.com/agile-beer-singapore/
Social Media:
Facebook: https://www.facebook.com/agilebeerglobal/
Instagram: https://www.instagram.com/agile.beer/
LinkedIn: https://www.linkedin.com/company/agile4you/
Where we are
3

4. 4
Our Mission

5. Happiness: volunteer at setting and preparing the events for the fun and fulfilling feeling that
it brings to us. We do not see it as work, we see it as an expression of our passion for the
topic.
Respect: for our community, for each individual and their abilities, points of view and their
own value and what they bring to our circle and community.
Transparency and Openness: to collaborate and share openly any subject, and to talk
about any topic they judge to be aligned with our Agile Beer.
Collaboration: we need the whole so the magic happens. :)
Agreement and Commitment: with Agile Beer’s objectives and collective decisions (always
through consensus) and with the other organisers and members. Despite being a volunteer
work, we only commit to what we know we can deliver.
Win-Win: we believe none of our members should have a feeling of loss regarding our
events and the volunteer work in setting it all up.
Our Values
5

6. Keep Talking and NobodyExplodes!
6

7. Have you ever tried to defuse a ticking time-bomb?
7

8. 8
Let’s keep talking
and nobody
explodes!
Today is
YOUR
day!

9. • At least 5 for round one!
Volunteers Needed
9

10. 2 Engineers Out in the Field
10

11. 3 Experts in the HQs to Provide Directions
11

12.  An explosive device needs to be disarmed.
 One or two people are out in the field facing the device (operators) and
performing steps to disarm the device.
 Team of 3-4 experts provide directions from afar.
 The experts are equipped with a manual with instructions for disarming
various types of explosive devices.
 Each bomb is composed of several distinct modules with its own set of
instructions.
 All modules in the device have to be neutralized in under 5 minutes to
prevent an explosion.
Instructions
12

13. Ready to start?
13

14. GAME TIME!!!!
14

15. How was the communication between experts and
engineers?
15

16.  The operator provides little information
about the bomb's construction details.
 Repeating the same sentence over and
over.
 Difficulty describing the problem making it
hard for the experts to engage.
16
#1 Not Enough Information
Difficulty describing the situation/problem. Lack of words.

17.  Operator describes the entire device at
the beginning of the game, talking about
all the modules, batteries, serial number,
etc ...
 Or giving irrelevant details like Green
Button if instructions are black and white
 And sometimes this information is of no
use ...
 Doesn’t focus on what is really important
to disarm a module
 Too much at once
17
#2 Too much information
Inability to summarize key facts or focus on one topic at a time

18.  Experts advise operators to spend a long
time on the same point in the manual
 Failing to move on from a failed
experiment, i.e. hitting the same key,
although not evolving to the solution ...
 Example: stuck in the wrong page of the
manual (module when the correct one
was the keypad module).
18
#3 Too attached to the first idea
Spending too much time on the same solution without making
progress

19.  In an eagerness to solve the problem
quickly, the team (experts) do not read
the instructions correctly ...
 and do not pay attention to the details of
the manual, giving wrong instructions to
the operator
 Example: Labyrinth said about the
placement of circular marks, but the team
instructed to check the white and red
point ...
19
#4 Inattention to details
Rushing through instructions leading to mistakes

20. 20
#5 Multitasking
Trying to solve two problems in parallel
 Divide the team (experts) to solve more
than one module at a time
 However the operator can only do one
thing at a time
 It can lead to mistakes when paths get
confused.
 Depends a lot on the orchestration
capacity of the operator
 Sometimes it works, but in most of times
not ...

21. 21
#6 Not acting as one team
Everyone for themselves forgetting a shared goal
 Team members (experts) do not help
each other
 Putting each other down rather than
trying to reach a shared understanding
 Not listening to each other

22. 22
#7 Lack of Trust
Acting on your own and not trusting instructions
 Operator did not wait for the team to
finish passing the instructions and goes
out trying solutions anyway ...

23. 23
#8 Continuous Improvement
Improving communication as the game progresses
 Operator realizing that he should improve
the way he described the bomb, so the
instructions came in more clearly and
objectively.
 Operator orchestrated the communication
, steady flow of details and responses,
waiting for experts to give follow up
information
 Building on each other’s knowledge to
pain the picture

24. Anything else?

25. 25