Do You Want to Play a Game?

by Brenda Camille Davis

Nine years ago in the Windy City, at one of the major financial corporations, senior leadership decided we need to make a major change. The business stakeholders were not pleased with the time it took for a project to be delivered to them, which usually ranged from nine to eighteen months. The decision and intentional commitment to begin the Agile transformation came from the top. A leading Agile transformation company was hired, and training and coaches were in place.

I was a project manager at the time, with over ten years of waterfall mindset, when my Agile journey started. I was a sponge and open to learning how our teams could make improvements. To start the process, I registered for class and began googling information on Agile, but there was so much information, I decided to wait for class to get started.

On day one of class, leadership kicked off the day with “Why Agile?” The senior vice-president talked enthusiastically about the Agile benefits. A surprise to me, we were told to pair up with someone at our table and to write on post-it notes, “Why do we have difficulty delivering projects in a timely manner?” We were told to put our post-notes on the white board under the category that they best fit in. A few of us said, “I think we are playing a game.” It was never called this by the coach, but it was “The Learning the 12 Agile Manifesto Principles Game”.

As my Agile journey continued, I loved the improvements I saw with the teams I worked on, and looked for opportunities to learn more about the framework and what other companies were doing that were having successful transformations. I joined local Agile meet-ups and attended meetings and conferences that were focused on Agile.  

During one of the local meet-up group meetings, we were broken into teams and told that for the next five minutes, we should write on post-it notes and add to the board what we do each morning before we leave home to go to work. We were then told to name the tasks we would perform if we only had 15 minutes after waking up and before we had to leave home to go to work, so we worked with our team to eliminate some of the tasks from the board. In the next iteration we only had 10 minutes, then five minutes. Through this game, we learned team building, prioritization, and introducing Kanban to share with our company teams. The Kanban board should all the tasks in the “To Do” initially, then in the 15 minute column, then the 5 minute column; this was our way of showing how WIP (Work in Progress) looks on a Kanban board.

More recently, as a SAFe Scrum Master, at the end of each iteration I facilitate the retrospective with my team. It is important to keep the team innovative, engaged, motivated and encouraged to grow and share. Each iteration we play a game, and yes, there are post-it notes. These retrospective games have included Weather (What were the weather conditions of this iteration?), Your Super Power (What Super Power Did You Demonstrate During This Iteration?), Focus On/Focus Off (productive communication), and Twitter (In 140 words or less write about the iteration). The team says all the time how now they look forward to attending Retrospectives because they are all new and each one challenges their way of thinking of improving and growing as a team. These games and so many others are found in the book Agile Retrospectives Making Good Teams Great by Esther Derby and Diana Larsen and by Googling “retrospective”; there is a great list (40 ideas to spice up your retrospective) on

No matter what game you are playing, if it is promoting the Agile principles, ceremonies, or continuous learning, then this a part of being Agile.

The One Where I Accidentally Presented At a Conference

By Zoë Kaler

Last September, I attended my first work conference: Agile Midwest 2019. Day one was called “Women in Agile.”  

The keynote speaker was an upbeat, knowledge-filled woman named Jenny Tarwater. Her interactive keynote included a worksheet to help us create an action plan for “Amplifying Our Voices.” There was a section on the worksheet called “I Will…” where we listed the things we, as women in agile, will do to amplify our voices. The first thing I wrote was “embrace the uncomfortable.” Little did I know how soon I would practice this pledge. 

Day two of Agile Midwest 2019 was called “Open Space.” Again, first work conference, so I had NO idea what that meant; I came to find out it essentially means crowdsourcing the day’s topics. All 350ish of us sat facing the middle of the room where the microphone and “stickies” were. If you had a topic you’d like discussed, you came to the middle, wrote it on a sticky and announced it to the room. Then you put the stickie on panels called the “Marketplace,” which indicated the time and room number for that topic. 

In the morning session, I sat back and watched. I didn’t think I had anything to contribute to this group of seasoned conference-goes. However, when we reconvened for the afternoon, I knew I wanted to contribute. I saw a gap in the morning sessions. There was so much talk about how to do Agile, how to implement Agile, problems with Agile, but no talk about what happens after the product development parts of Agile. What do you do after you created this awesome product? How are you telling your users and stakeholders what you’ve accomplished? Are you even doing this at all?

I’ve found stories to be an effective way to talk about these product outcomes, so I added, “Storytelling in Agile” to the Marketplace. I chose the first time slot for the afternoon session, so after the Marketplace was full, the conference-goers disassembled to their selected topics and I headed to mine.   

1pm arrived. It was time to get started. Trying to start a conversation, I asked the room if they wanted to share how they practice storytelling in Agile. No one raised their hands. Someone piped up and said, “Aren’t YOU going to tell US??” My throat lumped up and I realized that these people were not here to have an open conversation. They were here to learn about something they knew nothing about, and they expect ME to teach THEM!  

I brought this topic to the Marketplace because it’s something I believe in. I studied storytelling in undergrad as a journalism major and in grad school as an information science student. I’ve gone on to practice it in my career. I know a thing or two about it, but, needless to say, I was not prepared to teach these people anything. I began to recall all I could from the IS 590: Storytelling course I took in the Fall 2018 semester. So, there I was, rambling about the story structure of “The Three Little Pigs”. I asked questions and got no hands, asked more questions and got blank stares. I felt the lump in my throat grow, my neck and face get hot, and my chest tighten. What the heck was I doing?!

Luckily, I had just been to a session called, “Everything Icebreakers,” so I decided to break the ice with a game called “Link Up.” The object of the game is to learn something about everyone in the room while forming a human “link.” The first person yells out something unique about them, such as “I have a cat!” and if you have a cat, you yell, “link up” and run up the that person and link arms. This goes on until everyone is “linked.” I saw this as an opportunity to not just breaking ice, but for me to prepare for the next 50 minutes. 

With the broken ice and then next 50 minutes roughly planned, I dove in, embracing the uncomfortable…

I told a story about the jacket I was wearing, how I’m trying to pay off my student loans at an accelerated pace, and how the trip to Ann Taylor LOFT to pick up said jacket set me back a little more than intended. That got a few laughs and boosted my confidence. I told them about the three main elements of a story: tale, teller, and audience. I asked them to tell their neighbor a story; then we talked about how they felt telling and listening. We talked about empathy and how we’re humans who remember narratives better than facts. Then we talked about “Three Little Pigs” (again) and “Little Red Riding Hood” and how those story structures can apply to the corporate world.  

This 60 minutes in conference room 103 at Agile Midwest Open Space was the scariest thing; standing up there, responsible for filling the heads of theses 20 or so individuals with knowledge. But it ended up being a huge growth opportunity. 

As I was looking over my notes from Agile Midwest 2019, that note I wrote under the “I Will…” section caught my eye. In fact, a ton on the notes I took at “Women in Agile” caught my eye. I’ve even signed up for their “Launching New Voices” program to improve my public speaking skills.  

I could’ve left the room, I could’ve ignored my urge to add to the Marketplace in the first place, but I felt a little fire that day that told me to keep going and stand in that uncomfortable place.