Transition to Agile - the fun way

We all have heard the term “AGILE” many times. The manifesto of Agile software Development was signed in 2001. It described the new approach to Software Development. Since then agile has gained significant traction in various industries from Advertising to Manufacturing to Finance and even healthcare.

Agile is collection of principles and values that enables teams to deliver work in small, workable increments thus delivering value to their customers with ease. This helps the teams to respond to changes faster. To put it in simple words, the agile organizations know the best way to drink a tank full of water is one glass at a time.

But the important thing here we need to understand is that, Agile is not a quick thing or change we can implement overnight. It requires a 360-degree shift of not only the way your team works but of a mindset. That’s where this fun way of transitioning will help the team to understand.

Before I go further explaining these fun activities you can implement, let’s look at what you can expect out of these.

You must have heard the apologue “Boiling the Frog”.

The premise is that if a frog is put suddenly into boiling water, it will jump out, but if the frog is put in tepid water which is then brought to a boil slowly, it will not perceive the danger and will be cooked to death.

So, if you would like to put everything on your team in one go to transition them to Agile, they will jump out and will not understand it. But with the fun ways, you can slowly inculcate the Agile ways of working in them and then it will come from within. These fun activities will

1.??????Help teams to get comfortable with agile concepts in way that’s approachable as the fun activities such as games and small practical exercises strongly connected to human development and intelligence.

2.??????Offer hands on learning experiences that are very team engaging.

3.??????Provide an opportunity for the teams to improve creativity and problem solving

4.??????Help teams to unite and tackle a shared challenge by collaborating and working in a non-competitive environment.

Let’s quickly move on to these fun activities.?

Activity 1: Passing the Parcel

Time Required:?15 Mins

Mode: Physical or Virtual

Number of Players: 4+

Props Required: Balls or any other product

Learning Outcomes: Agile Production Process

Game Play: This is one of the most well-known game out there, helps the team to understand production process and agile projects. The team need to use self-organization, establish a process and iterate.?It can be played in person with physical balls (or any other object) to be passed back and forth or virtually using collaboration tools like MiroBoard, Lucidchart, Mural.

The game has a simple goal. Your team will pass a ball (ormultiple balls) around the table. Every team member needs to touch the ball once. When a ball makes it all the way around table, the team earns one point.

The game is split into sprints, with each sprint lasting 3 minutes. In first minute, the team should commit the number of points they expect to score in the first round and discuss their approach. The next minute is actual game play where the ball is passed around. The last minute is used to write down the actual number of points they earned as well as what they learned.

Then move on to the next sprint. Rather than using one ball, allow team members to choose as many balls as they would like the pass at one time. Your team will learn a lot as they iterate their approach and attempt to score more points.

After multiple sprints, you can introduce them to the velocity concept as well.

Activity 2: Bake a Cake

Time Required:?6 Mins

Mode: Physical or Virtual

Number of Players: 4+

Props Required:None

Learning Outcomes: Iteration and customer feedback

Game Play: This activity is designed for people who are new to agile process and practices. It is a helpful way for teams to learn about iterations and customer feedback. This can be done in person or virtually using any collaboration tools.

The Goal is simple and Delicious: you are trying to make a cake based on inputs from your customers. Your team will select one person to be the product owner and everyone else will be customer.

The PO is tasked with making a cake that customers will love, and they have their choice of type (Pineapple, Blackforest, chocolate, fruit etc.), Fillings, shape, toppings and any other special features (gluten free, sugar free etc.)

Each iteration gives PO a chance to source feedback from their customers on different elements of the cake. During the first round, they will ask customers to give a “Yay or Nay” to each type of cake. They will make a final decision (inform customers), note it and then moved to next iteration where they will ask about the next feature of the cake.

They will keep going until they have created a cake that satisfies most of their customers.

Activity 3: Paper Plane Race

Time Required:?30 Mins

Mode: Physical

Number of Players: 4+

Props Required: None

Learning Outcomes: Iteration and Time Blocks

?Gameplay: We all know how build a simple aeroplane with paper. But what if we are trying to build a plane which will fly the furthest distance. This energetic and simple activity will familiarize your team with working sprints or time blocks, as well as iterating on their ideas.

Split your team into groups,and give them each a stack of paper. Their goal is to build as many paper planes as possible. The catch? Team members can only make one fold at a time before passing the piece of paper to the next person. Additionally, planes will only count for points if they fly a minimum distance determined by your entire team.

You’ll break the game down into six-minute sprints: two minutes for planning, two minutes for building and testing, and two minutes for a retrospective. Before the time box begins, teams should give a count for how many planes they plan to produce, so they can evaluate themselves during their reviews.

It’s a great way for your team to get comfortable with numerous aspects of agile, including collaboration, sprints, and agile retrospectives.

To Be Continued... (with more activities)?