As adults, we learn by experiences, more than we learn by reading/writing/talking/listening.

This has always inspired me to come up with interactive games/workshops to help people change their mindset. All my games/workshops are intended towards helping people understand any practice through "Experiential learning"

This game is an attempt at helping participants understand one of the many great practices that are required to make a team Agile, with respect to coding.

 

 
1 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

The game is inspired by the African game of Jenga. Through multiple iterations, participants learn the thought process around some  great engineering practices. The Game starts with the first iteration, where teams are required to build a certain structure with Jenga blocks. Subsequent iterations, teams are asked to better the structure that was already built (Equivalent of code refactoring) and then build on top of it. At this point, teams realize the need of building a simple an easy to reuse piece of code.

 

Sharing the slides with the participants will give away the intent of the game, and learning might not be as effective. There is an element of surprise in the game. It will be best enjoyed when the slides are not known.

I have facilitated this game at various conferences. I have the slides, as well as the video recording of the same. 

I can share it with the organizers. Sharing with participants, before the event, will take the Fun-Learning out of the workshop

Learning Outcome

After this workshop, participants will experience the benefits of great coding, and its importance in having code agility.

 Since the participants learn all this through their experience, this leads to a mindset shift

All participants will go back, learning - 

 

> Simple Design

> Refactoring and the need for it

> Modularity

> Incremental design

Target Audience

Developers, QA, Development Managers, Scrum Masters, Architects

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Rohit Arora
    By Rohit Arora  ~  1 year ago
    reply Reply

    Hi Deepak,

    I like the topic and believe that games are good way of sharing a message.

    Do you think you would be able to introduce people to game, play and debrief in allocated 45 minutes?

    You have mentioned the workshop as Intermediate. What do you think as prerequisites that attendees should be aware of?

    Thanks,

    Rohit

    • Deepak Gururaja
      By Deepak Gururaja  ~  1 year ago
      reply Reply

      Hi Rohit,

      Good Morning.

      Yes, Introduction to the game, playing the game and the debrief can be complete in 45 minutes. However, if the participants have questions, then, there might be a spill over in time. I can propose 2 options here - 

      1. Extend the workshop to 60 minutes, and take the questions

      2. Keep the duration to 45 minutes, and take all questions off-line.

       

      Both have pros and cons. We can choose based on what suits us best.

       

      I would say that the workshop is intermediate, as it requires participants to have some prior knowledge and experience in coding and coding practices. Through the workshop, I intend to help participants understand the benefits of great coding practices. Hence, would require the participants to already be familiar with coding practices.

  • Sergey Shishkin
    By Sergey Shishkin  ~  1 year ago
    reply Reply

    Hi Deepak, thank for your proposal!

    After reading your workshop description, I still wonder if participants will learn the rules of simple design, the various methods of refactoring and how to do modular, incremental software design or just the intuitive need for those. Could you extend your proposal with a non-trivial example of a particular game experience and the learning transferred from it to the software domain?