Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Scrum games for everybody

Everyone knows that the fastest learning is by games and fun. During games, you also integrate with others, get to know them better and spend nice time together. Integration with your team is an important part of coworking and make your job more pleasant. If you want to do something new with your team, learn them some agile and this type of thinking or even present them Scrum, these games will be perfect for you. Remember that all games are for fun and try to avoid strong competition. They are for fun and learning not for making conflicts. Also, you can modify these games but try to keep them in the spirit of Scrum. 

So, let’s start. 

A Paper Plane

You will need teams with at least 4 people in each, printer papers (it can be used before), space, board and marker. 

Each team has to build paper planes which can fly distance 20-30 meters (it depends what difficulty you chose). Planes have to be tested, be high quality and can’t be a paper ball.

Each game lasts 10 minutes: it’s 3 for planning, 4 minutes for building (and testing) and 3 minutes for review/retrospective in groups and at the end of whole games 15 minutes to analyze the process of improvements in each team at the forum. 

Game rules: 

  1. Build as many planes as you can in 3 minutes and test them in 1 minute before showing other groups.
  2. Only planes which can fly more than 20/30 metres will count at the end
  3. After planning each team should tell how many planes (high quality) they are going to build. That’s obligated for every team. Try to estimate sources and then bring as many planes as you told.
  4. Sum the final count of all build planes also these which weren’t tested, completed or couldn’t fly. Write it next to these “good scores” to see “tasks in action”
  5. During the retrospective, each team has to discuss improvements and write them on papers, because after the game every team share their ideas loudly and tell what was good and whatnot. 
  6. Summarize game and ask everybody about their feelings. What they like, what was good etc

Origin idea you find here:

Have fun!


Create small teams and give them a box with 6 Lego bricks. Every team has the same Legos and have to build a duck, horse, house, tower etc in 1 minute (or even 30 seconds). If you need to build something bigger you can give them 4 more Legos but not more because then it will be too easy.

You will find that every team created a different building using more or fewer bricks. And their art looks different than you expected and different than others. It is an important lesson to clearly communicate what you want to achieve, how and what your team has to do. 

Food Tower

Buy a few packs of spaghetti pasta and jelly beans/gums/rubber bands/marshmallows/filaments. (You need something to link this spaghetti).

Create a maximum of 6 person groups and give each of them ¼ pack (about 30 pieces) of spaghetti pasta and bands. Teams have 10-15 minutes to build a tower, house or other building with information that tower should be the highest/biggest and stay for all presentation without any help or repairs. It should also support marshmallow in the highest point of it. 

Try to support teams during the game and ask them about their tactics and ideas for this task. Try to talk with teams and during conversation suggest different methods (not always good) to find how they think and motivate to innovation. This is a group task so every member has to have a role. They should at first discuss how to do this and later step by step build making improvements if it will need them. In the end, you can organize a forum where teams show their arts and talk about their ideas, tactics and what they do.

Sprint simulator

It’s more for single persons but you can ask a team to do individually and later discuss their problems during the game and how they found solutions. It will be also very educational because they probably found different solutions and ways to achieve success. Probably each of them fought with different problems so sharing them on the forum can start a discussion. 

Game build a Polish company game and I truly recommend it:


There are many more games which will help you prepare your team for agile methodology but these are the most popular. I’m sure that you and your team will like them. If you know any more games/ activities having some elements from Scrum/Agile give a comment and I’m sure I’ll try them with my buddies. 

1 comment

Hello @Zuzanna Perkowska

I must say I love this post. Especially the food tower! I'm surely going to be running that team-building exercise in the near future. Would you have any pro-tips for running the session and caveats to avoid?



Hey @Fernando Bordallo 

I'm glad that you like it. 

If I was you, I would definitely make sure everyone feels comfortable in the group. This is necessary for group integration and avoiding conflicts or strong and not healthy competition.

I will focus on linking the results and final effects with really good fun and a nice atmosphere. By ending the task your team learn the definition of "done" and will follow the rules in the next Sprints.

Let them be creative and don't close on any crazy or weird ideas, it's their time to try new and make some experiments. Maybe they have their own ideas for fun- let them try to do it and if they need your help - give it to them. 

I will also write on a board a goal for a meeting. For example: On today's meeting we will become more integrated and get to know each other names. It's easy to do and after all, you will know if you do a good job or something went wrong. You will be able to discuss the good and bad points of the session.

If your team are a type of busy people, ask them to turn off their phones and don't use it during the session. And of course, you can't use it also. 

I suggest avoiding rushing. It's better to have more time than less. And of course, enjoy the moment, if you be an honest and open, your team will copy you. 

Have fun and good luck! Be sure to let me know how it went.


👍thanks for the tips. Have you structured the session in specific chunks? I'm thinking of something along the following lines:

  • Intro - Kick-off the fun
  • Mini team experimentation
  • Planning
  • Execution
  • Demo
  • Celebration + informal retro


Not yet, I was taking part in a similar session. It was well organized and we had a ton of fun 😎

Like Fernando Bordallo likes this

I'll be running a mini-trial of this with the team in the coming weeks. I'll post a little something on it :D 

Like Zuzanna Perkowska likes this


Log in or Sign up to comment

Atlassian Community Events