Inviting people to take a walk outside is a deceptively simple and powerful tool for collaboration, for team-building, and for team health.  This workshop will explore different ways to take a walk, discuss typical Agile challenges which can be addressed by different kinds of walks, and report on some scientific studies of what changes physiologically after we’ve been for a walk outdoors.   And yes, those who are interested will actually go outdoors!

“Let’s go for a walk!” is an invitation that gets people thinking about the weather and connecting with the wider physical land and world where they work. Taking any kind of break from being indoors can inspire playfulness, creativity and memories of a shared experience. Well-guided walks can also provide a team with a common experience of absorbing new information as an ensemble through heightened observation and listening skills,  improved critical thinking, an appreciation of the importance of soliciting and connecting different perspectives. It meshes well with the mindset of an Agile Retrospective, and with a culture of ensuring every voice is heard.

Agile walks I’ve guided in the past include: a basic nature walk to understand the landscape surrounding a team’s place of work; a docent-style visit to a destination; a walk inspired by Visual Thinking Strategies (VTS), a method developed by the museum curator community to facilitate a conversation about a piece of art; and a walk with focus cards inspired by a design community event at VergeNYC.

Nature and artists have a lot to teach us -- getting ourselves to pay attention is the challenge, and simply taking a walk helps with that. 



Outline/Structure of the Workshop

Indoor lecture and discussion for the first 50-60 minutes, after which we'll break into groups to go outdoors on preplanned routes for the remaining 30-40 minutes.


Learning Outcome

Understand at least three different ways to guide a team or other set of collaborators on a focussed walk to address typical Agile adoption challenges.

Target Audience

Scrum Master, Scrum team members

schedule Submitted 5 years ago

  • David Koontz

    David Koontz - Cultivating Collaboration - Simulation of Pair Programming via Tangrams Exercise

    David Koontz
    David Koontz
    Agile Transition Guide
    schedule 5 years ago
    Sold Out!
    90 Mins

    It’s said that two heads are better than one, in reference to problem solving. We will use Tangram puzzles to simulate this experience, and via structured debriefs of these exercises, discover the powerful behaviors of awesome collaboration, and the negative warning signs of poor collaboration.


    We will jump right into simulation exercises, come prepared to have FUN and learn by doing.

    No lecture - if you want a lecture… go here:

    References will lead you to the science behind collaboration - if you wish to know more.  Seems like an example right about now might be helpful,  wish I had a chicken tangram....

    Tangram example of a chicken

  • Mike Bowler

    Mike Bowler - Agile Technical Practices in LEGO®

    90 Mins

     In this interactive and engaging workshop, you will learn the concepts behind, and the value of, several Agile Engineering Practices. Without requiring programming or other technical knowledge, these concepts can be explained through the use of play and understanding the importance of failure in individual and team growth.

    You will be given several challenges to complete in LEGO bricks and through this, and the subsequent debrief, you will learn about the agile technical practices.

    We'll cover simplicity, TDD, refactoring, technical debt, and continuous integration.

  • 180 Mins

    Want your team to really learn Agile? Have them teach it back to themselves. Here’s their assignment:
    "Design, implement, and deliver courseware that teaches you everything you need to know about Agile."
    Guide your team one step at a time through the complete Agile product development lifespan, from team formation all the through product delivery and team retrospective. Your team members leave your session with:

    • a demonstrated high level of Agile proficiency—they delivered an actual product,
    • high internalized knowledge of Agile—they taught the subject matter to their teammates, and
    • an important artifact—a team-specific guide to everything they need to know about Agile